Files
Claude-Code-Monitor/desktop/src/menu.ts
T
nntrivi2001 57dc91585d feat: Claude Code Monitor — lanes, pipelines and a merged workspace
Internal SmartGift build of a Claude Code monitoring dashboard.

Lanes: a durable unit of parallel agent work, one per working directory,
tracked across session restarts. Managed lanes are git worktrees the
dashboard provisions and can reset or remove behind a three-check destroy
guard and a counted preflight; adopted lanes are directories you already
own and are never destroyable.

Pipelines: a lane moves through pipeline stages. A stage the agent declares
with evidence renders green; a stage inferred from the tool-event stream
renders dashed amber and never counts as done. Detection is forward-only
within a 30-minute window, and never writes the declared stage.

Workspace: one page at /run with a lane grid, the selected lane's pipeline,
and a full Claude console behind a disclosure.
2026-07-30 14:39:03 +07:00

259 lines
10 KiB
TypeScript

/**
* @file Native application menu (the macOS top-bar menu).
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
*/
/* =============================================================================
* MODULE_GUIDE — extended in-file reference (comments only; safe to read, never executed)
* =============================================================================
* **Purpose:** Dashboard module consumed by the React client, MCP tools, or desktop shell depending on deployment mode.
*
* ## Design constraints
* - Local-first: no telemetry leaves the machine unless the user configures webhooks.
* - Fail-safe hooks path on the server must never block Claude Code; UI mirrors that
* philosophy by degrading gracefully (empty states, stale badges, reconnect loops).
* - Destructive flows stay behind explicit confirmation modals and server-side gates.
* - Internationalization: user-visible strings belong in i18n JSON, not literals here.
*
* ## Remote data & SSH
* Remote Data Sources let operators aggregate multiple machines. SSH entries describe
* how to reach a peer dashboard; the global data scope (`dataScope.ts`) narrows every
* scoped GET via `?sources=`. Health checks and import history surface in Settings.
*
* ## Observability
* Prometheus scrapes `GET /api/metrics` (see `monitoring/`). Grafana ships four
* provisioned boards (overview, sessions, tools, alerts). Native npm scripts and
* Docker Compose profiles are documented in `monitoring/README.md`.
*
* ## Internal dependencies
* - `./constants`
*
* ## Public surface
* - `MenuActions` — exported API; see TSDoc on the symbol for behavior.
* - `installApplicationMenu` — exported API; see TSDoc on the symbol for behavior.
* - `focusOrCreateWindow` — exported API; see TSDoc on the symbol for behavior.
*
* ## Testing pointers
* - Prefer colocated `__tests__` with Vitest + Testing Library for UI.
* - Server contract changes require `npm run test:server` and OpenAPI sync.
* - MCP edits: `npm run mcp:typecheck` and `npm run mcp:build`.
*
* ## Related docs
* - `ARCHITECTURE.md` — hooks → API → SQLite → WebSocket → UI pipeline.
* - `docs/API.md` — REST reference.
* - `.claude/skills/file-headers/` — mandatory `@author` header policy.
* ============================================================================= */
/* -----------------------------------------------------------------------------
* EXPORT CATALOG — quick index of symbols defined below (documentation only).
* -----------------------------------------------------------------------------
* **MenuActions**
* Part of this module's public contract. Downstream imports should treat
* the signature and return type as stable unless release notes say otherwise.
* When behavior changes, update the `@file` overview and relevant tests.
*
* **installApplicationMenu**
* Part of this module's public contract. Downstream imports should treat
* the signature and return type as stable unless release notes say otherwise.
* When behavior changes, update the `@file` overview and relevant tests.
*
* **focusOrCreateWindow**
* Part of this module's public contract. Downstream imports should treat
* the signature and return type as stable unless release notes say otherwise.
* When behavior changes, update the `@file` overview and relevant tests.
*
* ----------------------------------------------------------------------------- */
import { BrowserWindow, Menu, app, shell, type MenuItemConstructorOptions } from "electron";
import { APP_NAME } from "./constants";
/** Callbacks the menu wires to its items. `main.ts` supplies these, sharing
* the same handlers passed to `createTray` so both surfaces stay consistent. */
export interface MenuActions {
/** Bring the dashboard window to front, creating it if it doesn't exist. */
showDashboard: () => void;
/** Reload the currently loaded dashboard page (`webContents.reload()`). */
reloadDashboard: () => void;
/** Stop and re-launch the embedded server, then reload the window. */
restartServer: () => void;
/** Reveal `desktop.log` in the OS file browser. */
openLogs: () => void;
/** Flip the OS auto-start-at-login registration. */
toggleOpenAtLogin: () => void;
/** Read the current auto-start state, used to render the checkbox. */
isOpenAtLogin: () => boolean;
}
/**
* Build and install the native application menu (the macOS global menu bar;
* the per-window menu on Windows/Linux) and return it.
*
* Structure: an macOS-only app submenu (About, Open at Login, Services,
* Hide/Quit) prepended to standard File / Edit / View / Window / Help menus.
* Item visibility and roles branch on `process.platform === "darwin"` in a
* handful of places — see the inline comments on the `File ▸ Open Dashboard`
* item and the `Window` submenu for why those specific items are macOS-only.
*/
export function installApplicationMenu(actions: MenuActions): Menu {
const isMac = process.platform === "darwin";
const template: MenuItemConstructorOptions[] = [
...(isMac
? ([
{
label: APP_NAME,
submenu: [
{ role: "about" },
{ type: "separator" },
{
label: "Open at Login",
type: "checkbox",
checked: actions.isOpenAtLogin(),
click: () => actions.toggleOpenAtLogin(),
},
{ type: "separator" },
{ role: "services" },
{ type: "separator" },
{ role: "hide" },
{ role: "hideOthers" },
{ role: "unhide" },
{ type: "separator" },
{ role: "quit" },
],
},
] satisfies MenuItemConstructorOptions[])
: []),
{
label: "File",
submenu: [
// "Open Dashboard" is macOS-only. On macOS the menu bar is global and
// persists after the window is closed/hidden, so this item (and Cmd+1)
// genuinely reopens it. On Windows/Linux the menu is attached to the
// window itself and a menu accelerator only fires while that window is
// already focused/foreground — so the item could only ever run when the
// window is already up, making it a confusing no-op. Reopening from a
// hidden/tray state is handled by the tray's own "Open Dashboard" there.
...(isMac
? ([
{
label: "Open Dashboard",
accelerator: "CmdOrCtrl+1",
click: () => actions.showDashboard(),
},
] satisfies MenuItemConstructorOptions[])
: []),
{
// No accelerator here: the View menu's `reload` role already owns
// CmdOrCtrl+R. Two menu items sharing one accelerator triggers an
// Electron duplicate-accelerator warning at startup.
label: "Reload Dashboard",
click: () => actions.reloadDashboard(),
},
{ type: "separator" },
{
label: "Restart Server",
click: () => actions.restartServer(),
},
{
label: "Show Logs",
click: () => actions.openLogs(),
},
{ type: "separator" },
isMac ? { role: "close" } : { role: "quit" },
],
},
{
label: "Edit",
submenu: [
{ role: "undo" },
{ role: "redo" },
{ type: "separator" },
{ role: "cut" },
{ role: "copy" },
{ role: "paste" },
{ role: "selectAll" },
],
},
{
label: "View",
submenu: [
{ role: "reload" },
{ role: "forceReload" },
{ role: "toggleDevTools" },
{ type: "separator" },
{ role: "resetZoom" },
{ role: "zoomIn" },
{ role: "zoomOut" },
{ type: "separator" },
{ role: "togglefullscreen" },
],
},
{
label: "Window",
submenu: [
{ role: "minimize" },
{ role: "zoom" },
...(isMac
? ([
{ type: "separator" },
{ role: "front" },
{ type: "separator" },
{ role: "window" },
] satisfies MenuItemConstructorOptions[])
: ([{ role: "close" }] satisfies MenuItemConstructorOptions[])),
],
},
{
role: "help",
submenu: [
{
label: "Project on GitHub",
click: () =>
void shell.openExternal("https://git.smartgift.io.vn/Smartgift-AI/Claude-Code-Monitor"),
},
{
label: "Report an Issue",
click: () =>
void shell.openExternal(
"https://git.smartgift.io.vn/Smartgift-AI/Claude-Code-Monitor/issues/new/choose"
),
},
{
label: `${APP_NAME} v${app.getVersion()}`,
enabled: false,
},
],
},
];
const menu = Menu.buildFromTemplate(template);
Menu.setApplicationMenu(menu);
return menu;
}
/**
* Bring the dashboard window to focus, creating one via the supplied factory
* if needed. Shared by `main.ts`'s `ensureWindow` for every "open the
* dashboard" entry point (dock click, tray click, menu item, second-instance
* relaunch) so they all get the same restore/show/focus sequence.
*
* @param existing The current window reference, or `null`/destroyed if none.
* @param create Factory invoked only when `existing` is missing or destroyed.
* @returns The existing (now focused) window, or the newly created one.
*/
export function focusOrCreateWindow(
existing: BrowserWindow | null,
create: () => BrowserWindow
): BrowserWindow {
if (existing && !existing.isDestroyed()) {
if (existing.isMinimized()) existing.restore();
// Call show() unconditionally (not just when hidden): on Windows a bare
// focus() on a visible-but-background window often only flashes the taskbar
// button instead of raising it, whereas show() reliably activates and
// brings it to the foreground. Harmless when the window is already frontmost.
existing.show();
existing.focus();
return existing;
}
return create();
}