Pure black dark theme

[t3dotgg]

Dark canvas goes from #161616 to pure black with raised card surfaces, a light primary, and a rounder composer.

Before

After

---

Note

Low Risk
Visual and CSS token changes only; no auth, data, or business logic affected.

Overview
Dark mode shifts from charcoal (#161616) to a pure black canvas, with boot splash, theme-color, and CSS tokens updated so --background is black and card/popover surfaces use raised oklch grays instead of neutral mixes.

Primary actions in dark mode flip to a light primary on dark text (--primary near white), and focus rings move to a white alpha instead of the old blue primary.

UI polish includes a rounder chat composer (20px radii), stronger composer glass (82% card mix), sidebar v2 using dark:bg-card on the black canvas, user message bubbles with translucent white fill and no border in dark, terminal fallback background black, and a split-button border tweak on Implement actions in dark.

^{Reviewed by Cursor Bugbot for commit 70d022d. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add pure black dark theme and Sidebar v2 beta with thread settling

• Changes the dark mode background to pure black (#000000) across index.html and index.css, updating CSS variables for contrast, opacity, and composer glass opacity.
• Introduces a new SidebarV2 component (SidebarV2.tsx) behind a sidebarV2Enabled client setting, rendering animated card-based thread rows with visual status indicators ordered by creation time.
• Adds thread settling logic: effectiveSettled in threadSettled.ts marks threads as settled based on archive state, PR merge/close state, or configurable inactivity (sidebarAutoSettleAfterDays, default 3, range 1–90).
• Adds a /settings/beta route with controls for toggling sidebar v2 and configuring the auto-settle inactivity period; mobile gets a matching Beta section in settings.
• On mobile, HomeScreen renders a merged live + archived thread list when threadListV2Enabled is set, with a settled tail behind a divider, optimistic hold for newly settled threads, and settle/unsettle swipe actions.
• startNewThreadInProjectFromContext no longer passes branch/worktree context when the target project differs from the current context.
• Behavioral Change: dark mode backgrounds are now pure black by default, which may affect users with system-level dim/contrast adjustments.

📊 Macroscope summarized 70d022d. 31 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted

🗂️ Filtered Issues

No issues evaluated.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 884b49b7-44cc-4e0a-a502-44e868c0bf11

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/cool-black-redesign

---

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

[macroscopeapp]

Approvability

Verdict: Needs human review

2 blocking correctness issues found. Diff is too large for automated approval analysis. A human reviewer should evaluate this PR.

^{You can customize Macroscope's approvability policy. Learn more.}

[chiqors]

It would be great to add a Project Filter dropdown to the new sidebar v2 to help manage and isolate threads (i might be wrong to put comment in this PR, but just let you know).

Right now, as the number of threads grows, it gets difficult to focus on specific workstreams. Adding the ability to filter by project (e.g., project-a, project-b, project-c) would significantly improve navigation and reduce noise.

Dismissing prior approval to re-evaluate 70d022d

[macroscopeapp]

🟡 Medium components/SidebarV2.tsx:991

attemptSettle treats an interrupted settleThread result as a success: when result._tag === "Failure" and isAtomCommandInterrupted(result) is true, the failure branch is skipped, so the optimistic settledHolds entry stays in place, refreshArchivedThreadsForEnvironment runs, and navigateAfterSettle fires — navigating the user away from a thread whose settle was interrupted, not completed. Every other stateful call site in this file returns before its success-side effects when the result is an interrupted failure. The attemptSettle callback should remove the hold and skip navigation for any failure, while still suppressing the toast for interruptions.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/web/src/components/SidebarV2.tsx around line 991:

`attemptSettle` treats an interrupted `settleThread` result as a success: when `result._tag === "Failure"` and `isAtomCommandInterrupted(result)` is true, the failure branch is skipped, so the optimistic `settledHolds` entry stays in place, `refreshArchivedThreadsForEnvironment` runs, and `navigateAfterSettle` fires — navigating the user away from a thread whose settle was interrupted, not completed. Every other stateful call site in this file returns before its success-side effects when the result is an interrupted failure. The `attemptSettle` callback should remove the hold and skip navigation for any failure, while still suppressing the toast for interruptions.

[macroscopeapp]

🟡 Medium home/HomeScreen.tsx:655

The v2 list header renders every queued task in props.pendingTasks without filtering by selectedEnvironmentId or searchQuery, so when Thread List v2 is enabled, selecting a single environment still shows pending tasks from all environments, and pending tasks that don't match an active search stay visible. The grouped v1 list filters both ways via buildHomeThreadGroups, but the v2 header maps props.pendingTasks directly. Consider applying the same environmentId and search-query filters to props.pendingTasks before rendering the v2 header rows.

🚀 Reply "fix it for me" or copy this AI Prompt for your agent:

In file @apps/mobile/src/features/home/HomeScreen.tsx around line 655:

The v2 list header renders every queued task in `props.pendingTasks` without filtering by `selectedEnvironmentId` or `searchQuery`, so when Thread List v2 is enabled, selecting a single environment still shows pending tasks from all environments, and pending tasks that don't match an active search stay visible. The grouped v1 list filters both ways via `buildHomeThreadGroups`, but the v2 header maps `props.pendingTasks` directly. Consider applying the same `environmentId` and search-query filters to `props.pendingTasks` before rendering the v2 header rows.

[t3dotgg]

Closing because this branch bundles the old sidebar-v2 stack with the theme experiment. Sidebar v2 has landed through #4026 and later work; the remaining focused true-black direction is tracked in #3980.