v0.9.4: dark-first chrome, glass surfaces, no terminal or side panels#51
Merged
ojowwalker77 merged 2 commits intoJul 21, 2026
Merged
Conversation
Chrome - Border radius anchored on the Bonsai chrome radius (--radius: 0.75rem); the whole ladder derives from that one knob. - Palette moved to #090909 canvas / #141414 elevated, warm-neutral ink ramp. - Liquid glass: one blur/saturate recipe shared by the shell, sidebar and composer, with a window-transparency slider in Appearance. - Sidebar reads as the same pane of glass as the composer; rows carry a single identity glyph (PR badge > terminal > provider) trailing the title. Appearance - Light mode is back, with a Follow System / Light / Dark control. The chrome palette now swaps to the variant's default instead of rendering the dark palette under a light canvas. - UI density and the background-image picker are no longer configurable. Removals - Embedded terminal UI, the right dock, and every side panel (diff panel, editor workspace, file explorer, review tree, message trail). - Skills settings panel. - The PTY layer stays: project dev servers run through it.
Typecheck and the unit suites were still exercising APIs this branch deleted. Every change here updates or drops a stale expectation; no production behavior moved. - Keybindings (contracts, server, web): fixtures no longer reference the retired `terminal.*` / `chat.newTerminal` commands, and the web DEFAULT_BINDINGS mirror the server defaults again (which carry no `when` guards). Tests that only covered terminal-focus gating are gone; the generic when-expression and physical-key coverage is kept. - Composer draft store, prompt-history snapshots, thread bootstrap, message context, timeline heights: dropped `terminalContexts` and `entryPoint` from fixtures and assertions. - ChatView browser/logic tests: removed the terminal RPC mocks, the terminal-pill tests, and the project-script runs (the script path is a stub since it needs a terminal). - Chat header: `diff` is no longer a control id. - Deleted `lib/fileDiffTree.ts` + test — it only fed the removed review file tree panel. - Reverted the `.ts` import extension in teacodeEnvironmentBootstrap that a local dev-runner workaround left behind; it broke `bun typecheck`. - Refreshed the theme assertions stranded by the palette change.
ojowwalker77
deleted the
teacode/what-is-our-current-border-radius-thruout-app
branch
July 24, 2026 21:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chrome
--radius: 0.75rem); the whole ladder derives from that one knob.#090909canvas /#141414elevated, with a warm-neutral ink ramp.Appearance
resolveThemePackForVariant) instead of rendering the dark palette under a light canvas.Removals
Verification
bun fmt,bun lint,bun typecheckclean. Two assertions intheme.logic.test.tscarry stale expected values from the palette change (opaqueWindows: true,rgb(47, 48, 53)) and still need updating.