feat(desktop): add cross-platform window capture

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}

[Bil0000]

What Changed

• Adds opt-in window capture for macOS, Windows, and Linux Wayland.
• Uses Shift + Shift by default on macOS and Windows. Wayland requires a key chord because its portal does not support modifier-pair shortcuts.
• Checks T3 Code keybindings, common system and app chords, and live OS registration before a normal key chord can be saved on supported desktop sessions.
• Requests macOS Accessibility and Screen Recording only when the user turns Window Capture on and the permission is not already granted. Startup only reads permission state.
• Attaches the image with app name and window title, plus the app icon and accessibility data when they are available.
• Runs accessibility extraction in a short-lived helper, so a native provider crash or timeout falls back to screenshot-only instead of crashing or blocking T3 Code.
• Adds a dedicated settings page, command palette entry, onboarding, platform-aware shortcut key caps, inline sound play controls, capture sound, high-density app icons, an early and gentler visual cue, compact image cards, and one-shot attachment animation.
• Stores pending captures durably and preserves their metadata through drafts, uploads, timeline rendering, and provider input.

Why

Users can add visual and text context from another app without leaving their T3 Code workflow or managing screenshot files. Native behavior stays in the desktop service, while the existing settings, IPC, draft, attachment, and provider paths carry the result.

Platform Details

• macOS and Windows capture the active window. Linux supports Wayland sessions; X11 sessions are unavailable.
• macOS permission prompts only run on the off-to-on settings transition. Already-granted permissions do not prompt again.
• Linux Wayland uses the system portal or the optional GNOME extension and requires a key chord. Portal captures omit accessibility data because the portal does not identify the selected window.
• Outside Wayland, normal key chords are probed through the OS global-shortcut registry. Wayland submits key chords to the desktop portal without claiming that the desktop accepted them. Modifier-only shortcuts cannot be reserved exclusively by any operating system.
• Modifier-pair listeners run only while Window Capture is enabled, require both physical keys to be held together, and stop on disable or app shutdown. macOS uses a permission-free polling helper; Windows and Linux use the isolated Node-mode hook.

Demo

CleanShot.2026-08-31.at.3.17.42.mp4

Testing on macOS

1. Run pnpm dev:desktop, then open Settings > Window Capture.
2. Turn Window Capture on. Permission requests should appear during this off-to-on change, not at startup or on the first capture.
3. In System Settings > Privacy & Security, allow both T3 Code (Dev).app and the terminal app used to run pnpm (such as Terminal, iTerm, or Warp) in:
   • Accessibility — lets T3 Code identify the active window and attach available text.
   • Screen & System Audio Recording (called Screen Recording on older macOS) — lets T3 Code capture the window image.
     If T3 Code is missing, use the + button to select <repo>/apps/desktop/.electron-runtime/T3 Code (Dev).app.
4. Fully restart dev mode after changing either permission: stop pnpm dev:desktop with Ctrl+C, then run it again. If macOS offers Quit & Reopen, still restart the terminal command so the dev server and app start together.
5. Open another app and press both Shift keys together. Confirm T3 Code attaches the image, app name, window title, and available icon and text to the current draft.
6. Turn Window Capture off and on again. Already-granted permissions must not prompt again.
7. Check a custom shortcut, each inline sound play button, Capture flash, Capture animations, and Capture window from the command palette.

Verification

• Focused tests passed for contracts, desktop capture, modifier-pair state, shortcut conflicts, typed IPC, durable delivery, settings support, draft bridge behavior, and timeline rendering.
• Strict focused lint, formatting, and whitespace checks passed.
• Contracts, web, server, and desktop type checks passed.
• Production web, server, and desktop builds passed.
• Electron desktop smoke test passed with isolated state under Xvfb.
• Desktop startup was verified with Window Capture and Capture Flash already enabled.
• Modifier-pair observation and accessibility extraction run outside the Electron main process. Native accessibility crashes, early exits, and timeouts fall back to screenshot-only; source thumbnails remain memory-bounded.
• The capture flash uses renderer-free native windows on macOS and Windows. Linux uses a short-lived renderer fallback. Every flash timer and window is destroyed after playback.
• The desktop bundle keeps uiohook-napi as a packaged runtime dependency with prebuilt macOS, Windows, and Linux binaries for the supported CPU architectures.

Checklist

• One user workflow
• Cross-platform behavior is explicit
• Permission timing is explicit
• UI evidence is included
• Focused tests and builds pass

Generated by GPT-5.6-sol in T3 Code using the Codex harness.

Note

Add cross-platform window capture with native Linux, macOS, and Windows backends

• Desktop process gets a DesktopWindowCapture coordinator that manages pending captures, compositor-specific backends, accessibility extraction, transparent transition overlays, and PNG persistence
• Native capture backends added for Hyprland (Wayland protocol), KDE (D-Bus/KWin scripts), GNOME (Shell extension), macOS (screencapture), and Windows (xa11y), with shortcut registration via D-Bus portals, compositor configs, and native modifier-pair polling
• Web layer adds WindowCaptureCoordinator.tsx, composer attachment frames with arrival animation, a two-step setup wizard, shortcut recorder, sound playback, and a settings panel with backend-specific status
• New IPC contracts in orchestration.ts and ipc.ts define capture state, config preview/apply, shortcut schemas, accessibility element trees (bounded to 10,000 nodes / 32,000 serialized chars), and DesktopBridge methods; captured accessibility metadata is compacted and appended to provider input as untrusted JSON
• Risk: Electron upgraded to 44.1.0 in desktop/package.json; composerDraftStore.addImage now returns boolean and rejects duplicate image IDs; keybindings event-key resolution uses physical key codes for punctuation shortcuts; client settings writes are now serialized through a promise chain; window-capture IPC handlers validate sender identity against the current main window's web-contents ID

^{Macroscope summarized 2fad302.}

Summary by CodeRabbit

• New Features
  • Added desktop window capture with configurable global shortcuts across macOS, Windows, Linux, and Wayland.
  • Captures include previews, application details, icons, accessible text, configurable sounds, and visual animations.
  • Added onboarding, command palette access, animated composer attachments, and a dedicated Window Capture settings page.
  • Added permission guidance, shortcut conflict validation, status reporting, and pending-capture recovery.
• Bug Fixes
  • Improved attachment metadata preservation, settings persistence, desktop window focusing, and menu-action delivery.
• Documentation
  • Added guidance for configuring and using window capture.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3f127620-45e6-49c1-a4b4-463c86a598df

📥 Commits

Reviewing files that changed from the base of the PR and between 297e448 and 293c41d.

📒 Files selected for processing (3)

• apps/desktop/src/windowCapture/DesktopWindowCapture.test.ts
• apps/desktop/src/windowCapture/DesktopWindowCapture.ts
• apps/desktop/src/windowCapture/WindowCaptureTransition.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 6 remain after this review.

---

📝 Walkthrough

Walkthrough

The pull request adds desktop window capture across contracts, native capture, IPC, web chat, settings, persistence, provider serialization, packaging, and documentation. It supports platform-specific shortcuts, capture metadata, animations, and pending-capture recovery.

Changes

Window Capture Feature

Layer / File(s)	Summary
Contracts and desktop runtime packages/contracts/..., apps/desktop/src/windowCapture/..., apps/desktop/src/electron/...	Adds capture schemas, platform capture paths, shortcut workers, accessibility metadata, persistence, animations, and desktop integration.
IPC and web capture flow apps/desktop/src/ipc/..., apps/desktop/src/app/..., apps/desktop/src/main.ts, apps/desktop/src/preload.ts, apps/web/src/components/desktop/..., apps/web/src/components/chat/..., apps/web/src/lib/...	Connects trusted IPC handlers, preload methods, capture coordination, animation destinations, composer focus, attachment previews, and command-palette capture.
Settings and delivery apps/web/src/components/settings/..., apps/web/src/hooks/..., apps/web/src/composerDraftStore.ts, apps/server/src/...	Adds capture settings and onboarding, serialized settings writes, source metadata persistence, provider-safe window data encoding, and attachment size enforcement.
Build and documentation support apps/desktop/scripts/..., apps/desktop/package.json, apps/desktop/vite.config.ts, pnpm-workspace.yaml, scripts/..., docs/...	Adds native runtime dependencies, worker packaging, macOS signing and usage metadata, development launcher updates, tests, and user documentation.

Estimated code review effort: 5 (Critical) | ~120 minutes

Merge Risk:🟠 High · up to 293c4

Window capture now imports text and metadata from other applications, listens for global shortcuts, and drains captures into drafts. At the current head, captured text is not isolated from provider instructions, the default shortcut can fail on Windows/Linux, timed-out accessibility work can accumulate, and captures can target stale or different drafts; these create security, reliability, and data-integrity risks, so the PR is not merge-ready without fixes or explicit acceptance.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 102 functions across 70 files.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely identifies the main change: adding cross-platform desktop window capture.
Description check	✅ Passed	The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not…

Full details: Description check

Explanation

The description includes What Changed, Why, platform details, testing evidence, UI evidence through a demo, and a checklist. It is mostly complete, although it uses custom checklist items and does not retain the exact UI Changes heading.

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Reviewed the new Effect service (apps/desktop/src/windowCapture/DesktopWindowCapture.ts), its IPC methods, layer wiring, and contract additions. Module shape (namespace imports, Context.Service with inline interface, exported make/layer, dependencies acquired via yield*) follows the conventions; the Effect.runPromiseWith bridge for the Electron globalShortcut callback matches the existing desktop native-callback pattern. Two error-modeling issues below.

^{Posted via Macroscope — Effect Service Conventions}

[macroscopeapp]

UI consistency review

Two findings, both in the new window-capture UI.

1. apps/web/src/index.css introduces a global rule keyed on the class trio .animate-in.fade-in.zoom-in-95, which does not exist as a utility in this project. The repo's established pattern (see ComposerStashBadge/prompt-stash-count-enter) is keyframes in index.css plus an animate-[…] utility at the owner. As written, the unlayered global rule wins over Tailwind's layered animate-none, so the call-site motion-reduce:animate-none is inert (reduced motion only works because of the duplicated media query), duration-200 never affects the animation, and any future element combining those class names silently inherits this animation.

2. WindowCaptureSettings records a shortcut on a Button without the data-keybinding-capture opt-out that app-level shortcut handlers check, so global capture-phase handlers (e.g. sidebar.toggle in AppSidebarLayout) consume the keypress before the recorder sees it.

Details inline.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR adds a broad cross-platform capture workflow with native compositor integrations, permission and shortcut handling, persistent screenshots, accessibility data, and provider prompt changes. Its production and sensitive-data blast radius, plus new static-analysis overrides and product defaults, require human review.

Not approved because:

• Per-review cost limit exceeded (workspace setting). Approvability relies on correctness review in order to determine eligibility

^{Review your spending limits in Billing settings, or comment @macroscope-app review this PR to bypass the limit and review now. You can add or adjust custom eligibility rules. Learn more.}

[macroscopeapp]

Window capture UI review: one new finding on WindowCaptureOnboardingDialog (dialog body bypasses the DialogPanel contract). The three findings from the previous run (index.css.animate-in.fade-in.zoom-in-95 global override, the matching ChatComposer class string, and the missing data-keybinding-capture on the shortcut recorder) are unchanged in this head commit and are not re-posted.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the web-side window capture surfaces. Four findings, all on newly added lines; the three items flagged in the previous run (global .animate-in override, call-site animation ownership, and the missing data-keybinding-capture marker) are resolved in this revision.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

UI consistency review of the window-capture web surfaces. Two findings on the new settings page; the composer/timeline attachment cards, the onboarding dialog, the keyframe ownership, and the command palette action all follow the existing primitives and conventions.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the web UI surface of this feature (composer/timeline capture cards, capture settings page, onboarding dialog, command palette entry, keyframe ownership). The earlier findings on the window-capture-card-enter keyframe ownership, data-keybinding-capture, DialogPanel composition, capability gating of the onboarding dialog, and the disabled state of the sound/flash/animation switches are all resolved. Two remaining items below.

Still open from earlier reviews (not re-posted): the shortcut recorder still preventDefault()s Tab so focus cannot leave the button, and WindowCaptureAttachmentDetails still anchors its title to text-foreground while rendering on bg-background/70 inside the text-message-foreground bubble.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture web code. Previously flagged items (recorder Tab handling, data-keybinding-capture, disabled-state parity for the feedback switches, capability gating on the onboarding dialog, DialogPanel composition, and the named window-capture-card-enter keyframes) all look resolved at this head.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Reviewed the changed web UI surfaces (window-capture settings page, onboarding dialog, composer/timeline attachment cards, command palette entry, index.css keyframe). Earlier rounds' items (shared focus-event constant, DialogPanel composition, data-keybinding-capture, Tab handling, named keyframe animation, uniformly gated switches) all look resolved. Two remaining consistency points on the new settings page.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

Two findings on the settings surface introduced/changed here. The composer and timeline capture cards, the extracted SettingsUnavailableGroup, the keyframe ownership, and the onboarding dialog composition all look consistent with the existing primitives now.

^{Posted via Macroscope — UI Consistency}

[macroscopeapp]

One consistency finding on the new window-capture attachment card; everything else (settings layout group, dialog composition, keyframe ownership, palette action) matches the existing contracts.

^{Posted via Macroscope — UI Consistency}