Repository navigation
feat(workspace): rename and color workspaces from the sidebar and CLI - #702
Merged
Merged
Conversation
Replace the unused colorTone enum with a workspace color: "auto" or one of the theme's lane colors (red, amber, lime, green, cyan, blue, violet, pink). Migration v10 adds the color column (every workspace starts as "auto") and drops color_tone. - Sidebar row menu: Rename… (inline) and Color ›. The color tints the row's folder icon, so it is not mistaken for the connection status dot. - Agent view uses the chosen color, falling back to the id-hash lane color for "auto". - CLI: `nexus workspace edit <ws> --name/--color`, `workspace add --color`, `color` in --json. New consent kind workspaceEdit. - docs/CLI.md and the agent context note updated. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Only add the color column. Older builds that open the same database still insert into color_tone, so dropping it would break adding a workspace after a rollback. Nothing reads or writes it now; it is kept for compatibility. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Nov 19, 2026
Merged
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.
Summary
A workspace had a
colorTone(subdued, default, prominent, pinned) that only storage and the IPC contract knew; no screen or CLI set or showed it, and the sidebar had no way to rename a workspace. This turns it into a color the user picks and adds rename.color:autoor one of eight colors mapped in order to the git lane tokens 0–7.autokeeps today's look (the agent view's hash color).auto.nexus workspace edit <workspace> [--name N] [--color C]andworkspace add --color;--jsonoutput includescolor. Editing another workspace asks under a new consent kind,workspaceEdit. A task (worktree) follows its parent's color and is refused. docs/CLI.md and the agent context are updated.color TEXT NOT NULL DEFAULT 'auto'. Every existing workspace starts asauto. The oldcolor_tonecolumn stays, unused, so an older build opening the same database can still insert rows.Tests
auto, an older build's insert still reads asauto) and color round trip instorage-global.test.ts.workspace editandadd --colorargument handling inworkspace-sidebar.test.ts.bun run typecheck,bun run check:ci, unit plus storage and reorder integration tests (4471).Manual check
Rename from the context menu (Korean IME Enter included), pick colors in light and dark themes, set Auto back, run
nexus workspace edit … --colorand see the sidebar update; open an existing database once and check the migration.🤖 Generated with Claude Code