docs: complete the built-in Slash Commands table

[hongyi-chen]

What this feature does

Four GA Slash Commands were missing from the built-in Slash Commands table on agents/capabilities/slash-commands.mdx, a page that presents that table as the complete list ("Warp currently supports the following built-in Slash Commands"). Three of them (/continue-locally, /handoff, /remote-control) are documented on their own feature pages but absent from the reference table. /set-tab-color was undocumented anywhere in the docs.

Summary

missing_docs drift-watch for stable v0.2026.08.26.17.59.stable_01, exhaustive pass.

The audit's slash command check reported 0 findings because, as the skill documents, that check is repo-wide rather than surface-scoped: a command counts as covered when any page mentions it. This run re-ran the check scoped by the registry's own SlashCommandSurfaces field (GuiOnly / TuiOnly / GuiAndTui), which is the same blind spot that previously let /usage ship undocumented for CLI users.

Scoped results:

• Warp Agent CLI — all 32 TUI-capable commands are covered under agents/cli/. Clean.
• GUI — 4 GA commands absent from the reference table. /docker-sandbox is also absent but is deliberately mapped -> internal in the surface map, so it stays out.

Changes

src/content/docs/agents/capabilities/slash-commands.mdx

Four rows added in alphabetical position:

• /continue-locally — fork the current cloud agent conversation into a local Warp session
• /handoff — hand the current local conversation off to a cloud agent (marked *, since cloud agent runs consume credits)
• /remote-control — publish the current third-party CLI agent session to the cloud
• /set-tab-color — set the current tab's color

src/content/docs/terminal/windows/tabs.mdx

One paragraph under Tab colors > Set a tab's color, giving /set-tab-color as an alternative to the right-click flow, alongside the existing right-click and cycle-color entry points.

Content design plan

No plan required. Per .agents/references/content-design-plan.md → "When a plan can be skipped", this is adding a missing entry to an existing reference table or list where the surrounding page already establishes the reader and the format. The tabs.mdx addition is a second entry point for a flow the section already documents, not a new concept.

Worthiness verdicts

All four pass Gate 1 (configurable — a nameable command is a knob) and resolve to update an existing page, the preferred outcome. /continue-locally is in fact the worked example in .agents/references/docs-worthiness-criteria.md making exactly this point: it fails Gate 4's second condition because the menu surfaces it, but Gate 1 carries it anyway.

Gate 0 verified against app/src/search/slash_command_menu/static_commands/commands.rs: all four are in the public warpdotdev/warp repo and carry no feature_flag, so all are GA.

Unverified claims

None. Command names, descriptions, surfaces, and argument shapes are verified against app/src/search/slash_command_menu/static_commands/commands.rs. The /set-tab-color color list comes from TAB_COLOR_OPTIONS in app/src/ui_components/color_dot.rs (red, green, yellow, blue, magenta, cyan) plus the none sentinel in SET_TAB_COLOR_HINT.

Deferred findings

Recorded in the bookkeeping added to #657. Nothing in this run's exhaustive sweep is dropped silently:

• --weak-coverage (81 low findings) — no docs. Every one is a mapped, curated surface-map entry whose page simply doesn't contain a phrase derived from the internal flag name. Spot-verified against code and docs: FullScreenZenMode → workspace_decoration_visibility is documented; SuggestedRules → rule_suggestions_enabled is documented and rules.mdx describes the behavior; SharedWithMe → warp-drive sharing is documented; tab flags → tabs.mdx covers groups, dragging, and colors. One map-target nit fixed in the bookkeeping: KittyImages pointed at full-screen-apps.mdx, but the Kitty image protocol is documented on files-and-links.mdx.
• 23 potentially_stale_docs — no docs. Verified line by line rather than dismissed in bulk. "AI credits" is the deliberate name of the inference bucket, contrasted throughout with compute credits and platform credits; "Warp AI" hits are verbatim telemetry event names in privacy.mdx plus one historical FAQ; "Warp Terminal" hits are the distinguishing usage the style guide allows. Pure wording questions belong to style_lint.
• 2 /factory API routes, 3 new settings, usage_display_unit, NativeShellCompletions, and the 15 changelog items — already triaged by the earlier run for this same release; verdicts re-verified and left standing in docs: document completion and custom endpoint settings keys (+ missing_docs bookkeeping for v0.2026.08.26) #657.
• /docker-sandbox — no docs; already mapped -> internal.

/cc @moirahuang @vkodithala

Co-Authored-By: Warp agent@warp.dev

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 2, 2026 1:02am UTC

[hongyi-chen]

This PR was generated with Warp.

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

  View origin

[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 updates the Slash Commands reference table with four missing built-in commands and adds /set-tab-color as another tab color entry point. The command coverage and internal links match existing docs; no approved spec context was provided, and the security pass found no code or configuration surface.

Concerns

• tabs.mdx adds an em dash in a procedural instruction, which violates the docs style guide's rule against em dashes in procedural or instructional text.
• No security findings.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

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]

⚠️ [IMPORTANT] The style guide forbids em dashes in procedural or instructional text; use a colon before the argument list.

Suggested change

	You can also set the color without leaving the input. Run the [`/set-tab-color`](/agents/capabilities/slash-commands/) Slash Command with the color you want — `red`, `green`, `yellow`, `blue`, `magenta`, `cyan`, or `none` to clear it. For example, `/set-tab-color blue`.
	You can also set the color without leaving the input. Run the [`/set-tab-color`](/agents/capabilities/slash-commands/) Slash Command with the color you want: `red`, `green`, `yellow`, `blue`, `magenta`, `cyan`, or `none` to clear it. For example, `/set-tab-color blue`.