Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion .agents/references/terminology.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,9 @@ For the summary of the most critical terms (core features, Automation Platform t
- **Tab Configs** — Reusable TOML-based tab layout definitions that launch preconfigured terminal sessions.
*Usage note:* Capitalize as a feature name.

- **Launch Configuration** / **Launch Configurations** — The legacy, YAML-based way to save a configuration of windows, tabs, and panes. Replaced by Tab Configs; existing Launch Configurations still work but aren't being extended.
*Usage note:* Capitalize as a feature name, including in headings ("Creating a Launch Configuration"). Use "Tab Configs" for new content.

- **Vertical Tabs** — The sidebar-based tab management panel that replaces the horizontal tab bar.
*Usage note:* Capitalize as a feature name.

Expand Down Expand Up @@ -108,6 +111,12 @@ For the summary of the most critical terms (core features, Automation Platform t
- **Active AI** — The feature that proactively surfaces fixes and next actions based on terminal errors, inputs, and outputs. Covers Prompt Suggestions, Next Command predictions, and Suggested Code Diffs.
*Usage note:* Always capitalize "Active AI" — it is a proper feature name and the label of the Settings toggle. Write the full capability as **Active AI Recommendations**, matching the page title. Lowercase the following word only when it is a plain common noun rather than part of the name, as in "Active AI features" or "the Active AI toggle".

- **Computer Use** — The capability that lets agents interact with a desktop environment (screenshots, clicks, typing) inside a sandboxed cloud environment.
*Usage note:* Capitalize as a feature name, including in headings ("Enabling Computer Use", "How Computer Use works").

- **Full Terminal Use** — The capability that lets an agent attach to and drive interactive terminal programs (for example `psql`, `vim`, a dev server) by reading live PTY output.
*Usage note:* Capitalize as a feature name, including in headings.

## Coding terms (Warp features)

- **Code** — Warp's coding experience for agent-assisted changes (editing, diffs, code review).
Expand Down Expand Up @@ -164,7 +173,7 @@ catches the literal, `platform-determiner` catches a missing article.
*Usage note:* In prose the term takes the definite article — "the Warp Agent". Reserve the bare form for headings, sidebar labels, page titles, and the Settings path. "Runs the Warp Agent" reads correctly; "runs Warp Agent" reads as a different product.
- **The Automation Platform is the platform, not the agent.** Never introduce it as "Warp's agent" or equate the two. The Automation Platform runs and coordinates agents; the Warp Agent is the agent.
- **Warp Agent CLI** — The standalone terminal program (the `warp` binary) that runs the Warp Agent in any terminal, including over SSH and on machines without the Warp app. Documented at `/agents/cli/`.
*Usage note:* Distinct from the Oz CLI (the `oz` binary), which runs and manages cloud agents. At the next launch (approximately August 18, 2026) the Oz CLI is retired and wrapped into the Warp Agent CLI, leaving a single CLI under this name. Until that ships, keep the two clearly separate in prose; afterwards, "Warp Agent CLI" covers both.
*Usage note:* Distinct from the Oz CLI (the `oz` binary), which runs and manages cloud agents. The Oz CLI is retired and wrapped into the Warp Agent CLI on 2026-09-15, matching the `oz` binary holdout in "What still says Oz" below — not the 8/18 platform rename. Until that ships, keep the two clearly separate in prose; afterwards, "Warp Agent CLI" covers both. `oz` commands themselves remain supported through the end of September 2026; the successor `warp` CLI commands for CLI-scripted workflows (environments, secrets, integrations, schedules) haven't been defined yet.
- **Automation Platform** — Warp's programmable platform for running and coordinating agents at scale
- There is typically one Warp environment per user session. The Automation Platform can run many agents concurrently, across machines, repos, and teams.

Expand Down Expand Up @@ -284,6 +293,9 @@ Not every "Oz" in the docs is stale. These are deliberate and correct until
- **Automation Platform** — Warp's cloud agent platform, covering environments, integrations, orchestration, self-hosting, and the Agent API/SDK. Renamed from "Oz" on 2026-08-18.
*Usage note:* See "Automation Platform terminology" above for the full entry and the article rule. Always write it as `{VARS.WARP_AUTOMATION_PLATFORM}` / `{{WARP_AUTOMATION_PLATFORM}}`, never as a literal string, so a future rename stays a one-line change.

- **Direct backend** — The self-hosted worker backend that runs cloud agent tasks directly on the worker host, without Docker or Kubernetes. One of three self-hosting backends alongside the Docker and Kubernetes backends.
*Usage note:* Capitalize "Direct" as part of the compound proper term, including in headings ("Start the worker with the Direct backend"); lowercase "backend" as the common noun.

## Warp Factories terminology

### The product/instance rule
Expand Down Expand Up @@ -362,6 +374,9 @@ Docs match the screen; the fix belongs in the app.
- **command-line** — hyphenated when used as an adjective
- **Git repository** or **repo** — not "git repository" (capitalize "Git")
- **macOS** — not "Mac OS" or "Mac"
- **Zero Data Retention (ZDR)** — Warp's agreements with contracted LLM providers not to train on or retain customer data. Capitalize as a proper term, including in headings ("Zero Data Retention (ZDR)"); keep the "(ZDR)" acronym on first mention in a section.
- **SSO (Single Sign-On)** — Authentication through an organization's identity provider (Okta, Microsoft Entra ID, Google Workspace, or any SAML 2.0/OIDC provider). Always capitalize the acronym "SSO"; capitalize "Single Sign-On" when spelled out as the feature name.
- **Bring Your Own LLM (BYOLLM)** — Warp Enterprise's routing of agent inference through a customer's own cloud infrastructure (AWS Bedrock or Google Cloud via Gemini Enterprise). Capitalize as a proper feature name, including in headings; keep the "(BYOLLM)" acronym on first mention in a section. Distinct from BYOK (Bring Your Own API Key), a self-serve, user-level feature.

## Branded and informal terms

Expand Down Expand Up @@ -407,3 +422,6 @@ Docs match the screen; the fix belongs in the app.
- **GitHub App** — GitHub's installation/auth mechanism used for repo access in integrations
- **Linear** — capitalize
- **Slack** — capitalize
- **Bitbucket Data Center** — Atlassian's official self-hosted Bitbucket edition name (alongside Bitbucket Server and Bitbucket Cloud). Capitalize all three words, including in headings ("Bitbucket Data Center / Server").
- **Workload Identity Pool and Provider** — GCP's IAM resources for federating external identities. Capitalize as GCP's official term, including in headings.
- **Workload Identity Federation** — GCP's mechanism for granting external identities access without a long-lived service account key. Capitalize as GCP's official term, including in headings.
8 changes: 3 additions & 5 deletions .agents/skills/missing_docs/references/feature_surface_map.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,9 @@ CodeFindReplace -> src/content/docs/code/code-editor/find-and-replace.md
VimCodeEditor -> src/content/docs/code/code-editor/code-editor-vim-keybindings.md
McpServer -> src/content/docs/agents/capabilities/mcp.mdx
McpOauth -> src/content/docs/agents/capabilities/mcp.mdx
# Factory MCP (the hosted MCP endpoint agents use to work with a factory) is
# GA and documented on the Factory MCP page and related factories/* pages.
FactoryMcp -> src/content/docs/factories/factory-mcp.mdx
ImageAsContext -> src/content/docs/agents/local-agents/agent-context/images-as-context.mdx
SelectionAsContext -> src/content/docs/agents/local-agents/agent-context/selection-as-context.mdx
DiffSetAsContext -> src/content/docs/agents/local-agents/agent-context/selection-as-context.mdx
Expand Down Expand Up @@ -242,11 +245,6 @@ OscHyperlinks -> src/content/docs/terminal/more-features/files-and-links.mdx
# MCP reference (and the cloud agent MCP schema page).
WellKnownMcpIds -> src/content/docs/reference/cli/mcp-servers.mdx

# Auto-attaches the Warp-hosted Factory MCP server to agent sessions with no
# manual setup. Promoted dogfood -> GA; that zero-config behavior is documented
# in the "Connect and authenticate" section of the Factory MCP page.
FactoryMcp -> src/content/docs/factories/factory-mcp.mdx

## CLI commands -> doc pages

# Top-level Oz CLI commands
Expand Down
11 changes: 8 additions & 3 deletions .agents/skills/style_lint/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,14 +85,19 @@ This skill checks broader formatting and terminology. The `validate_ui_refs` ski

## Tests

Three checks have regression suites, because each is a narrow rule where the
hard part is not firing on legitimate text. Run them after touching any of
these checks:
Several checks have regression suites, because each is a narrow rule where the
hard part is not firing on legitimate text. Run the relevant one(s) after
touching the corresponding check:

```bash
python3 .agents/skills/style_lint/test_platform_determiner.py
python3 .agents/skills/style_lint/test_factory_proper_noun.py
python3 .agents/skills/style_lint/test_hardcoded_var_exemptions.py
python3 .agents/skills/style_lint/test_header_case_sentence_boundary.py
python3 .agents/skills/style_lint/test_product_casing_word_boundary.py
python3 .agents/skills/style_lint/test_proper_feature_names_third_party.py
python3 .agents/skills/style_lint/test_tone_checks.py
python3 .agents/skills/style_lint/test_context_aware_terminology.py
```

## Dependencies
Expand Down
Loading
Loading