feat(code): add Option+Space quick entry widget

[fercgomes]

Summary

Claude-Desktop-style quick entry: pressing Option+Space anywhere on macOS — even with PostHog Code minimized or in the background — pops a small floating bar at the bottom of the active display where the user can type a prompt and pick a recent folder. Submitting creates the task and routes the main window to the new task detail.

Screen.Recording.2026-05-22.at.17.09.04.mov

• New QuickEntryService + quickEntry tRPC router orchestrate show/hide/submit and getRecentRepos.
• Frameless, transparent, always-on-top BrowserWindow (720×132) loaded from the same renderer bundle with hash #quick-entry; renderer entry branches to mount QuickEntryRoot.
• QuickEntryView reuses the existing PromptInput and calls TaskService.createTask with the user's last-used workspace mode, adapter, and model.
• globalShortcut.register(\"Alt+Space\") wired in index.ts with cleanup on `will-quit`.
• Adds OpenTask event on `UIService` so the QE submit flow can tell the main renderer to navigate to a specific task.
• Blur-to-hide with a 120ms grace so dropdown popups don't dismiss the widget.

Architectural note: because main-process services can't import `electron` directly (biome `noRestrictedImports` rule), the BrowserWindow primitives live in `window.ts` and the service calls them.

Out of scope / follow-ups:

• Settings UI toggle to enable/disable the widget.
• Customizable hotkey.
• True double-tap-Option detection (would require `uiohook-napi` + macOS Accessibility permission).
• Windows/Linux polish (`Alt+Space` collides with the window menu on those platforms).

Test plan

• `pnpm dev`, app boots, main window appears.
• With main window focused, press Option+Space → widget appears bottom-center of the active display.
• Minimize the main window, press Option+Space from another app (e.g. Chrome) → widget appears in front.
• Type a prompt, pick a folder from the dropdown, hit Enter → widget hides, main window restores + focuses, navigates to the new task detail, agent starts.
• Press Option+Space to open, then press Escape → widget hides.
• Press Option+Space to open, click another app → blur fires → widget hides.
• Press Option+Space twice rapidly → second press toggles off.
• Quit the app (`Cmd+Q`), reopen → shortcut still registers.
• `pnpm --filter code typecheck` passes.
• Biome clean on changed files.

Screenshots

The widget mimics the layout shown in the original screenshot from Claude Desktop: a horizontal pill at the bottom of the screen with prompt input + repo dropdown + send button.

[greptile-apps]

Comments Outside Diff (2)

1. apps/code/src/main/services/quick-entry/service.ts, line 172-178 (link)

   windowCreated flag can go stale after a renderer crash

   createWindow() sets this.windowCreated = true and never clears it unless dispose() is called. If the BrowserWindow closes unexpectedly (renderer process crash or OOM kill) without dispose() being invoked, the "closed" event in window.ts nulls out quickEntryWindow, but windowCreated stays true. From that point on, createWindow() is a no-op, so every subsequent toggle() call falls into show() → showQuickEntryWindow() → logs a warning and returns false. The widget is permanently broken until the app restarts with no user-facing indication.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: apps/code/src/main/services/quick-entry/service.ts
   Line: 172-178
   
   Comment:
   **`windowCreated` flag can go stale after a renderer crash**
   
   `createWindow()` sets `this.windowCreated = true` and never clears it unless `dispose()` is called. If the BrowserWindow closes unexpectedly (renderer process crash or OOM kill) without `dispose()` being invoked, the `"closed"` event in `window.ts` nulls out `quickEntryWindow`, but `windowCreated` stays `true`. From that point on, `createWindow()` is a no-op, so every subsequent `toggle()` call falls into `show()` → `showQuickEntryWindow()` → logs a warning and returns `false`. The widget is permanently broken until the app restarts with no user-facing indication.
   
   How can I resolve this? If you propose a fix, please make it concise.

2. apps/code/src/renderer/components/GlobalEventHandlers.tsx, line 578-632 (link)

   Inline type re-declaration duplicates CreateTaskRequest from schemas.ts

   The params object shape is declared inline via data as { content: string; repoPath: string; … }, which exactly replicates the CreateTaskRequest interface already defined in apps/code/src/main/services/quick-entry/schemas.ts. If a field is added or renamed in the schema it must also be updated here, creating a silent divergence risk. The tRPC subscription for onCreateTaskRequested already exposes the inferred type, so handleCreateTaskFromQuickEntry can accept the properly-typed argument directly instead of data?: unknown with a subsequent cast.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: apps/code/src/renderer/components/GlobalEventHandlers.tsx
   Line: 578-632
   
   Comment:
   **Inline type re-declaration duplicates `CreateTaskRequest` from `schemas.ts`**
   
   The `params` object shape is declared inline via `data as { content: string; repoPath: string; … }`, which exactly replicates the `CreateTaskRequest` interface already defined in `apps/code/src/main/services/quick-entry/schemas.ts`. If a field is added or renamed in the schema it must also be updated here, creating a silent divergence risk. The tRPC subscription for `onCreateTaskRequested` already exposes the inferred type, so `handleCreateTaskFromQuickEntry` can accept the properly-typed argument directly instead of `data?: unknown` with a subsequent cast.
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

Fix the following 3 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 3
apps/code/src/main/services/quick-entry/service.ts:172-178
**`windowCreated` flag can go stale after a renderer crash**

`createWindow()` sets `this.windowCreated = true` and never clears it unless `dispose()` is called. If the BrowserWindow closes unexpectedly (renderer process crash or OOM kill) without `dispose()` being invoked, the `"closed"` event in `window.ts` nulls out `quickEntryWindow`, but `windowCreated` stays `true`. From that point on, `createWindow()` is a no-op, so every subsequent `toggle()` call falls into `show()` → `showQuickEntryWindow()` → logs a warning and returns `false`. The widget is permanently broken until the app restarts with no user-facing indication.

### Issue 2 of 3
apps/code/src/renderer/components/GlobalEventHandlers.tsx:578-632
**Inline type re-declaration duplicates `CreateTaskRequest` from `schemas.ts`**

The `params` object shape is declared inline via `data as { content: string; repoPath: string; … }`, which exactly replicates the `CreateTaskRequest` interface already defined in `apps/code/src/main/services/quick-entry/schemas.ts`. If a field is added or renamed in the schema it must also be updated here, creating a silent divergence risk. The tRPC subscription for `onCreateTaskRequested` already exposes the inferred type, so `handleCreateTaskFromQuickEntry` can accept the properly-typed argument directly instead of `data?: unknown` with a subsequent cast.

### Issue 3 of 3
apps/code/src/renderer/features/quick-entry/QuickEntryView.tsx:95-104
Missing `.catch()` on the skills query — if the call rejects, it silently swallows the error, leaving the command list unpopulated with no feedback.

```suggestion
    trpcClient.skills.list.query().then((skills) => {
      if (cancelled) return;
      useDraftStore.getState().actions.setCommands(
        SESSION_ID,
        skills.map((s) => ({
          name: s.name,
          description: s.description,
        })),
      );
    }).catch((err) => {
      log.warn("Failed to load skills for quick entry", { err });
    });
```

_{Reviews (1): Last reviewed commit: "fix(code): invalidate tasks list after q..." | Re-trigger Greptile}

[greptile-apps]

Missing .catch() on the skills query — if the call rejects, it silently swallows the error, leaving the command list unpopulated with no feedback.

Suggested change

	trpcClient.skills.list.query().then((skills) => {
	if (cancelled) return;
	useDraftStore.getState().actions.setCommands(
	SESSION_ID,
	skills.map((s) => ({
	name: s.name,
	description: s.description,
	})),
	);
	});
	trpcClient.skills.list.query().then((skills) => {
	if (cancelled) return;
	useDraftStore.getState().actions.setCommands(
	SESSION_ID,
	skills.map((s) => ({
	name: s.name,
	description: s.description,
	})),
	);
	}).catch((err) => {
	log.warn("Failed to load skills for quick entry", { err });
	});

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/quick-entry/QuickEntryView.tsx
Line: 95-104

Comment:
Missing `.catch()` on the skills query — if the call rejects, it silently swallows the error, leaving the command list unpopulated with no feedback.

```suggestion
    trpcClient.skills.list.query().then((skills) => {
      if (cancelled) return;
      useDraftStore.getState().actions.setCommands(
        SESSION_ID,
        skills.map((s) => ({
          name: s.name,
          description: s.description,
        })),
      );
    }).catch((err) => {
      log.warn("Failed to load skills for quick entry", { err });
    });
```

How can I resolve this? If you propose a fix, please make it concise.

[adamleithp]

this is awesome! I really suggest you add the toggle on/off in settings before pushing this lol