docs(cli): document the /team slash command

[hongyi-chen]

What this feature does

/team switches the active team from inside the Warp Agent CLI. It opens a searchable list of the teams you belong to, marks the active one, and re-scopes the current session in place when you pick one. The desktop app has no equivalent in-place switch — its title-bar pill opens a new window for the chosen team instead — so the CLI behavior is genuinely different, not just a second entry point.

The command is GA and ungated: StaticCommand TEAM in app/src/search/slash_command_menu/static_commands/commands.rs:566 declares supported_surfaces: SlashCommandSurfaces::TuiOnly and Availability::ALWAYS, with no feature_flag. It dispatches SlashCommandKind::Team, which opens TuiTeamMenuModel (crates/warp_tui/src/team_menu.rs).

Why this was missing

The "Slash commands" table in agents/cli/reference.mdx presents itself as the complete list of CLI slash commands, and /team was the only GA, unflagged TUI-capable command absent from it.

The missing_docs audit could not see the gap, for two compounding reasons:

1. /team is mapped -> internal in the surface map. That entry is correct for the GUI slash-commands page — the command does not exist in the desktop app — but the CLI reference maintains its own table, which internal also suppresses.
2. The slash-command audit is repo-wide rather than surface-scoped (documented as a known limitation in SKILL.md): a command counts as covered when any page mentions it. This is the same blind spot that previously let /usage and /set-tab-color ship undocumented.

Caught by re-running the surface-scoped check that prior runs used to work around that limitation.

Worthiness verdict

Gate 1 — update an existing page. The knob is the nameable command /team itself, matching the /continue-locally worked example in .agents/references/docs-worthiness-criteria.md ("a nameable command, which is a knob, so Gate 1 carries it"). Gate 4 does not apply: the product surfaces the command in the slash menu and in the statusline team label, which opens the same list on click.

No content design plan: this adds a missing entry to an existing reference table, which .agents/references/content-design-plan.md lists under "When a plan can be skipped."

Changes

• Added the /team row to the slash commands table, in alphabetical position between /statusline and /theme.
• Added one paragraph alongside the existing /status and /usage explanations, covering the filter-and-Enter flow, the in-place re-scoping that differs from the desktop app, and the statusline affordance.

Validation

• npm run build — passes (383 pages, 381 markdown docs generated).
• style_lint --changed — one TONE-META-OPENER hit at line 252 ("This section covers common issues..."), pre-existing in the Troubleshooting section and untouched by this diff. Left for a style_lint sweep rather than widening scope.

Deferred findings from this run

The rest of the audit was already in sync. Full triage lives in the companion bookkeeping PR #657; deferrals worth naming here:

• /team's surface-map entry moves from internal to this page in docs: document completion, custom endpoint, and /team surfaces (+ missing_docs bookkeeping for v0.2026.08.26–v0.2026.09.02) #657. Eleven sibling TUI-only commands (/exit, /status, /api-keys, /vim-mode, /theme, /voice, /clear, /logout, /statusline, /reset-statusline, /natural-language-detection) are still mapped -> internal even though they are documented in this same table. Suppression behavior is identical either way, so this is a map-accuracy nit rather than a docs gap; deferred to avoid churning a PR already under review.
• Slash audit scoping. The repo-wide check that hid this gap remains unfixed in audit_docs.py. Until it is surface-scoped, doc_covered cannot be read as "documented in the right place."
• Two preview flags (ShellWidgetHandoff, HistorySearchRankingV2) and agents.warp_agent.other.usage_display_unit (dogfood, gated by PricingTransparency) fail Gate 0 and re-surface on promotion.
• Twelve new /factory* and screenshot-download API routes are x-internal: true in warp-server's canonical spec, so the publish filter strips them from the released OpenAPI. Not hand-documentable; re-check when the Factory REST API is published.
• Twenty-three potentially_stale_docs findings are terminology-only false positives, itemized and rejected in the ledger. The unresolved ai credits rule conflict is still flagged there for a human docs owner.

/cc @moirahuang

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 4, 2026 5:17pm UTC

[hongyi-chen]

This PR was generated with Warp.

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

  View origin