docs(tabs): document tab colors and the cycle-tab-color action

[hongyi-chen]

Summary

Tab colors were undocumented, and the 2026.08.13 release added a customizable action to cycle the active tab's color. This adds a Tab colors section to the Tabs page covering both.

Found by the missing_docs drift-watch audit (changelog item: "Added a customizable action to cycle the active tab color from a keybinding or the Command Palette").

Changes

• How to set and clear a tab's color from the tab context menu.
• What happens when the tab belongs to a group (the group's color changes, so all its tabs change together).
• The Cycle current tab color action (workspace:cycle_active_tab_color), which has no default shortcut and is reachable from the Command Palette or a custom keybinding.
• A pointer to the directory_tab_colors setting for automatic per-directory colors.

Verification

• Action name and label from app/src/workspace/mod.rs; behavior (group-aware cycling, wrap back to no color) from app/src/workspace/view.rs; the context-menu color row, including its "Default (no color)" entry and toggle-off behavior, from app/src/tab.rs.
• npm run build passes; style_lint --changed reports no new issues.

Deferred findings from this audit run

• Remaining 2026.08.13 changelog items reviewed and judged already covered or not doc-worthy: /connect-grok (already in agents/cli/models-and-usage.mdx), repository-qualified skill references (already in the CLI reference), new shell completions (vagrant, openssl, yc, journalctl) and the run-platform icon, which have no per-item doc surface.
• 44 Factory REST endpoints absent from the released OpenAPI spec are mapped internal in the companion bookkeeping PR.
• 30 low-severity terminology/staleness findings are owned by the style_lint skill.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 26, 2026 9:39pm

[hongyi-chen]

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

  View origin

[warp-factories]

Your GitHub account is not connected to Warp. Connect it here.

[warp-for-oss]

@hongyi-chen

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

Overview

This PR adds a Tab colors section to the Tabs documentation, covering manual tab colors, group behavior, the keyless workspace:cycle_active_tab_color action, and the related directory_tab_colors setting. The behavior described matches the referenced implementation, and there are no security or spec-alignment blockers.

Concerns

• Two small docs-style issues can be cleaned up inline: one UI option should use the exact label/formatting, and one contextual callout should use the note style instead of tip.

Verdict

Found: 0 critical, 0 important, 2 suggestions

Approve with nits

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

💡 [SUGGESTION] Use the exact UI label and format it as a UI option.

Suggested change

	To remove a color, right-click the tab and click the same color again, or pick the default (no color) option.
	To remove a color, right-click the tab and click the same color again, or select **Default (no color)**.

[warp-for-oss]

💡 [SUGGESTION] This callout points to related reference material rather than an expected outcome, so use a note callout.

Suggested change

	:::tip
	:::note

[warp-agent-staging]

Approved after reviewing the documentation diff and verifying the client action and settings names, UI-reference validation, npm run typecheck, npm run build, and the green GitHub CI checks. Local npm run lint was unavailable because the repository does not vendor the Trunk binary.