Skip to content

docs(cli): context (rules, skills, MCP) - #400

Closed
hongyi-chen wants to merge 2 commits into
hyc/launch-clifrom
hyc/launch-cli-cli-context
Closed

docs(cli): context (rules, skills, MCP)#400
hongyi-chen wants to merge 2 commits into
hyc/launch-clifrom
hyc/launch-cli-cli-context

Conversation

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Pages changed

  • src/content/docs/cli/context.mdx — agent context in the Warp CLI (feature-doc type)

Features covered

  • Project context pickup — working-directory context; cd re-scopes rules and skills to the session's working directory; AGENTS.md/WARP.md project rules; global ~/.agents/AGENTS.md rules; cross-links agent-platform/capabilities/rules
  • Skills/skills menu (search, select, insert /skill-name for extra instructions), direct /skill-name invocation with arguments, skills matching in the slash menu; cross-links agent-platform/capabilities/skills
  • Bundled skills/modify-settings (schema-guided settings edits) and /tui-migrate-setup (migrate compatible settings + global MCP definitions from the Warp app; no credentials copied)
  • MCP/mcp management view (transport, status, tool counts; start/stop/retry; OAuth reopen + log out), CLI-specific global .mcp.json config (same mcpServers format, auto-reloaded, servers auto-start after login); cross-links agent-platform/capabilities/mcp

Dropped/unconfirmed

  • Project-scoped MCP servers — not shipped in the CLI: TUI-mode MCP discovery is explicitly limited to the CLI's global Warp config (project + third-party provider discovery is deferred "to a later phase" in code). The page instead carries a note that only the global config file is read.
  • MCP import/discovery from other tools — fast follow, not landed; excluded per plan.

Validation

  • npm run build passes (363 pages, no errors)

Suggested reviewer(s): Kevin, moira

Co-Authored-By: Oz oz-agent@warp.dev

Fill in src/content/docs/cli/context.mdx with launch content:
- Working-directory context and AGENTS.md/WARP.md project rules pickup,
  plus global ~/.agents/AGENTS.md rules
- /skills menu and direct /skill-name invocation
- Bundled skills: /modify-settings and /tui-migrate-setup
- /mcp management view, global JSON config, server statuses and actions

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jul 28, 2026
@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 28, 2026 9:47pm

Request Review

@oz-for-oss

oz-for-oss Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

@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 /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR replaces the placeholder CLI context page with documentation for project rules, skills, bundled skills, and MCP server management. I found one blocking issue in the new page: it uses a content variable key that does not match the repository's documented src/data/vars.ts key for the CLI name, which will break or bypass the intended product-name variable system.

Concerns

  • src/content/docs/cli/context.mdx uses {VARS.WARP_CLI} throughout, but the docs repository guidance defines the CLI product variable as WARP_AGENT_CLI; replace the new page's body references with {VARS.WARP_AGENT_CLI} or add an intentionally named variable if the key has changed on the base branch.
  • No approved spec context was provided, so I did not identify spec-drift findings.
  • No security-specific findings were identified in this documentation-only diff.

Verdict

Found: 1 critical, 0 important, 0 suggestions

Request changes

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

Powered by Oz

{/* TODO(cli-context): draft per drafts/warp-cli-launch-plan.md — "cli/context.mdx" section. Feature-doc content type. */}

The {VARS.WARP_CLI} documentation for this page is in progress.
The {VARS.WARP_CLI} gives its agent the same layered context system as the Warp app: your working directory, project rules, skills, and MCP servers. All of it follows the directory you're working in, so the agent's knowledge stays scoped to the project at hand.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚨 [CRITICAL] {VARS.WARP_CLI} does not match the repository's documented CLI variable key (WARP_AGENT_CLI), so this page should use {VARS.WARP_AGENT_CLI} consistently or add the intended variable before merge.

{{WARP_CLI}} tokens are not substituted in MDX frontmatter, so replace
them with the literal product name in title and description. Body-prose
{VARS.WARP_CLI} usages are unchanged.

Co-Authored-By: Oz <oz-agent@warp.dev>
@hongyi-chen

Copy link
Copy Markdown
Collaborator Author

Content absorbed into #401 (customization: settings, themes, statusline, rules, skills, MCP) as part of consolidating the CLI docs from 13 pages to 9. The context.mdx stub will be deleted in the integration commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant