diff --git a/.agents/references/terminology.md b/.agents/references/terminology.md index aea79cf..addeab3 100644 --- a/.agents/references/terminology.md +++ b/.agents/references/terminology.md @@ -69,8 +69,8 @@ For the summary of the most critical terms (core features, Oz terms, terms to av ## Agent concepts -- **Ambient Agents** — Oz agents that run automatically in the background on a schedule or trigger, without interactive input. - *Usage note:* Capitalize as a feature/section name. Use lowercase "ambient agents" only when describing the generic concept of agents running in the background. +- **Cloud Agents** — Agents that run in the cloud on a schedule, trigger, or integration, without interactive input. Managed by the Oz Platform. + *Usage note:* Use lowercase "cloud agents" in most contexts. Capitalize as "Cloud Agents" only when referring to the product section or feature name. - **Agent Profiles** — Saved configurations that define how an Agent runs (for example, permissions and model selection). *Usage note:* Use when describing "choose how your Agent behaves." @@ -121,33 +121,33 @@ For the summary of the most critical terms (core features, Oz terms, terms to av ## Oz terminology -### Oz vs Warp +### Warp Agent vs Oz -- **Warp** is the terminal and coding surface -- **Oz** is Warp's programmable agent for running and coordinating agents at scale +- **Warp Agent** — Warp's built-in agent harness. Use "Warp Agent" when specifically referring to the built-in harness, especially when contrasting with third-party agents (Claude Code, Codex, etc.), or when referencing the Settings label (**Settings** > **Agents** > **Warp Agent**). +- **Oz** — Warp's programmable platform for running and coordinating agents at scale - There is typically one Warp environment per user session. Oz can run many agents concurrently, across machines, repos, and teams. -### Core Oz terms +### Core terms -- **Environment** — The execution context for an Oz agent, including repo access, dependencies, secrets, compute, and runtime configuration. +- **agent** — A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Agents can be local or cloud. Use lowercase "agent" in most contexts; use "Warp Agent" only when referring specifically to the built-in Warp harness. + *Example:* Launch an agent from the CLI, the web app, an API or SDK, or directly inside Warp. -- **Oz** — Warp's programmable agent for running and coordinating agents at scale. - *Example:* With Oz, you can orchestrate multiple agents to automate and parallelize complex workflows. +- **cloud agent** — An agent running in the cloud, from a trigger, schedule, or started from someone's local machine. -- **Oz agent** — A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Agents can be local or cloud, and interactive or ambient. - *Example:* Launch an Oz agent from the CLI, the web app, an API or SDK, or directly inside Warp. +- **conversation** — An interactive execution lifecycle within the Warp Terminal, regardless of whether it's local or in the cloud. -- **Oz cloud agent** — An Oz agent running in the cloud, from a trigger, schedule, or started from someone's local machine. Cloud agents can be interactive or ambient. +- **Environment** — The execution context for an agent, including repo access, dependencies, secrets, compute, and runtime configuration. -- **Oz conversation** — An interactive execution lifecycle within the Warp Terminal. An Oz conversation is interactive, started in the terminal regardless of whether it's local or in the cloud. +- **Oz** — Warp's programmable platform for running and coordinating agents at scale. + *Example:* With Oz, you can orchestrate multiple agents to automate and parallelize complex workflows. - **Oz dashboard** — The app surface to manage all Oz runs, unified across the Warp app and web. -- **Oz run** — A single execution lifecycle of an Oz agent, including actions, outputs, and logs. An Oz run is always ambient and cloud-based. +- **Oz run** — A single execution lifecycle of an agent, including actions, outputs, and logs. An Oz run is always cloud-based. -- **Oz subagent** — A child Oz agent created by a parent Oz agent to parallelize or delegate work. +- **Oz web app** — The web app for configuring agents and managing runs. -- **Oz web app** — The web app for configuring Oz agents and managing runs. +- **subagent** — A child agent created by a parent agent to parallelize or delegate work. ### Oz CLI commands @@ -155,8 +155,8 @@ For the summary of the most critical terms (core features, Oz terms, terms to av - `oz agent run-cloud` — Run an adhoc cloud agent - `oz environment create/list/get/update/delete` — CRUD on environments - `oz integration create` — Install integrations (Slack, Linear) -- `oz run list/get` — Get info on ambient agent runs -- `oz schedule create/list/get/update/delete` — CRUD on scheduled ambient agents +- `oz run list/get` — Get info on cloud agent runs +- `oz schedule create/list/get/update/delete` — CRUD on scheduled cloud agents - `oz secret create/list/update/delete` — CRUD on Warp-managed secrets ### Preferred phrases @@ -167,11 +167,16 @@ For the summary of the most critical terms (core features, Oz terms, terms to av ### Terms to avoid -- ❌ "Ozzies" → Use "Oz agents", "instances", or "Oz subagents" -- ❌ "Deploying an Oz" → Use "Deploying an Oz agent" -- ❌ "The Oz Agent" → Use "An Oz agent" or "A parent Oz agent" -- ❌ "Oz is running" → Use "An Oz agent is running" or "A run is in progress" +- ❌ "Oz agent" / "Oz agents" → Use "agent" / "agents" (or "Warp Agent" / "Warp Agents" when referring to the built-in harness) +- ❌ "Oz cloud agent" → Use "cloud agent" +- ❌ "Oz subagent" → Use "subagent" +- ❌ "Oz conversation" → Use "conversation" +- ❌ "Ozzies" → Use "agents", "instances", or "subagents" +- ❌ "Deploying an Oz" → Use "Deploying an agent" +- ❌ "The Oz Agent" → Use "the agent" or "the Warp Agent" +- ❌ "Oz is running" → Use "An agent is running" or "A run is in progress" - ❌ "AI agents" → Use "agents" (the "AI" prefix is redundant) +- ❌ "Ambient Agents" / "ambient agents" → Use "Cloud Agents" / "cloud agents" ("ambient" is no longer a product term; acceptable only in code identifiers like `AmbientAgentConfig`) ## Platform terms diff --git a/.agents/rules/oz-style-guidelines.md b/.agents/rules/oz-style-guidelines.md index 561ab24..99675b2 100644 --- a/.agents/rules/oz-style-guidelines.md +++ b/.agents/rules/oz-style-guidelines.md @@ -34,46 +34,52 @@ When writing about Warp products or features, tie back to at least one of these ## Oz Terminology and Capitalization -### Core Oz Terms +### Core Terms - **Oz** - Warp's programmable platform for running and coordinating agents at scale -- **Oz agent** - A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Can be local or cloud, interactive or ambient -- **Oz cloud agent (general)** - An Oz agent running in the cloud, from a trigger, schedule, or started from someone's local machine -- **Oz subagent** - A child Oz agent created by a parent Oz agent to parallelize or delegate work -- **Oz run** - A single execution lifecycle of an Oz agent, including actions, outputs, and logs. Always ambient and cloud-based -- **Oz conversation** - An interactive execution lifecycle within Warp terminal, regardless of whether it's local or in the cloud -- **Environment** - The execution context for an Oz agent, including repo access, dependencies, secrets, compute, and runtime configuration +- **Warp Agent** - Warp's built-in agent harness. Use "Warp Agent" when specifically referring to the built-in harness, especially when contrasting with third-party agents (Claude Code, Codex, etc.) +- **agent** - A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Can be local or cloud. Use lowercase "agent" in most contexts. +- **cloud agent** - An agent running in the cloud, from a trigger, schedule, or started from someone's local machine +- **subagent** - A child agent created by a parent agent to parallelize or delegate work +- **Oz run** - A single execution lifecycle of an agent, including actions, outputs, and logs. Always cloud-based +- **conversation** - An interactive execution lifecycle within Warp terminal, regardless of whether it's local or in the cloud +- **Environment** - The execution context for an agent, including repo access, dependencies, secrets, compute, and runtime configuration - **Oz dashboard** - The app surface to manage all Oz runs, unified across the Warp app and web -- **Oz web app** - The web app for configuring Oz agents and managing runs +- **Oz web app** - The web app for configuring agents and managing runs ### Capitalization Rules **Cloud agents:** -- **Product** (capitalized): "Oz Cloud Agent" or "Oz Cloud Agents" when referring to Warp's specific product feature - - "Oz Cloud Agents send you session sharing links" - - "Launch an Oz Cloud Agent from the CLI" +- **Product** (capitalized): "Cloud Agent" or "Cloud Agents" when referring to Warp's specific product feature + - "Cloud Agents send you session sharing links" + - "Launch a Cloud Agent from the CLI" - **Concept** (lowercase): "cloud agent" or "cloud agents" when referring to the general concept - "Running cloud agents lets you escape the limits of your local machine" - "The cloud agent architecture enables scalability" **Other terms:** - Use "agents" not "AI agents" (redundant) +- Use "agent" not "Oz agent" (deprecated); use "Warp Agent" only when referring to the built-in harness - "Skills" not "skills" (capitalized) - "AGENTS.md" not "agents.md" (all caps) ### Terms to Avoid ❌ **Don't use:** -- "Ozzies" → Use "Oz agents", "instances", or "Oz subagents" -- "Deploying an Oz" → Use "Deploying an Oz agent" -- "The Oz Agent" → Use "An Oz agent" or "A parent Oz agent" -- "Oz is running" → Use "An Oz agent is running" or "A run is in progress" +- "Oz agent" / "Oz agents" → Use "agent" / "agents" (or "Warp Agent" / "Warp Agents" when referring to the built-in harness) +- "Oz cloud agent" → Use "cloud agent" +- "Oz subagent" → Use "subagent" +- "Oz conversation" → Use "conversation" +- "Ozzies" → Use "agents", "instances", or "subagents" +- "Deploying an Oz" → Use "Deploying an agent" +- "The Oz Agent" → Use "the agent" or "the Warp Agent" +- "Oz is running" → Use "An agent is running" or "A run is in progress" - "AI agents" → Use "agents" - "Warp's terminal" → Use "Warp" or "Warp terminal" ### Important Context About Oz -**All agents in Warp are Oz agents**, whether they are running in the cloud or running locally. +Oz is Warp's programmable platform for running and coordinating agents at scale, whether they are running in the cloud or running locally. Oz exists to take agent workflows beyond a single prompt or a single laptop, making them scalable, autonomous, collaborative, and auditable. diff --git a/.agents/skills/answer_question/SKILL.md b/.agents/skills/answer_question/SKILL.md index 1029e01..e7a1757 100644 --- a/.agents/skills/answer_question/SKILL.md +++ b/.agents/skills/answer_question/SKILL.md @@ -49,7 +49,7 @@ Both repos are indexed for `codebase_semantic_search`. Use `grep` for exact symb - Be direct and matter-of-fact. Answer the question, don't summarize the docs. - Be comprehensive — cover what the user needs to fully understand the answer — but don't pad with tangential information. -- Use Warp's standard terminology from `AGENTS.md` and the full glossary in `.warp/references/terminology.md`. Key rules: capitalize feature names (Agent, Agent Mode, Warp Drive, Codebase Context), use "Oz agent" not "Ozzie" or "the Oz Agent", use "credits" not "AI credits." +- Use Warp's standard terminology from `AGENTS.md` and the full glossary in `.warp/references/terminology.md`. Key rules: capitalize feature names (Agent, Agent Mode, Warp Drive, Codebase Context), use "agent" (generic) or "Warp Agent" (built-in harness) not "Oz agent" or "Ozzie", use "credits" not "AI credits." - If the docs do not cover the topic, say so honestly. Do not guess or fabricate information. ### 4. Generate doc links diff --git a/.agents/skills/missing_docs/references/feature_surface_map.md b/.agents/skills/missing_docs/references/feature_surface_map.md index ccf0eb0..7698fac 100644 --- a/.agents/skills/missing_docs/references/feature_surface_map.md +++ b/.agents/skills/missing_docs/references/feature_surface_map.md @@ -8,7 +8,7 @@ Lines starting with `#` are comments. Blank lines are ignored. # Maintenance: when a new GA feature flag ships, add a mapping here. # Run `python3 .warp/skills/missing_docs/scripts/audit_docs.py` to find unmapped flags. -# This audit is also run as a recurring scheduled Oz agent to catch drift. +# This audit is also run as a recurring scheduled cloud agent to catch drift. ## Feature flags -> doc pages diff --git a/.agents/skills/missing_docs/references/stale_terms.md b/.agents/skills/missing_docs/references/stale_terms.md index 555a2b3..d6756ca 100644 --- a/.agents/skills/missing_docs/references/stale_terms.md +++ b/.agents/skills/missing_docs/references/stale_terms.md @@ -25,10 +25,17 @@ mac os -> Use 'macOS' ## Deprecated terminology -ozzies -> Use 'Oz agents', 'instances', or 'Oz subagents' -warp agent -> Use 'Agent' or 'Oz agent' depending on context -warp agents -> Use 'Agents' or 'Oz agents' depending on context +ambient agent -> Use 'cloud agent' — 'ambient' is no longer a product term +ambient agents -> Use 'cloud agents' — 'ambient' is no longer a product term +ozzies -> Use 'agents', 'instances', or 'subagents' +oz agent -> Use 'agent' or 'Warp Agent' depending on context +oz agents -> Use 'agents' or 'Warp Agents' depending on context +oz cloud agent -> Use 'cloud agent' +oz cloud agents -> Use 'cloud agents' +oz subagent -> Use 'subagent' +oz subagents -> Use 'subagents' +oz conversation -> Use 'conversation' agent-mode -> Use 'Agent Mode' (two words, no hyphen) -deploying an oz -> Use 'Deploying an Oz agent' -the oz agent -> Use 'An Oz agent' or 'A parent Oz agent' -oz is running -> Use 'An Oz agent is running' or 'A run is in progress' +deploying an oz -> Use 'Deploying an agent' +the oz agent -> Use 'the agent' or 'the Warp Agent' +oz is running -> Use 'An agent is running' or 'A run is in progress' diff --git a/.agents/skills/style_lint/SKILL.md b/.agents/skills/style_lint/SKILL.md index f2550d9..188c2a8 100644 --- a/.agents/skills/style_lint/SKILL.md +++ b/.agents/skills/style_lint/SKILL.md @@ -52,7 +52,7 @@ python3 .warp/skills/style_lint/style_lint.py --all --fix --create-pr ### Terminology checks - **Product name casing**: "Warp Terminal" (→ "Warp"), "agent mode" (→ "Agent Mode"), "warp drive" (→ "Warp Drive"), "codebase context" (→ "Codebase Context"), "agent management panel" (→ "Agent Management Panel") -- **Oz terms to avoid**: "Ozzies", "Deploying an Oz", "The Oz Agent", "Oz is running", "AI agents" +- **Oz terms to avoid**: "Oz agent", "Oz cloud agent", "Oz subagent", "Oz conversation", "Ozzies", "Deploying an Oz", "The Oz Agent", "Oz is running", "AI agents" - **Deprecated terminology**: "whitelist" (→ "allowlist"), "blacklist"/"blocklist" (→ "denylist") - **External product names**: "Github" (→ "GitHub"), "github actions" (→ "GitHub Actions"), "MacOS" (→ "macOS"), "A.I." (→ "AI") - **Unrecognized terms** (warning): Bolded terms that look like product names but aren't in `terminology.md`. Flags candidates for glossary addition — not errors, just suggestions. @@ -65,7 +65,7 @@ When run with `--fix`: ## Relationship to validate_ui_refs -This skill checks broader formatting and terminology. The `validate_ui_refs` skill validates UI paths and Command Palette names against the warp-internal codebase. They complement each other with no overlap. Both can run in scheduled Oz agent workflows. +This skill checks broader formatting and terminology. The `validate_ui_refs` skill validates UI paths and Command Palette names against the warp-internal codebase. They complement each other with no overlap. Both can run in scheduled cloud agent workflows. ## Dependencies @@ -73,7 +73,7 @@ Requires Python 3.7+. Optional: `requests` (for Slack notifications), `gh` CLI ( ## Cloud agent / scheduling -For scheduled Oz cloud agent runs: +For scheduled cloud agent runs: 1. Configure the environment with the docs repo 2. Set the `SLACK_BOT_TOKEN` secret in the environment (for `--slack-notify`) 3. Run: `python3 .warp/skills/style_lint/style_lint.py --all --fix --create-pr --slack-notify` diff --git a/.agents/skills/style_lint/style_lint.py b/.agents/skills/style_lint/style_lint.py index 488ed83..b2369a8 100644 --- a/.agents/skills/style_lint/style_lint.py +++ b/.agents/skills/style_lint/style_lint.py @@ -35,7 +35,7 @@ # Feature names that are correctly Title Case (exceptions to sentence-case rule) PROPER_FEATURE_NAMES = { "Admin Panel", "Agent Management Panel", "Agent Mode", "Agent Profiles", - "Ambient Agents", "Auto-detection Mode", "Cloud Agent Credits", + "Auto-detection Mode", "Cloud Agent Credits", "Cloud Agents", "Codebase Context", "Code Review", "Command Palette", "Global Rules", "Oz CLI", "Oz Platform", "Project Rules", "Slash Commands", "Terminal Mode", "Universal Input", "Warp Drive", "Warp Platform", @@ -70,11 +70,16 @@ # Oz terms to avoid (case-insensitive patterns) OZ_TERMS_TO_AVOID = [ - (r"\bOzzies\b", "Use 'Oz agents', 'instances', or 'Oz subagents'"), - (r"\bDeploying an Oz\b", "Use 'Deploying an Oz agent'"), - (r"\bThe Oz Agent\b", "Use 'An Oz agent' or 'A parent Oz agent'"), - (r"\bOz is running\b", "Use 'An Oz agent is running' or 'A run is in progress'"), + (r"\bOzzies\b", "Use 'agents', 'instances', or 'subagents'"), + (r"\bDeploying an Oz\b", "Use 'Deploying an agent'"), + (r"\bThe Oz Agent\b", "Use 'the agent' or 'the Warp Agent'"), + (r"\bOz is running\b", "Use 'An agent is running' or 'A run is in progress'"), (r"\bAI agents?\b", "Use 'agents' (the 'AI' prefix is redundant)"), + (r"\bOz cloud agents?\b", "Use 'cloud agent(s)'"), + (r"\bOz subagents?\b", "Use 'subagent(s)'"), + (r"\bOz conversation\b", "Use 'conversation'"), + (r"\bOz agents?\b", "Use 'agent(s)' or 'Warp Agent(s)' depending on context"), + (r"\b[Aa]mbient [Aa]gents?\b", "Use 'cloud agent(s)' — 'ambient' is no longer a product term"), ] # Action verbs that precede UI elements (should be bold, not backtick) @@ -386,13 +391,23 @@ def check_product_casing(lines: List[str], filepath: str) -> List[Issue]: def check_oz_terms(lines: List[str], filepath: str) -> List[Issue]: - """Check for Oz terms to avoid.""" + """Check for Oz terms to avoid. + + Skips fenced code blocks and strips inline code (backtick-wrapped text) + so that legitimate CLI commands like `oz agent run` are not flagged. + """ issues = [] + in_code_block = False for i, line in enumerate(lines, 1): - if line.strip().startswith("```") or line.strip().startswith("`"): + if line.strip().startswith("```"): + in_code_block = not in_code_block + continue + if in_code_block: continue + # Strip inline code spans so `oz agent run` is not matched + prose_line = re.sub(r"`[^`]+`", "", line) for pattern, suggestion in OZ_TERMS_TO_AVOID: - for m in re.finditer(pattern, line, re.IGNORECASE): + for m in re.finditer(pattern, prose_line, re.IGNORECASE): issues.append(Issue( filepath, i, "oz-term", f"Avoid \"{m.group(0)}\" → {suggestion}", diff --git a/.agents/skills/sync-error-docs/references/error-page-template.md b/.agents/skills/sync-error-docs/references/error-page-template.md index a9210d6..6d9067b 100644 --- a/.agents/skills/sync-error-docs/references/error-page-template.md +++ b/.agents/skills/sync-error-docs/references/error-page-template.md @@ -60,7 +60,7 @@ This error is returned when: ## Related -* [Oz Agent API & SDK](https://docs.warp.dev/reference/api-and-sdk/agent) — API reference +* [Agent API & SDK](https://docs.warp.dev/reference/api-and-sdk/agent) — API reference * [Cloud Agents Overview](https://docs.warp.dev/agent-platform/cloud-agents/overview) — How cloud agents work ``` diff --git a/.agents/skills/validate_ui_refs/SKILL.md b/.agents/skills/validate_ui_refs/SKILL.md index 8b76f2b..4b1ce86 100644 --- a/.agents/skills/validate_ui_refs/SKILL.md +++ b/.agents/skills/validate_ui_refs/SKILL.md @@ -135,7 +135,7 @@ The `--slack-notify` flag posts a summary to the configured Slack channel when u ### Intended behavior for scheduled runs -When this skill is configured as a scheduled Oz agent, Slack notifications should alert the team in two cases: +When this skill is configured as a scheduled cloud agent, Slack notifications should alert the team in two cases: 1. **Auto-fixes applied** — the script found and corrected issues, and created a PR. The notification should include the PR link so the team can review and merge. 2. **Unfixed issues remain** — some issues could not be auto-corrected (e.g., a renamed or removed section) and require manual attention. The notification should list these for triage. @@ -162,7 +162,7 @@ python3 .warp/skills/validate_ui_refs/validate_ui_refs.py --all --slack-notify ## Cloud Agent / Scheduling -For scheduled Oz cloud agent runs: +For scheduled cloud agent runs: 1. Configure the environment with the docs repo 2. Keep `valid_paths.json` up-to-date by running `--refresh-valid-paths` as a pre-step (requires `warp-internal` in the environment) diff --git a/.agents/templates/faq.md b/.agents/templates/faq.md index 73f36bd..a1e32ac 100644 --- a/.agents/templates/faq.md +++ b/.agents/templates/faq.md @@ -1,7 +1,7 @@ --- description: >- [1-2 sentences: what topic area these FAQs cover. - Example: "Answers to common questions about Oz cloud agents, billing, and environments."] + Example: "Answers to common questions about cloud agents, billing, and environments."] --- # [Title — sentence case. Title convention: "[Feature] FAQs" or "Frequently asked questions"] diff --git a/.agents/templates/quickstart.md b/.agents/templates/quickstart.md index 9adac6c..1cb9d36 100644 --- a/.agents/templates/quickstart.md +++ b/.agents/templates/quickstart.md @@ -1,7 +1,7 @@ --- description: >- [1-2 sentences: what the reader will accomplish + time estimate. - Example: "Learn how to run your first Oz cloud agent in ~10 minutes."] + Example: "Learn how to run your first cloud agent in ~10 minutes."] --- # [Descriptive title — sentence case. Title convention: "[Feature] quickstart" or "Quickstart for [product]". Do NOT use a bare "Quickstart" — include the feature name.] diff --git a/.agents/templates/troubleshooting.md b/.agents/templates/troubleshooting.md index 561c394..ea91da9 100644 --- a/.agents/templates/troubleshooting.md +++ b/.agents/templates/troubleshooting.md @@ -1,7 +1,7 @@ --- description: >- [1-2 sentences describing common issues covered on this page. - Example: "Solutions for common issues with Oz cloud agents, environments, and integrations."] + Example: "Solutions for common issues with cloud agents, environments, and integrations."] --- # [Title — sentence case. Title convention: "Troubleshooting [feature]" or "Known issues with [feature]"] diff --git a/.github/workflows/respond-to-comment.yml b/.github/workflows/respond-to-comment.yml index 4d87a86..7e4f40b 100644 --- a/.github/workflows/respond-to-comment.yml +++ b/.github/workflows/respond-to-comment.yml @@ -102,7 +102,7 @@ jobs: const commentBody = context.payload.comment.body; const author = context.payload.comment.user.login; - let prompt = `You are an expert software engineer and the Oz Agent. + let prompt = `You are an expert software engineer and the Warp Agent. You are responding to a specific request on a Pull Request. This may involve answering questions, providing explanations, or implementing code changes. **Context**: @@ -162,12 +162,12 @@ jobs: env: GH_TOKEN: ${{ github.token }} run: | - git config user.name "Oz Agent" + git config user.name "Warp Agent" git config user.email "agent@warp.dev" if [[ -n $(git status --porcelain) ]]; then git add . - git commit -m "Oz Agent: Address comment" + git commit -m "Warp Agent: Address comment" git push else echo "No changes to commit." diff --git a/.github/workflows/review-pr.yml b/.github/workflows/review-pr.yml index 772db56..a1dfe1b 100644 --- a/.github/workflows/review-pr.yml +++ b/.github/workflows/review-pr.yml @@ -17,7 +17,7 @@ jobs: - name: Checkout Repository uses: actions/checkout@v4 - - name: Review PR with Oz agent + - name: Review PR with Warp Agent uses: warpdotdev/oz-agent-action@v1 env: GH_TOKEN: ${{ github.token }} @@ -179,7 +179,7 @@ jobs: if (hasSummary) { payload.body = summary; } else { - payload.body = 'Automated review by Oz Agent'; + payload.body = 'Automated review by Warp Agent'; } if (comments.length > 0) { diff --git a/AGENTS.md b/AGENTS.md index d3ad135..2a642c7 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -553,7 +553,7 @@ Product feature names retain their standard capitalization. Match the exact casi - **Agent** or **Agents** (capitalized when referring to Warp's AI agents) - **Agent Mode** (not "agent mode" or "Agent-mode") - **Terminal and Agent modes** - The two distinct modes in Warp: terminal mode (for shell commands) and Agent Mode (for multi-turn agent conversations). Use "Terminal and Agent modes" on first reference; use "terminal mode" or "Agent Mode" individually in subsequent references. Do not use "agent modality" or "Agent Modality" — this was an internal name that is not user-facing. -- **Ambient Agents** (capitalized as a feature/section name; lowercase "ambient agents" only when describing the generic concept) +- **Cloud Agents** (capitalized as a product section/feature name; lowercase "cloud agents" in most contexts) - **Warp Drive** - Shared workspace for saving and organizing commands, workflows, and environment variables across your team. - **Codebase Context** - Warp indexes your Git-tracked codebase to help Agents understand your code. - **Admin Panel** - Team management surface for controlling members, roles, and billing. @@ -561,30 +561,30 @@ Product feature names retain their standard capitalization. Match the exact casi ### Oz terminology -#### Oz vs Warp -- **Warp** is the terminal and coding surface -- **Oz** is Warp's programmable agent for running and coordinating agents at scale +#### Warp Agent vs Oz +- **Warp Agent** — Warp's built-in agent harness. Use "Warp Agent" when specifically referring to the built-in harness, especially when contrasting with third-party agents (Claude Code, Codex, etc.), or when referencing the Settings label (**Settings** > **Agents** > **Warp Agent**). +- **Oz** — Warp's programmable platform for running and coordinating agents at scale - There is typically one Warp environment per user session. Oz can run many agents concurrently, across machines, repos, and teams. -#### Core Oz terms -- **Oz** - Warp's programmable agent for running and coordinating agents at scale -- **Oz agent** - A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Agents can be local or cloud, and interactive or ambient. -- **Oz cloud agent** - An Oz agent running in the cloud, from a trigger, schedule, or started from someone's local machine -- **Oz subagent** - A child Oz agent created by a parent Oz agent to parallelize or delegate work -- **Oz run** - A single execution lifecycle of an Oz agent, including actions, outputs, and logs. Always ambient and cloud-based. -- **Oz conversation** - An interactive execution lifecycle within the Warp Terminal, regardless of whether it's local or in the cloud -- **Environment** - The execution context for an Oz agent, including repo access, dependencies, secrets, compute, and runtime configuration +#### Core terms +- **agent** - A combination of agent instructions (skill or prompt), trigger (cron, webhook, manual), environment (local, cloud), profile, and host. Agents can be local or cloud. Use lowercase "agent" in most contexts; use "Warp Agent" only when referring specifically to the built-in Warp harness. +- **cloud agent** - An agent running in the cloud, from a trigger, schedule, or started from someone's local machine +- **subagent** - A child agent created by a parent agent to parallelize or delegate work +- **conversation** - An interactive execution lifecycle within the Warp Terminal, regardless of whether it's local or in the cloud +- **Oz** - Warp's programmable platform for running and coordinating agents at scale +- **Oz run** - A single execution lifecycle of an agent, including actions, outputs, and logs. Always cloud-based. +- **Environment** - The execution context for an agent, including repo access, dependencies, secrets, compute, and runtime configuration - **Oz dashboard** - The app surface to manage all Oz runs, unified across the Warp app and web -- **Oz web app** - The web app for configuring Oz agents and managing runs +- **Oz web app** - The web app for configuring agents and managing runs #### Oz CLI commands - `oz agent run` - Run a local agent - `oz agent run-cloud` - Run an adhoc cloud agent - `oz integration create` - Install integrations (Slack, Linear) - `oz environment create/list/get/update/delete` - CRUD on environments -- `oz schedule create/list/get/update/delete` - CRUD on scheduled ambient agents +- `oz schedule create/list/get/update/delete` - CRUD on scheduled cloud agents - `oz secret create/list/update/delete` - CRUD on Warp-managed secrets -- `oz run list/get` - Get info on ambient agent runs +- `oz run list/get` - Get info on cloud agent runs #### Preferred phrases - ✅ "Ask Oz to..." @@ -592,11 +592,16 @@ Product feature names retain their standard capitalization. Match the exact casi - ✅ "What would you like Oz to do?" #### Terms to avoid -- ❌ "Ozzies" → Use "Oz agents", "instances", or "Oz subagents" -- ❌ "Deploying an Oz" → Use "Deploying an Oz agent" -- ❌ "The Oz Agent" → Use "An Oz agent" or "A parent Oz agent" -- ❌ "Oz is running" → Use "An Oz agent is running" or "A run is in progress" +- ❌ "Oz agent" / "Oz agents" → Use "agent" / "agents" (or "Warp Agent" / "Warp Agents" when referring to the built-in harness) +- ❌ "Oz cloud agent" → Use "cloud agent" +- ❌ "Oz subagent" → Use "subagent" +- ❌ "Oz conversation" → Use "conversation" +- ❌ "Ozzies" → Use "agents", "instances", or "subagents" +- ❌ "Deploying an Oz" → Use "Deploying an agent" +- ❌ "The Oz Agent" → Use "the agent" or "the Warp Agent" +- ❌ "Oz is running" → Use "An agent is running" or "A run is in progress" - ❌ "AI agents" → Use "agents" (the "AI" prefix is redundant) +- ❌ "Ambient Agents" / "ambient agents" → Use "Cloud Agents" / "cloud agents" ("ambient" is no longer a product term) - ❌ "Agent Modality" or "agent modality" → Use "Terminal and Agent modes" (this was an internal name, not user-facing) ### Technical terms diff --git a/README.md b/README.md index 9496312..342f87a 100644 --- a/README.md +++ b/README.md @@ -73,7 +73,7 @@ Read [CONTRIBUTING.md](CONTRIBUTING.md) for the full contribution flow, local se ## Agent skills -The `.warp/skills/` directory contains [Oz agent skills](https://docs.warp.dev/agent-platform/capabilities/skills) used by the Warp docs team for automated workflows, including style linting, link checking, changelog updates, and terminology syncing. The skills are included for transparency and as examples of how Oz skills can automate documentation workflows. See [`warpdotdev/oz-skills`](https://github.com/warpdotdev/oz-skills) for more examples. +The `.warp/skills/` directory contains [agent skills](https://docs.warp.dev/agent-platform/capabilities/skills) used by the Warp docs team for automated workflows, including style linting, link checking, changelog updates, and terminology syncing. The skills are included for transparency and as examples of how Oz skills can automate documentation workflows. See [`warpdotdev/oz-skills`](https://github.com/warpdotdev/oz-skills) for more examples. Some skills depend on internal Warp repositories (`warp-internal`, `warp-server`) and won't run end-to-end without access to those codebases. diff --git a/developers/agent-api-openapi.yaml b/developers/agent-api-openapi.yaml index cd2bc4b..83f2285 100644 --- a/developers/agent-api-openapi.yaml +++ b/developers/agent-api-openapi.yaml @@ -1,9 +1,9 @@ openapi: 3.0.0 info: - title: Oz Agent API + title: Agent API version: 1.0.0 description: | - API for creating, managing, and querying Oz cloud agent runs. + API for creating, managing, and querying cloud agent runs. These endpoints allow users to programmatically spawn agents, list runs, and retrieve detailed run information. diff --git a/scripts/generate-og-api.mjs b/scripts/generate-og-api.mjs index 984d63f..87469db 100644 --- a/scripts/generate-og-api.mjs +++ b/scripts/generate-og-api.mjs @@ -45,7 +45,7 @@ const svg = ` - Oz Agent API Reference + Agent API Reference Create and manage cloud agent runs, schedules, and more. diff --git a/src/content/docs/agent-platform/capabilities/agent-notifications.mdx b/src/content/docs/agent-platform/capabilities/agent-notifications.mdx index 15f931e..b285948 100644 --- a/src/content/docs/agent-platform/capabilities/agent-notifications.mdx +++ b/src/content/docs/agent-platform/capabilities/agent-notifications.mdx @@ -77,14 +77,14 @@ Desktop notifications require system permissions. If you're not receiving them, Agent notifications currently work with: -* **Oz agent** - supported out of the box. No setup required. +* **Warp Agent** - supported out of the box. No setup required. * **Claude Code** - full support via notification plugin. * **Codex** - full support via native Codex configuration. * **OpenCode** - full support via notification plugin. ## Setting up notifications -For the **Oz agent**, notifications work out of the box — no setup needed. +For the **Warp Agent**, notifications work out of the box — no setup needed. For **third-party CLI agents**, each agent requires a one-time setup. The process varies by agent: diff --git a/src/content/docs/agent-platform/capabilities/codebase-context.mdx b/src/content/docs/agent-platform/capabilities/codebase-context.mdx index 03b7b0f..da9351e 100644 --- a/src/content/docs/agent-platform/capabilities/codebase-context.mdx +++ b/src/content/docs/agent-platform/capabilities/codebase-context.mdx @@ -121,7 +121,7 @@ Files excluded by ignore rules **do not** count toward your codebase's file limi ## Codebase Context in cloud agent runs -Codebase Context is available in all Oz cloud agent runs — including runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules — as long as Codebase Context is enabled for your account. +Codebase Context is available in all cloud agent runs — including runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules — as long as Codebase Context is enabled for your account. **No additional configuration is needed.** If Codebase Context is enabled, cloud agents use it automatically. diff --git a/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx b/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx index d3ae1bf..2611d40 100644 --- a/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx +++ b/src/content/docs/agent-platform/cloud-agents/deployment-patterns.mdx @@ -11,7 +11,7 @@ Teams adopt cloud agents in a few repeatable ways. This page outlines the most c #### Quick mental model -Oz cloud agent setups usually have four moving parts: +Cloud agent setups usually have four moving parts: 1. **Trigger**: something happens (CI step, webhook, cron, Slack mention). 2. **Orchestration**: something decides what to run and tracks it (Oz orchestrator, GitHub Actions, your internal system). diff --git a/src/content/docs/agent-platform/cloud-agents/environments.mdx b/src/content/docs/agent-platform/cloud-agents/environments.mdx index a36a971..ee39882 100644 --- a/src/content/docs/agent-platform/cloud-agents/environments.mdx +++ b/src/content/docs/agent-platform/cloud-agents/environments.mdx @@ -66,7 +66,7 @@ Components in the execution flow: 6. **Outputs** – The run produces PRs, messages, reports, or transcripts :::note -**Local agent** runs (using `oz agent run`) don't require an environment. These runs use your current machine's setup. Environments are required for **automated platform** runs like Oz cloud agents and integrations +**Local agent** runs (using `oz agent run`) don't require an environment. These runs use your current machine's setup. Environments are required for **automated platform** runs like cloud agents and integrations ::: ### Hosts and environments diff --git a/src/content/docs/agent-platform/cloud-agents/faqs.mdx b/src/content/docs/agent-platform/cloud-agents/faqs.mdx index 265a84f..3d36762 100644 --- a/src/content/docs/agent-platform/cloud-agents/faqs.mdx +++ b/src/content/docs/agent-platform/cloud-agents/faqs.mdx @@ -47,7 +47,7 @@ If you're not happy with where it landed, you can take over to finish the task. ### Do cloud agents have access to Codebase Context and indexing? -Yes. [Codebase Context](/agent-platform/capabilities/codebase-context/) is enabled for all Oz cloud agent runs, as long as Codebase Context is enabled for your account. This includes runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules. No additional configuration is needed — if Codebase Context is enabled, cloud agents use it automatically. +Yes. [Codebase Context](/agent-platform/capabilities/codebase-context/) is enabled for all cloud agent runs, as long as Codebase Context is enabled for your account. This includes runs triggered from the CLI, API/SDK, integrations (Slack, Linear, GitHub Actions), and schedules. No additional configuration is needed — if Codebase Context is enabled, cloud agents use it automatically. ### Can I access a shell inside a cloud agent environment? Are there limitations (Docker, Playwright, etc.)? diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx index a76169d..4ea16bc 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/azure-devops.mdx @@ -3,11 +3,11 @@ title: Azure DevOps integration sidebar: label: "Azure DevOps" description: >- - Connect Oz cloud agents to Azure DevOps repos using personal access tokens + Connect cloud agents to Azure DevOps repos using personal access tokens and Warp-managed secrets. --- -Oz cloud agents work with any Git repository, including those hosted on Azure DevOps. A native Azure DevOps integration is not yet available, but you can grant agents access to your repositories using a personal access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. +Cloud agents work with any Git repository, including those hosted on Azure DevOps. A native Azure DevOps integration is not yet available, but you can grant agents access to your repositories using a personal access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. This page explains how to generate an Azure DevOps personal access token, store it securely, and configure a cloud agent environment that clones your repository at runtime. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx index 300f4d1..2f02af4 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/bitbucket.mdx @@ -3,11 +3,11 @@ title: Bitbucket integration sidebar: label: "Bitbucket" description: >- - Connect Oz cloud agents to Bitbucket repos using access tokens and + Connect cloud agents to Bitbucket repos using access tokens and Warp-managed secrets. --- -Oz cloud agents work with any Git repository, including those hosted on Bitbucket. Unlike GitHub, Bitbucket does not have a native Warp integration, but you can grant agents access to your Bitbucket repositories using an access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. +Cloud agents work with any Git repository, including those hosted on Bitbucket. Unlike GitHub, Bitbucket does not have a native Warp integration, but you can grant agents access to your Bitbucket repositories using an access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. This page explains how to generate a Bitbucket access token, store it securely, and configure a cloud agent environment that clones your repository at runtime. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx index b3c99ce..112fc8e 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/cloud-providers.mdx @@ -1,12 +1,12 @@ --- title: Cloud Providers (Preview) description: >- - Connect Oz cloud agents to your AWS and GCP services. + Connect cloud agents to your AWS and GCP services. sidebar: label: "AWS, GCP, and other cloud providers" --- -Oz cloud agents can securely access cloud providers using short-lived OpenID Connect credentials. +Cloud agents can securely access cloud providers using short-lived OpenID Connect credentials. This page explains how to configure a cloud agent environment to automatically authenticate to your cloud provider. Oz has built-in support for AWS and GCP, and can work with any provider that @@ -119,7 +119,7 @@ To allow multiple specific principals, use a list of subjects: ... ``` -4. Click **Next** and add permissions policies. These policies determine what Oz agents can access +4. Click **Next** and add permissions policies. These policies determine what agents can access in your AWS account. 5. Click **Next** and enter a role name and optional description. 6. Click **Create role**, then open the role and note down the role ARN. This will be of the form `arn:aws:iam:::role/`. @@ -128,7 +128,7 @@ To allow multiple specific principals, use a list of subjects: ### Step 3: Enable AWS federation in your cloud agent environment -Finally, configure the Oz cloud agent environment to use your new AWS role. +Finally, configure the cloud agent environment to use your new AWS role. 1. Open the Oz web app at [https://oz.warp.dev](https://oz.warp.dev). 2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions. @@ -139,7 +139,7 @@ Finally, configure the Oz cloud agent environment to use your new AWS role. Currently, AWS federation can only be configured in the Oz web app, not the CLI. ::: -Oz agents running in this environment will now automatically assume the configured role when using +Agents running in this environment will now automatically assume the configured role when using the `aws` CLI or a compatible SDK. :::note @@ -191,16 +191,16 @@ Replace `` with the UID of your Warp team. This is the last component panel URL is `https://app.warp.dev/admin/abc123def456`, your team UID would be `abc123def456`. :::caution -If you do not set an attribute condition, then _any_ Oz agent will be able to use your Workload +If you do not set an attribute condition, then _any_ agent will be able to use your Workload Identity Federation provider, even if they do not belong to your team. ::: ### Step 2: Configure IAM policies -You will need to configure IAM policies in GCP that allow Oz agents in the Workload Identity +You will need to configure IAM policies in GCP that allow agents in the Workload Identity Federation pool access to resources. -To give all Oz agents on your team read-only access to all Compute Engine resources in a project, +To give all agents on your team read-only access to all Compute Engine resources in a project, for example, you would run: ```bash @@ -214,7 +214,7 @@ for the full syntax supported. ### Step 3: Enable Workload Identity Federation in your cloud agent environment -Finally, configure the Oz cloud agent environment to use your Workload Identity Federation provider. +Finally, configure the cloud agent environment to use your Workload Identity Federation provider. 1. Open the Oz web app at [https://oz.warp.dev](https://oz.warp.dev). 2. Create or edit an environment. See [Environments](/agent-platform/cloud-agents/oz-web-app/#environments) for instructions. @@ -225,7 +225,7 @@ Finally, configure the Oz cloud agent environment to use your Workload Identity Currently, Workload Identity Federation can only be configured in the Oz web app, not the CLI. ::: -Oz agents running in this environment will now automatically configure +Agents running in this environment will now automatically configure [Application Default Credentials](https://docs.cloud.google.com/docs/authentication/application-default-credentials) to use the configured pool. Both the `GOOGLE_APPLICATION_CREDENTIALS` and `CLOUDSDK_AUTH_CREDENTIAL_FILE_OVERRIDE` environment variables are set, so both the `gcloud` CLI and official Google SDKs will use the Oz @@ -246,7 +246,7 @@ oz federate issue-token --audience your-provider.com --output-format json ``` Optionally, add `--duration ` to customize the token validity. This cannot exceed the -maximum runtime of an Oz agent. +maximum runtime of an agent. You may then exchange this token for provider-specific credentials. @@ -262,7 +262,7 @@ such as `https://iam.googleapis.com/projects//locations/global/w ### Subject (`sub`) -The `sub` claim is set to the identity that an Oz agent is executing as. This will either be a +The `sub` claim is set to the identity that an agent is executing as. This will either be a Warp user ID or an autogenerated account ID for team-scoped agent runs. By default, the `sub` claim uses the format `:`: @@ -313,7 +313,7 @@ list only ever contains a single value. ### Oz run -The following claims are derived from an Oz agent run: +The following claims are derived from an agent run: * `run_id`: the unique identifier for the individual run. This is not suitable for configuring access, but is useful to log for debugging. @@ -324,7 +324,7 @@ The following claims are derived from an Oz agent run: ### Example token -The following OIDC token references an Oz agent running as a specific Warp user: +The following OIDC token references an agent running as a specific Warp user: ```json // JWT Header diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx index 2b89bbd..9bf7f2d 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/github-actions.mdx @@ -1,12 +1,12 @@ --- title: GitHub Actions description: >- - Run Oz agents in GitHub Actions to automate code review, issue triage, and + Run agents in GitHub Actions to automate code review, issue triage, and CI fixes. --- import VideoEmbed from '@components/VideoEmbed.astro'; -Run Oz agents directly in your GitHub Actions workflows using `oz-agent-action`. The agent integrates seamlessly into your CI pipeline, automating tasks like code review, issue triage, bug fixing, and maintenance using your repository context and GitHub permissions. This page covers how the integration works, how to set it up, and common automation patterns for development teams. +Run agents directly in your GitHub Actions workflows using `oz-agent-action`. The agent integrates seamlessly into your CI pipeline, automating tasks like code review, issue triage, bug fixing, and maintenance using your repository context and GitHub permissions. This page covers how the integration works, how to set it up, and common automation patterns for development teams. :::note **Getting started?** See the [GitHub Actions quickstart](/agent-platform/cloud-agents/integrations/quickstart-github-actions/) to set up your first workflow, or visit the [oz-agent-action repository](https://github.com/warpdotdev/oz-agent-action) for detailed setup instructions and ready-to-use workflow templates. @@ -29,7 +29,7 @@ In this demo The `oz-agent-action` is a GitHub Action that wraps the Oz CLI and: -* Runs an Oz agent inside an Actions job +* Runs an agent inside an Actions job * Caches package installation for faster builds * Captures the agent's output for use in subsequent workflow steps * Lets you pass workflow context, event data, and previous step outputs into the agent prompt @@ -39,7 +39,7 @@ The `oz-agent-action` is a GitHub Action that wraps the Oz CLI and: ### Requirements -To use Oz agents in GitHub Actions, you need: +To use agents in GitHub Actions, you need: * A [**Warp API Key**](/reference/cli/#generating-api-keys) stored as a [GitHub secret](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions) — this authenticates the agent with Warp * Workflow permissions that match your intended actions (for example, `pull-requests: write` if the agent should commit or comment on PRs) — the agent performs actions on your behalf using the GitHub token available to the workflow @@ -49,7 +49,7 @@ To use Oz agents in GitHub Actions, you need: ### Using Skills -Skills provide reusable instructions for Oz agents. You can use pre-built skills from the [oz-skills repository](https://github.com/warpdotdev/oz-skills) or create custom [skills](/agent-platform/capabilities/skills/) for your specific workflows. Skills can also be deployed as [standalone agents](/agent-platform/capabilities/skills/#skills-as-agents) to run on a schedule or in response to events. +Skills provide reusable instructions for agents. You can use pre-built skills from the [oz-skills repository](https://github.com/warpdotdev/oz-skills) or create custom [skills](/agent-platform/capabilities/skills/) for your specific workflows. Skills can also be deployed as [standalone agents](/agent-platform/capabilities/skills/#skills-as-agents) to run on a schedule or in response to events. #### How to use skills diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx index aa6fc21..6f9dcc6 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/gitlab.mdx @@ -3,11 +3,11 @@ title: GitLab integration sidebar: label: "GitLab" description: >- - Connect Oz cloud agents to GitLab repos using personal access tokens and + Connect cloud agents to GitLab repos using personal access tokens and Warp-managed secrets. --- -Oz cloud agents work with any Git repository, including those hosted on GitLab. Unlike GitHub, GitLab does not have a native Warp integration, but you can grant agents access to your GitLab repositories using a personal access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. +Cloud agents work with any Git repository, including those hosted on GitLab. Unlike GitHub, GitLab does not have a native Warp integration, but you can grant agents access to your GitLab repositories using a personal access token and Warp-managed secrets. Once configured, your environment works with any Oz trigger—Slack, Linear, schedules, or the CLI. This page explains how to generate a GitLab personal access token, store it securely, and configure a cloud agent environment that clones your repository at runtime. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx index 3b8305f..5cafabb 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/linear.mdx @@ -3,7 +3,7 @@ title: Linear integration sidebar: label: "Linear" description: >- - Automate Linear issues with Oz agents that run code in the cloud and create + Automate Linear issues with agents that run code in the cloud and create pull requests on your behalf. --- import VideoEmbed from '@components/VideoEmbed.astro'; diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx index 82e28bb..4d2ebc3 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart-github-actions.mdx @@ -1,13 +1,13 @@ --- title: GitHub Actions quickstart description: >- - Set up your first Oz agent in GitHub Actions in ~10 minutes. Run agents as + Set up your first agent in GitHub Actions in ~10 minutes. Run agents as workflow steps to automate code review and issue triage. sidebar: label: "Quickstart" --- -Add Oz agents to your GitHub Actions workflows with [`oz-agent-action`](https://github.com/warpdotdev/oz-agent-action). This quickstart walks you through setting up your first GitHub Actions integration: a PR review workflow that automatically analyzes pull requests and posts inline review comments. +Add agents to your GitHub Actions workflows with [`oz-agent-action`](https://github.com/warpdotdev/oz-agent-action). This quickstart walks you through setting up your first GitHub Actions integration: a PR review workflow that automatically analyzes pull requests and posts inline review comments. --- @@ -30,7 +30,7 @@ Store your Warp API key as a GitHub Actions secret so workflows can authenticate ## 2. Create the workflow file -This workflow triggers an Oz agent whenever a PR is opened or marked ready for review. The agent reviews the diff and posts inline comments. +This workflow triggers an agent whenever a PR is opened or marked ready for review. The agent reviews the diff and posts inline comments. Create `.github/workflows/oz-pr-review.yml` in your repository with the following content: diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx index b411e5f..37c0ea7 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/quickstart.mdx @@ -1,7 +1,7 @@ --- title: Integrations quickstart description: >- - Trigger your first Oz agent from Slack in ~15 minutes and get results + Trigger your first agent from Slack in ~15 minutes and get results in-thread. sidebar: label: "Quickstart" @@ -18,7 +18,7 @@ Oz integrations let you trigger cloud agents directly from the tools your team a ## Prerequisites * **Eligible plan** - The Slack integration requires a Warp team on Build, Max, or Business plan with at least 20 credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). -* **An Oz cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one yet, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) or run `/create-environment` in Warp. +* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one yet, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) or run `/create-environment` in Warp. * **GitHub authorization** - Warp needs access to your repos to clone code and open PRs. You'll be prompted to authorize the Warp GitHub app when you first create the integration. --- @@ -77,5 +77,5 @@ When the task is complete, Oz posts a summary back to the original Slack thread. ## Next steps * **Customize agent behavior** - Use a [skill](/agent-platform/cloud-agents/skills-as-agents/) as the base prompt for your integration to give Oz consistent, reusable instructions across every run. -* **Trigger agents programmatically** - Use the [API & SDK](/reference/api-and-sdk/) to build custom automations and integrations on top of Oz agents. +* **Trigger agents programmatically** - Use the [API & SDK](/reference/api-and-sdk/) to build custom automations and integrations on top of agents. * **Read the full Slack reference** - [Slack](/agent-platform/cloud-agents/integrations/slack/) covers identity mapping, team access, monitoring runs, troubleshooting, and uninstall instructions. diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx index 9d25797..4eb7621 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/slack.mdx @@ -3,7 +3,7 @@ title: Slack integration sidebar: label: "Slack" description: >- - Trigger Oz agents from Slack to run cloud tasks, track progress, and create + Trigger agents from Slack to run cloud tasks, track progress, and create pull requests. --- diff --git a/src/content/docs/agent-platform/cloud-agents/overview.mdx b/src/content/docs/agent-platform/cloud-agents/overview.mdx index dd242d5..2aabbdc 100644 --- a/src/content/docs/agent-platform/cloud-agents/overview.mdx +++ b/src/content/docs/agent-platform/cloud-agents/overview.mdx @@ -8,7 +8,7 @@ sidebar: --- import VideoEmbed from '@components/VideoEmbed.astro'; -Oz Cloud Agents are **cloud-connected**, **background agents** that run on the [Oz Platform](/agent-platform/cloud-agents/platform/). +Cloud agents are **cloud-connected**, **background agents** that run on the [Oz Platform](/agent-platform/cloud-agents/platform/). **New to cloud agents?** Start with the [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) to run your first cloud agent in ~10 minutes. @@ -147,7 +147,7 @@ If your credit balance reaches zero, cloud agent runs will not be able to execut * [Cloud agents quickstart](/agent-platform/cloud-agents/quickstart/) — run your first cloud agent with an environment in ~10 minutes. * [Oz Platform](/agent-platform/cloud-agents/platform/) — CLI, Oz API/SDK, orchestration, tasks, environments, hosts, integrations, and more. * [Skills as Agents](/agent-platform/cloud-agents/skills-as-agents/) — run agents based on reusable skill definitions from the CLI, web app, API, or on a schedule. -* [Oz CLI](/reference/cli/) — shows how to run Oz agents in non-interactive mode from CI, scripts, or remote machines, including auth and common commands. +* [Oz CLI](/reference/cli/) — shows how to run agents in non-interactive mode from CI, scripts, or remote machines, including auth and common commands. * [Environments](/agent-platform/cloud-agents/environments/) — explains how environments provide the runtime context (repo, image, startup commands) for agent tasks. * [Oz API and SDK](/reference/api-and-sdk/) — documents the REST API for creating, querying, and monitoring agent tasks programmatically. * [Agent Secrets](/agent-platform/cloud-agents/secrets/) — covers how to store, scope, and inject credentials into agent runs safely. diff --git a/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx b/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx index c572f6b..eebe417 100644 --- a/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx +++ b/src/content/docs/agent-platform/cloud-agents/oz-web-app.mdx @@ -47,7 +47,7 @@ When you first sign in to the Oz web app, you'll see a guided onboarding flow th The onboarding asks "What brings you to Oz?" and offers three paths: * **Create an agent automation** — Walks you through setting up a scheduled agent, integration-triggered agent, or other automation -* **Run Oz Cloud Agents in Warp** — Opens the Warp desktop app (or takes you to the download page) to run cloud agents interactively +* **Run Cloud Agents in Warp** — Opens the Warp desktop app (or takes you to the download page) to run cloud agents interactively * **Build an app that uses agents** — Links to the [Oz Platform](/agent-platform/cloud-agents/platform/) docs for using the CLI, SDK, or API You can skip onboarding at any time to go directly to the Runs page. diff --git a/src/content/docs/agent-platform/cloud-agents/platform.mdx b/src/content/docs/agent-platform/cloud-agents/platform.mdx index 2773cf2..a29e32d 100644 --- a/src/content/docs/agent-platform/cloud-agents/platform.mdx +++ b/src/content/docs/agent-platform/cloud-agents/platform.mdx @@ -46,7 +46,7 @@ In practice: **triggers create tasks; tasks execute on a host (optionally in an ### Oz CLI -The [Oz CLI](/reference/cli/) is the **headless interface** for running Oz agents in non-interactive mode. It's commonly used in CI, scripts, and server environments where there is no interactive UI. For interactive workflows, use the [agent](/agent-platform/local-agents/overview/) embedded in Warp's desktop app. +The [Oz CLI](/reference/cli/) is the **headless interface** for running agents in non-interactive mode. It's commonly used in CI, scripts, and server environments where there is no interactive UI. For interactive workflows, use the [agent](/agent-platform/local-agents/overview/) embedded in Warp's desktop app. A key property of the CLI is that it is **cloud-connected**. Even when an agent is started on a local machine or in CI, it reports progress to Warp’s servers. This enables team visibility, session sharing (where supported), and programmatic tracking through the API. @@ -142,7 +142,7 @@ The Oz [Agent API](/reference/api-and-sdk/) is the HTTP interface to the Oz Plat * Monitor execution by listing tasks and tracking state transitions over time (for example: `QUEUED` → `INPROGRESS` → `SUCCEEDED/FAILED`). * Inspect results and provenance by fetching a task’s full details, including the original prompt, creator/source metadata, session link, and resolved agent configuration. -**Oz Agent SDKs** +**Oz SDKs** Oz provides official [Python](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript SDKs](https://github.com/warpdotdev/oz-sdk-typescript) that wrap the Oz API with: @@ -216,7 +216,7 @@ Examples of context extracted by first-party integrations: #### Custom integrations -With custom integrations, you own the webhook and event-handling logic. Your system receives an event, applies any filtering or enrichment you need, and then calls the Oz API (directly or via an SDK) to create a task. The resulting task is still a full Oz agent run — observable, manageable, and auditable like any other. +With custom integrations, you own the webhook and event-handling logic. Your system receives an event, applies any filtering or enrichment you need, and then calls the Oz API (directly or via an SDK) to create a task. The resulting task is still a full cloud agent run — observable, manageable, and auditable like any other. Custom integrations are a good fit when: diff --git a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/quickstart.mdx index a8d1def..c5b1bb6 100644 --- a/src/content/docs/agent-platform/cloud-agents/quickstart.mdx +++ b/src/content/docs/agent-platform/cloud-agents/quickstart.mdx @@ -1,14 +1,14 @@ --- title: Cloud agents quickstart description: >- - Learn how to run your first Oz cloud agent in ~10 minutes. Cloud agents run + Learn how to run your first cloud agent in ~10 minutes. Cloud agents run in remote environments, enabling automation, scheduling, and team collaboration. sidebar: label: "Quickstart" --- -**Oz cloud agents** run in a remote environment and can be triggered from events, schedules, integrations, or manually. This enables scaling agents off your laptop, automating development tasks, and building apps on top of agents. Oz handles the orchestration, execution, and observability. +**Cloud agents** run in a remote environment and can be triggered from events, schedules, integrations, or manually. This enables scaling agents off your laptop, automating development tasks, and building apps on top of agents. Oz handles the orchestration, execution, and observability. Cloud agents can run interactively (where you steer them in real-time) or autonomously (as background tasks). Each run creates a persistent session that your team can inspect, share, and query through the Warp app, the CLI, web app, or API. @@ -35,7 +35,7 @@ New to Warp? You'll get credits to try cloud agents. You need at least 20 credit --- -## Running your first Oz cloud agent +## Running your first cloud agent _~10 minutes • Recommended for all users_ @@ -142,7 +142,7 @@ oz schedule create \ Integrations require a team on Build, Max, or Business plan. ::: -### Build automations and apps on top of Oz agents +### Build automations and apps on top of agents Use the [Oz API & SDK](/reference/api-and-sdk/) to trigger agents programmatically from your own systems and workflows. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx index 453ca10..5272fe7 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/index.mdx @@ -1,19 +1,19 @@ --- title: Self-hosting overview description: >- - Run Oz cloud agents on your own infrastructure. Choose between a managed + Run cloud agents on your own infrastructure. Choose between a managed worker daemon orchestrated by Oz or unmanaged CLI-based execution you control. --- -Self-hosting lets your team run Oz cloud agent workloads on your own infrastructure instead of Warp-managed servers. You control the execution environment, compute resources, and network access. Repositories are cloned and stored only on your machines, and agents can reach services behind your VPN or firewall. +Self-hosting lets your team run cloud agent workloads on your own infrastructure instead of Warp-managed servers. You control the execution environment, compute resources, and network access. Repositories are cloned and stored only on your machines, and agents can reach services behind your VPN or firewall. **New to self-hosting?** Start with the [Self-hosting quickstart](/agent-platform/cloud-agents/self-hosting/quickstart/) to get a managed worker running on Docker in under 10 minutes. **Want a CLI-only path with no Docker requirement?** Jump straight to the [Unmanaged quickstart](/agent-platform/cloud-agents/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. :::note -**Enterprise feature**: Self-hosted Oz agents are available exclusively to teams on an Enterprise plan. To enable self-hosting for your team, [contact sales](https://warp.dev/contact-sales). +**Enterprise feature**: Self-hosted agents are available exclusively to teams on an Enterprise plan. To enable self-hosting for your team, [contact sales](https://warp.dev/contact-sales). ::: ## Managed vs unmanaged @@ -115,7 +115,7 @@ You're responsible for executing `oz agent run` on your infrastructure — simil ## Routing runs to self-hosted workers -This section applies to **all managed backends** (Docker, Kubernetes, and Direct). Once a worker is connected, route Oz cloud agent runs to it by specifying the `--host` flag (or equivalent) with your worker ID. The `--host` value must match the `--worker-id` of a connected worker exactly. +This section applies to **all managed backends** (Docker, Kubernetes, and Direct). Once a worker is connected, route cloud agent runs to it by specifying the `--host` flag (or equivalent) with your worker ID. The `--host` value must match the `--worker-id` of a connected worker exactly. :::note Unmanaged runs don't need routing — you invoke `oz agent run` directly on the host where you want the agent to execute. Routing is only relevant for managed workers. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx index d96bb44..14a27eb 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/quickstart.mdx @@ -7,7 +7,7 @@ sidebar: label: "Quickstart" --- -Run your first Oz cloud agent on your own infrastructure in ~10 minutes using the managed architecture with the Docker backend — the default and fastest path to self-hosting. +Run your first cloud agent on your own infrastructure in ~10 minutes using the managed architecture with the Docker backend — the default and fastest path to self-hosting. :::note This quickstart sets up the [managed architecture](/agent-platform/cloud-agents/self-hosting/#managed-architecture), where Oz orchestrates the agent and your worker provides the compute. **Prefer a CLI-only path with no Docker requirement?** Jump to the [Unmanaged quickstart](/agent-platform/cloud-agents/self-hosting/unmanaged/#unmanaged-quickstart) to run `oz agent run` directly on any host. diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx index 6ada078..8533c7c 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/security-and-networking.mdx @@ -34,7 +34,7 @@ While repositories are cloned and stored only on your infrastructure, code conte ## Network requirements -Self-hosted Oz agents **do not require any network ingress**. They require outbound (egress) access to the following services: +Self-hosted agents **do not require any network ingress**. They require outbound (egress) access to the following services: **Warp's backend (all architectures):** diff --git a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx b/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx index 84a2a11..a912561 100644 --- a/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx +++ b/src/content/docs/agent-platform/cloud-agents/self-hosting/unmanaged.mdx @@ -1,7 +1,7 @@ --- title: Unmanaged architecture description: >- - Run Oz agents in your existing CI, Kubernetes, or dev environments using + Run agents in your existing CI, Kubernetes, or dev environments using the oz agent run CLI with Warp tracking and observability. sidebar: label: "Unmanaged" @@ -72,7 +72,7 @@ The `--share` flag can be repeated to combine multiple sharing targets. If you a Warp maintains the [`warpdotdev/oz-agent-action`](https://github.com/warpdotdev/oz-agent-action) action for running agents in GitHub Actions. The action wraps `oz agent run` and is a drop-in for CI workflows: ```yaml -- name: Run Oz agent +- name: Run agent uses: warpdotdev/oz-agent-action@v1 # wraps `oz agent run` under the hood with: prompt: "Review the code changes on this branch" diff --git a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx index 298e9f9..bbeab5a 100644 --- a/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx +++ b/src/content/docs/agent-platform/cloud-agents/team-access-billing-and-identity.mdx @@ -102,13 +102,13 @@ This ensures runs are scoped to what the user is allowed to see and modify, and ## Team GitHub authorization -By default, Oz cloud agents authenticate with GitHub using the personal token of the user who triggered the run. Team GitHub authorization gives you an alternative: authenticate with the **Oz by Warp** GitHub App instead, so agents can clone repositories and open pull requests without relying on any individual's token. +By default, cloud agents authenticate with GitHub using the personal token of the user who triggered the run. Team GitHub authorization gives you an alternative: authenticate with the **Oz by Warp** GitHub App instead, so agents can clone repositories and open pull requests without relying on any individual's token. This is useful for fully automated workflows that use a [team API key](/reference/cli/api-keys/), like CI/CD pipelines, scheduled agents, and SDK-triggered runs, where you want code changes attributed to the GitHub App rather than a specific person. ### How it works -When an Oz agent task is initiated with a team API key, there is no individual user to authenticate on behalf of. Instead, Warp uses tokens issued by the **Oz by Warp** GitHub App installation to authenticate directly with GitHub. +When an agent task is initiated with a team API key, there is no individual user to authenticate on behalf of. Instead, Warp uses tokens issued by the **Oz by Warp** GitHub App installation to authenticate directly with GitHub. The GitHub App token gives the agent access to the repositories included in the app installation — it can clone repos, create branches, push commits, and open pull requests. During installation, you choose whether the app can access **all repositories** or only **selected repositories** in your GitHub organization, and this controls what team API key runs can access. @@ -140,7 +140,7 @@ There are two places you may encounter this installation flow: ### How this relates to environments -An [environment](/agent-platform/cloud-agents/environments/) is a template for an Oz cloud agent's sandbox — it defines the Docker image, repos, and setup commands, but it does not carry its own GitHub permissions. The same environment can be used by different users or by team API key runs, and each will authenticate to GitHub independently. +An [environment](/agent-platform/cloud-agents/environments/) is a template for a cloud agent's sandbox — it defines the Docker image, repos, and setup commands, but it does not carry its own GitHub permissions. The same environment can be used by different users or by team API key runs, and each will authenticate to GitHub independently. The environment configuration and the **Enabled GitHub Orgs** setting in the Admin Panel serve different purposes: diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx index 21946c9..279b706 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx +++ b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart.mdx @@ -1,14 +1,14 @@ --- title: Scheduled Agents quickstart description: >- - Schedule an Oz cloud agent to run recurring tasks automatically — issue + Schedule a cloud agent to run recurring tasks automatically — issue triage, dependency checks, code cleanup, and more. sidebar: label: "Quickstart" --- import VideoEmbed from '@components/VideoEmbed.astro'; -Scheduled agents are Oz cloud agents that run on a recurring cron schedule, handling recurring tasks automatically without manual triggers. This guide walks you through setting up an agent that triages your GitHub bug reports every week, checks whether each issue has enough detail to investigate, and posts follow-up comments when information is missing. You'll use a prebundled skill and the Oz web app; no CLI or custom code required. +Scheduled agents are cloud agents that run on a recurring cron schedule, handling recurring tasks automatically without manual triggers. This guide walks you through setting up an agent that triages your GitHub bug reports every week, checks whether each issue has enough detail to investigate, and posts follow-up comments when information is missing. You'll use a prebundled skill and the Oz web app; no CLI or custom code required. Watch this short demo of creating and testing a scheduled agent: @@ -18,7 +18,7 @@ Watch this short demo of creating and testing a scheduled agent: ## Prerequisites * **A Warp account on an eligible plan** - Build, Max, or Business, with credits available. See [Access, Billing, and Identity](/agent-platform/cloud-agents/team-access-billing-and-identity/). -* **An Oz cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) to create one first. +* **A cloud environment** - Agents run inside a configured environment that includes repos and other dependencies. If you don't have one, follow the [Cloud Agents Quickstart](/agent-platform/cloud-agents/quickstart/) to create one first. --- diff --git a/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx b/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx index 81548d3..71a870a 100644 --- a/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx +++ b/src/content/docs/agent-platform/getting-started/agents-in-warp.mdx @@ -1,18 +1,18 @@ --- title: Agents in Warp description: >- - Warp's Oz agents are capable collaborators that help you write code, debug + Warp's agents are capable collaborators that help you write code, debug issues, and complete terminal workflows, all from natural language prompts. --- import VideoEmbed from '@components/VideoEmbed.astro'; -Warp includes Oz agents. These coding agents are designed to help you build, test, deploy, and debug while keeping you in control. Describe what you want to do in natural language (_you can even use your voice_), and Oz will take action using your environment, codebase, and saved context. +Warp includes powerful coding agents designed to help you build, test, deploy, and debug while keeping you in control. Describe what you want to do in natural language (_you can even use your voice_), and the agent will take action using your environment, codebase, and saved context. -## What Oz agents can do +## What agents can do -Oz agents understand your codebase and can execute tasks autonomously while keeping you in control: +Agents understand your codebase and can execute tasks autonomously while keeping you in control: * **Write and edit code** - Create new files, refactor existing code, or make changes across multiple files in your codebase * **Debug and fix errors** - Analyze stack traces, interpret error output, and apply fixes @@ -66,7 +66,7 @@ For more details, see [Agent Profiles & Permissions](/agent-platform/capabilitie ## Managing agents -You can run multiple Oz agents simultaneously in Warp. All active agents—both local conversations and cloud agent runs—are tracked in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/). +You can run multiple agents simultaneously in Warp. All active agents—both local conversations and cloud agent runs—are tracked in the [management view](/agent-platform/cloud-agents/managing-cloud-agents/). Agents notify you when they need input, such as permission to run a command or approval to apply a code diff. This lets you focus on other work, knowing you'll be alerted when your attention is required. @@ -76,7 +76,7 @@ To access conversations across devices, share them with teammates, or restore pa ## Context and knowledge -Oz agents work best when they understand your codebase and workflows. Warp provides several ways to give agents the context they need: +Agents work best when they understand your codebase and workflows. Warp provides several ways to give agents the context they need: * [**Codebase Context**](/agent-platform/capabilities/codebase-context/) - Warp indexes your Git-tracked files so agents can search and understand your code * [**Rules**](/agent-platform/capabilities/rules/) - Define global and project-level guidelines that shape agent behavior @@ -88,7 +88,7 @@ Oz agents work best when they understand your codebase and workflows. Warp provi ## Third-Party CLI Agents -In addition to Warp's built-in Oz agent, Warp provides first-class support for third-party CLI coding agents like Claude Code, Codex, and OpenCode. Run any supported agent inside Warp and get rich input, code review, agent notifications, vertical tabs with agent metadata, and more. +In addition to Warp's built-in agent, Warp provides first-class support for third-party CLI coding agents like Claude Code, Codex, and OpenCode. Run any supported agent inside Warp and get rich input, code review, agent notifications, vertical tabs with agent metadata, and more. → [Learn about Third-Party CLI Agents](/agent-platform/cli-agents/overview/) @@ -96,7 +96,7 @@ In addition to Warp's built-in Oz agent, Warp provides first-class support for t ## From local to cloud -The same Oz agent capabilities that power interactive conversations in Warp also run in the cloud. Cloud agents can: +The same agent capabilities that power interactive conversations in Warp also run in the cloud. Cloud agents can: * React to events from Slack, Linear, or GitHub * Run on schedules for recurring tasks like dependency updates diff --git a/src/content/docs/agent-platform/index.mdx b/src/content/docs/agent-platform/index.mdx index 0580760..77fd64b 100644 --- a/src/content/docs/agent-platform/index.mdx +++ b/src/content/docs/agent-platform/index.mdx @@ -22,9 +22,9 @@ Oz is fully programmable—launch agents manually or build custom logic around t ## Key capabilities -* [**Local Agents**](/agent-platform/local-agents/overview/) - Interactive Oz agents embedded in Warp. Use natural language to write code, debug issues, run commands, and automate development tasks with full terminal access. +* [**Local Agents**](/agent-platform/local-agents/overview/) - Interactive agents embedded in Warp. Use natural language to write code, debug issues, run commands, and automate development tasks with full terminal access. * [**Third-Party CLI Agents**](/agent-platform/cli-agents/overview/) - Use Claude Code, Codex, OpenCode, and other CLI coding agents in Warp with rich input, notifications, code review, and remote session control. -* [**Oz Cloud Agents**](/agent-platform/cloud-agents/overview/) - Autonomous Oz agents that run in the background in response to system events, schedules, or integrations. +* [**Cloud Agents**](/agent-platform/cloud-agents/overview/) - Autonomous agents that run in the background in response to system events, schedules, or integrations. * [**Integrations**](/agent-platform/cloud-agents/integrations/) - Connect external system events to autonomous agent execution. Use [Slack](/agent-platform/cloud-agents/integrations/slack/), [Linear](/agent-platform/cloud-agents/integrations/linear/), [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/), and other integrations to trigger agents in the cloud. * [**Oz Platform**](/agent-platform/cloud-agents/platform/) - The underlying infrastructure that powers Oz, including the CLI, API/SDK, orchestration layer, environments, secrets, and management/observability. @@ -32,7 +32,7 @@ Oz is fully programmable—launch agents manually or build custom logic around t ## Getting started -* [**Agents in Warp**](/agent-platform/getting-started/agents-in-warp/) - Start using Oz agents interactively in Warp +* [**Agents in Warp**](/agent-platform/getting-started/agents-in-warp/) - Start using agents interactively in Warp * [**Oz web app**](https://oz.warp.dev) - Create runs, manage schedules, browse skills, and configure integrations * [**Oz CLI**](/reference/cli/) - Run agents from the command line, in CI, or on remote machines * [**Oz API & SDK**](/reference/api-and-sdk/) - Programmatically create and monitor agent runs diff --git a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx index d7386c6..6b07099 100644 --- a/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx +++ b/src/content/docs/agent-platform/local-agents/interacting-with-agents/terminal-and-agent-modes.mdx @@ -17,7 +17,7 @@ Warp provides two distinct modes: a clean terminal for commands, and a dedicated Before diving in, here are two key concepts: * **Terminal session** - Your shell environment where you run commands. This is the default mode when you open Warp—a clean, traditional terminal input. -* **Oz agent conversation** - A multi-turn interaction with Oz. Conversations maintain context across exchanges and have their own dedicated view with richer controls. +* **Agent conversation** - A multi-turn interaction with Oz. Conversations maintain context across exchanges and have their own dedicated view with richer controls. Terminal and Agent modes make switching between these two contexts seamless while keeping them visually distinct. @@ -67,7 +67,7 @@ If you disable the message bar while auto-detection is enabled, you won't see th The shortcuts shown on this page use macOS keybindings. For Windows and Linux shortcuts, see [Keyboard Shortcuts](/getting-started/keyboard-shortcuts/). ::: -### Oz agent conversation view (expanded UI) +### Agent conversation view (expanded UI) * A dedicated conversation view with richer agent controls including model select, voice input, image attachments, and conversation management. * Familiar "charms" (current directory, git branch, diff view entry point, etc.) are still available. @@ -111,7 +111,7 @@ This separation keeps your terminal view clean while preserving full context wit #### Cloud agent conversations -In addition to local agent conversations, you can start **Oz cloud agent conversations** that run in an isolated cloud environment. Cloud agents are useful for: +In addition to local agent conversations, you can start **cloud agent conversations** that run in an isolated cloud environment. Cloud agents are useful for: * Running parallel agents across multiple tasks * Running agents remotely on hosted computers (offloading compute from your local machine) @@ -124,7 +124,7 @@ Cloud agent conversations have a few differences from local conversations: * **Environment selector** - Choose which [Warp Environment](/agent-platform/cloud-agents/environments/) to run in * **Credits indicator** - Shows your remaining cloud agent credits -* **Different zero state** - The conversation header indicates "New Oz cloud agent conversation" +* **Different zero state** - The conversation header indicates "New cloud agent conversation" Cloud agent conversations are always stored in the cloud. For more details on accessing and sharing cloud conversations, see [Cloud-synced Conversations](/agent-platform/local-agents/cloud-conversations/). @@ -189,7 +189,7 @@ Auto-detection is enabled by default for new Warp users. For users who had Warp ### How to enter a conversation -There are several ways to start or enter an Oz agent conversation: +There are several ways to start or enter an agent conversation: #### A) Use the `/agent` or `/new` slash command @@ -311,7 +311,7 @@ If you prefer to type natural language at any point in a terminal session and ha ### Step 1 — Set new tabs to open in agent view -By default, new tabs and panes open in terminal mode. To launch directly into an Oz agent conversation instead: +By default, new tabs and panes open in terminal mode. To launch directly into an agent conversation instead: 1. Go to **Settings** > **Features** > **General**. 2. Change **Default mode for new sessions** to **Agent**. diff --git a/src/content/docs/agent-platform/local-agents/overview.mdx b/src/content/docs/agent-platform/local-agents/overview.mdx index 2764ed6..725b3aa 100644 --- a/src/content/docs/agent-platform/local-agents/overview.mdx +++ b/src/content/docs/agent-platform/local-agents/overview.mdx @@ -8,7 +8,7 @@ description: >- ## AI in Warp -Warp includes intelligent Oz agents designed to help you build, test, deploy, and debug while keeping you in control. Interactive agent conversations in Warp can look up commands, execute tasks, fix bugs, and adapt to your workflows. You can manage agent behavior directly, with full context from your Warp Drive and your team. +Warp includes intelligent agents designed to help you build, test, deploy, and debug while keeping you in control. Interactive agent conversations in Warp can look up commands, execute tasks, fix bugs, and adapt to your workflows. You can manage agent behavior directly, with full context from your Warp Drive and your team. :::note Warp's AI features can be globally disabled in **Settings** > **Agents** > **Warp Agent** with the AI toggle.\ diff --git a/src/content/docs/agent-platform/local-agents/session-sharing.mdx b/src/content/docs/agent-platform/local-agents/session-sharing.mdx index 7982c6d..b052f65 100644 --- a/src/content/docs/agent-platform/local-agents/session-sharing.mdx +++ b/src/content/docs/agent-platform/local-agents/session-sharing.mdx @@ -24,7 +24,7 @@ When you share an agent session, Warp publishes it to the cloud and generates a ## Sharing a session -1. Start or open an agent session in Warp. The agent can be an Oz agent, a third-party coding agent, or any interactive agent running in your terminal. +1. Start or open an agent session in Warp. The agent can be Warp's built-in agent, a third-party coding agent, or any interactive agent running in your terminal. 2. Open the share action from any of these entry points: * **Command Palette** - Search for "Share session" * **Pane header** - Click the overflow menu in the pane header diff --git a/src/content/docs/changelog/2026.mdx b/src/content/docs/changelog/2026.mdx index d29430c..13cdecc 100644 --- a/src/content/docs/changelog/2026.mdx +++ b/src/content/docs/changelog/2026.mdx @@ -297,7 +297,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * \[macOS] Right-clicking on text files in Finder allows you to open in Warp's code editor. * Send code review comments, attach diff hunks as context, and send substrings as context (`cmd L`) to 3rd party CLI tools such as Claude Code, Codex, Opencode, etc. -* Oz agents can now ask users clarifying questions during Agent Mode interactions. +* Agents can now ask users clarifying questions during Agent Mode interactions. * Warp's agent now suggests followups when it is done. **Improvements** @@ -308,7 +308,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * Added "Sign up" option to the settings gear menu for non-logged-in users. * MCP config files edited by the agent now show an 'Open config' button in the code diff header, making it easy to jump directly to the config file. * Added `/skills` support in CLI agent rich input for browsing and invoking agent-specific skills. -* Sandboxed Oz agents now have dedicated autonomy settings, instead of inheriting the team-level defaults. +* Sandboxed agents now have dedicated autonomy settings, instead of inheriting the team-level defaults. * Updated settings info icon tooltips to clarify they open documentation. * Improved quality and latency of prompt suggestions and suggested code diffs. * Cloud agents can now accept images and file attachments as context. @@ -337,7 +337,7 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * Fixed Oz session sharing failing behind HTTP proxies on port 80. * The `OZ_RUN_ID` environment variable is now available inside agent terminal sessions, set to the current task ID. * Improved error messages when agent session sharing fails, removing repetitive text and providing clearer guidance. -* Oz agents can now ask users clarifying questions during Agent Mode interactions. +* Agents can now ask users clarifying questions during Agent Mode interactions. ### 2026.03.25 (v0.2026.03.25.08.24) @@ -486,12 +486,12 @@ Submit bugs and feature requests on our [GitHub board!](https://github.com/warpd * Fixed "open file" button in code review diff view not working when the pane is maximized. * Fixed git metadata background operations after a terminal is closed. * Mobile soft keyboard will now work for LRCs. -* Oz agents now report more detailed information about session-sharing failures. +* Agents now report more detailed information about session-sharing failures. **Oz updates** -* Oz agent tasks now report structured error codes to the server, enabling better error tracking and retryability handling. -* Fixed Oz cloud agent not waiting for automatic error retry on network failures. +* Agent tasks now report structured error codes to the server, enabling better error tracking and retryability handling. +* Fixed cloud agent not waiting for automatic error retry on network failures. * Added support for passing arguments to skill invocations (`$ARGUMENTS`, `$N`) and for including user queries with the invocation. ### 2026.02.25 (v0.2026.02.25.08.24) @@ -564,7 +564,7 @@ Oz is Warp's orchestration platform for cloud agents: launch parallel agents, au [Read the launch post →](https://www.warp.dev/blog/oz-orchestration-platform-cloud-agents) -#### Oz Cloud Agents +#### Cloud Agents * **Run Cloud Agents from anywhere with built-in tracking** — start agents from Warp or via the CLI, triggers, or schedules. Every run is auditable and steerable. [Cloud Agents docs →](https://docs.warp.dev/agent-platform/cloud-agents/overview) * **Cloud environments for consistent execution** — configure Docker-based environments (unlimited repos + setup commands) and run agents in isolated cloud sandboxes. [Environments docs →](https://docs.warp.dev/agent-platform/cloud-agents/environments) diff --git a/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx b/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx index 43009fa..37dc72d 100644 --- a/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx +++ b/src/content/docs/enterprise/enterprise-features/architecture-and-deployment.mdx @@ -29,7 +29,7 @@ Warp's cloud agent infrastructure has four key components: ## Warp-hosted (SaaS) -Warp-hosted is the default deployment model. Oz agents run on Warp-managed infrastructure with no setup required from your team. +Warp-hosted is the default deployment model. Agents run on Warp-managed infrastructure with no setup required from your team. ### How it works diff --git a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx index 326b731..e81d703 100644 --- a/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx +++ b/src/content/docs/enterprise/enterprise-features/bring-your-own-llm.mdx @@ -12,7 +12,7 @@ This gives you control over cloud spend and model hosting, without changing how :::caution BYOLLM currently supports **AWS Bedrock** only. Coming soon: Azure Foundry and Google Vertex support. -BYOLLM applies to interactive Oz agents in the terminal. Oz cloud agents do not yet support BYOLLM routing. +BYOLLM applies to interactive agents in the terminal. Cloud agents do not yet support BYOLLM routing. ::: :::note @@ -35,7 +35,7 @@ Here's the high-level flow: 1. **Admin configures routing** - Your team admin sets routing policies in Warp's admin settings (e.g., "Route Claude Sonnet 4.5 through AWS Bedrock; disable direct Anthropic API"). 2. **Team members authenticate** - Each team member authenticates to AWS locally using the AWS CLI (`aws login`). -3. **Warp routes requests** - When a team member uses an interactive Oz agent in the terminal, Warp uses their short-lived session credentials to authenticate requests to your configured AWS Bedrock API endpoint. +3. **Warp routes requests** - When a team member uses an interactive agent in the terminal, Warp uses their short-lived session credentials to authenticate requests to your configured AWS Bedrock API endpoint. 4. **Inference executes in your cloud** - The model runs in your AWS account. Responses return to the Warp client. ### Credential lifecycle diff --git a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx index 66ba2fe..1e5ac98 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-developers.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-developers.mdx @@ -7,10 +7,10 @@ description: >- This guide helps developers get up and running with their team in Warp. You'll learn how to download Warp, log in with your organization's SSO, and configure key features like Codebase Context, Warp Drive, and Agent Profiles to accelerate your work across the entire SDLC (all while staying in your terminal). -When you use agents in Warp, you're using **Oz agents**. Oz is Warp's programmable agent for running and coordinating agents at scale, whether they run locally on your machine or in the cloud. Oz provides the orchestration, tracking, and control plane that makes scaling agent workflows seamless. +When you use agents in Warp, you're working with **Warp's built-in agents**. Oz is Warp's programmable agent for running and coordinating agents at scale, whether they run locally on your machine or in the cloud. Oz provides the orchestration, tracking, and control plane that makes scaling agent workflows seamless. :::note -New to Warp Enterprise? Try the [Enterprise quickstart](/enterprise/getting-started/quickstart/) for a 10-minute walkthrough of SSO login, Warp setup, and running your first Oz agent. +New to Warp Enterprise? Try the [Enterprise quickstart](/enterprise/getting-started/quickstart/) for a 10-minute walkthrough of SSO login, Warp setup, and running your first agent. ::: ## Step 1: Download and install Warp @@ -121,13 +121,13 @@ Once codebase indexing is enabled, you can index individual repositories: During indexing, your code is sent to Warp's servers for processing where embeddings are created and stored. The code itself is not saved—only the embeddings are persisted. This allows agents to understand your codebase structure and context without storing your actual source code. :::note -For Oz cloud agents: Code snippets may be stored as part of conversation records when agents create or modify files, since diffs are preserved in the conversation history. +For cloud agents: Code snippets may be stored as part of conversation records when agents create or modify files, since diffs are preserved in the conversation history. ::: ### Agent Profiles {/* Warp also supports third-party CLI agents (Claude Code, Codex, Copilot), so we say "built-in" rather than "every." */} -Agent Profiles let you configure how Warp's built-in Oz agents behave. Profiles give you direct control over model selection, autonomy, tools, and permissions for your agent workflows. +Agent Profiles let you configure how Warp's built-in agents behave. Profiles give you direct control over model selection, autonomy, tools, and permissions for your agent workflows. **Creating an Agent Profile:** @@ -232,7 +232,7 @@ Warp keeps you in your terminal with agent help across the entire SDLC: **Testing** * "Write unit tests for this function following our existing patterns" * "Run the test suite and explain what failed" -* Configure Oz cloud agents to run test suites and validate coverage on PRs in the background +* Configure cloud agents to run test suites and validate coverage on PRs in the background ### Learning resources @@ -251,7 +251,7 @@ For common login, SSO, and access issues, see the [Enterprise FAQ](/enterprise/g Now that you're set up: -* **Explore agent capabilities** - Learn about [agents in Warp](/agent-platform/local-agents/overview/) and [Oz cloud agents](/agent-platform/cloud-agents/overview/) +* **Explore agent capabilities** - Learn about [agents in Warp](/agent-platform/local-agents/overview/) and [cloud agents](/agent-platform/cloud-agents/overview/) * **Contribute to team knowledge** - Add useful Workflows, Prompts, and Rules to your team's Warp Drive to compound productivity gains across your team * **Stay updated** - Check the [Warp changelog](/changelog/) for new features diff --git a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx index 478d07b..9ce05e1 100644 --- a/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx +++ b/src/content/docs/enterprise/getting-started/getting-started-enterprise.mdx @@ -113,7 +113,7 @@ Alternatively, visit [app.warp.dev/admin](https://app.warp.dev/admin) directly. * **AI** - Configure general and AI autonomy settings for your team * **Models** - Configure which models are available to your team and AWS Bedrock * **Code** - Enable Codebase Context for your team -* **Platform** - Configure Oz cloud agent settings +* **Platform** - Configure cloud agent settings * **Privacy** - Configure user-generated content data collection, cloud conversation storage, and enterprise secret redaction * **Sharing** - Configure direct link sharing and "anyone with link" sharing permissions @@ -163,7 +163,7 @@ Once your team is set up: * **Agent Profiles** - Configure default [Agent Profiles](/agent-platform/capabilities/agent-profiles-permissions/) for different types of work to give teams appropriate autonomy and control * **BYOLLM** - Set up [Bring Your Own LLM](/enterprise/enterprise-features/bring-your-own-llm/) to route inference through your cloud infrastructure for data locality and cost control * **Monitor usage** - Review usage analytics in the Admin Panel to track adoption and measure engineering productivity gains -* **Self-hosting** - Run Oz agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions +* **Self-hosting** - Run agents on your own infrastructure to control where agents run and keep repository clones on your own machines. See [Self-Hosting](/agent-platform/cloud-agents/self-hosting/) for setup instructions ## Troubleshooting diff --git a/src/content/docs/enterprise/getting-started/quickstart.mdx b/src/content/docs/enterprise/getting-started/quickstart.mdx index 963e162..2dcfc35 100644 --- a/src/content/docs/enterprise/getting-started/quickstart.mdx +++ b/src/content/docs/enterprise/getting-started/quickstart.mdx @@ -2,12 +2,12 @@ title: Enterprise quickstart description: >- Get up and running with Warp Enterprise in under 10 minutes. Log in, set up - your terminal, and run your first Oz agent. + your terminal, and run your first agent. sidebar: label: "Quickstart" --- -This quickstart walks you through the essentials: logging in via SSO, setting up Warp, and running your first Oz agent. You can complete this in under 10 minutes. +This quickstart walks you through the essentials: logging in via SSO, setting up Warp, and running your first agent. You can complete this in under 10 minutes. ## Step 1: Log in via SSO @@ -32,20 +32,20 @@ If you have an existing Warp account from before your organization enabled SSO, 3. Launch Warp and log in with SSO (Step 1). 4. Verify you see your team name in **Settings** > **Teams**. -## Step 3: Configure and run your first Oz agent +## Step 3: Configure and run your first agent -When you use agents in Warp, you're using **Oz agents**. Oz is Warp's programmable agent for running and coordinating agents at scale, whether they run locally on your machine or in the cloud. +When you use agents in Warp, you're working with **Warp's built-in agents**. Oz is Warp's programmable agent for running and coordinating agents at scale, whether they run locally on your machine or in the cloud. ### Index your codebase 1. Navigate to a Git repository in Warp. 2. Warp automatically detects the repo and begins indexing. 3. Optionally, run `/init` to manually trigger indexing or re-indexing after significant code changes. -4. Once indexed, Oz agents understand your code structure, patterns, and conventions. +4. Once indexed, agents understand your code structure, patterns, and conventions. -### Run your first Oz agent locally +### Run your first agent locally -Start an Oz conversation right in the terminal. Try the following prompt: +Start a conversation right in the terminal. Try the following prompt: ``` Explain the architecture of this project @@ -60,9 +60,9 @@ Oz reads your codebase, understands its structure, and responds with a context-a * **Explore** - "What patterns does this repo use for error handling?" * **Plan** - Use `/plan` to have Oz create a structured task plan for complex features -## Step 4: Run an Oz cloud agent +## Step 4: Run a cloud agent -Oz cloud agents run in the cloud for background work, unlimited parallelization, and long-running tasks. +Cloud agents run in the cloud for background work, unlimited parallelization, and long-running tasks. ### Create an environment @@ -88,10 +88,10 @@ Once your environment is ready, use the following command to launch a cloud agen oz agent run-cloud --env my-env --prompt "Review the open PRs in this repo" ``` -Monitor and steer Oz cloud agents from the Oz dashboard or directly in Warp. +Monitor and steer cloud agents from the Oz dashboard or directly in Warp. ## Next steps * **Set up key features** - Follow the full [Getting started for developers](/enterprise/getting-started/getting-started-developers/) guide to configure Codebase Context, Warp Drive, MCP integrations, and Agent Profiles. -* **Explore Oz cloud agents** - Learn about [Oz cloud agents](/agent-platform/cloud-agents/overview/) for background automation and parallel workflows. +* **Explore cloud agents** - Learn about [cloud agents](/agent-platform/cloud-agents/overview/) for background automation and parallel workflows. * **Learn more** - Visit [Warp Guides](/guides/) for video tutorials and end-to-end workflows. diff --git a/src/content/docs/enterprise/index.mdx b/src/content/docs/enterprise/index.mdx index 2b7aa96..458c0d8 100644 --- a/src/content/docs/enterprise/index.mdx +++ b/src/content/docs/enterprise/index.mdx @@ -40,11 +40,11 @@ Warp Enterprise serves three primary audiences: * **Warp Drive team workspace** - Share Workflows, Notebooks, Prompts, Plans, Rules, and Environment Variables across your team * **Codebase Context** - Team-level code indexing helps agents understand your repositories and generate accurate, context-aware responses * **MCP integrations** - Connect to your team's tools (Linear, Sentry, Figma, GitHub, and more) for context-aware agent responses -* **Session sharing** - Collaborate on terminal sessions and Oz conversations with shareable links +* **Session sharing** - Collaborate on terminal sessions and conversations with shareable links -### Oz agent capabilities +### Agent capabilities * **State-of-the-art agents** - Multi-model agents with full terminal access, code editing, and autonomous task execution -* **Oz cloud agents** - Run agents in the cloud for unlimited parallelization, background automation, and long-running workflows. Perfect for PR reviews, scheduled tasks, and distributed work across multiple repositories +* **Cloud agents** - Run agents in the cloud for unlimited parallelization, background automation, and long-running workflows. Perfect for PR reviews, scheduled tasks, and distributed work across multiple repositories * **Integrated control plane** - Launch, orchestrate, and manage local, cloud, and autonomous agents from a unified interface. Track all agent activity across your team from the Oz dashboard * **Agent Profiles** - Customize agent behavior, models, autonomy levels, and permissions * **Rules and guardrails** - Enforce coding standards, tech stack preferences, and security practices through team-wide or project-specific rules diff --git a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx index 82febd9..b510159 100644 --- a/src/content/docs/enterprise/security-and-compliance/security-overview.mdx +++ b/src/content/docs/enterprise/security-and-compliance/security-overview.mdx @@ -119,7 +119,7 @@ Warp's operational security practices — including access controls, monitoring, ### Self-hosted deployments -Enterprise teams can self-host Oz cloud agent execution to control where agents run and keep repositories on their own infrastructure. +Enterprise teams can self-host cloud agent execution to control where agents run and keep repositories on their own infrastructure. Self-hosted deployments use a split architecture: * **Execution plane (customer-hosted)** - Repository clones, build artifacts, runtime secrets, and container filesystem state stay on your infrastructure @@ -158,7 +158,7 @@ Security-relevant controls include: * **Sharing** - Restrict or permit direct link sharing and "anyone with link" sharing permissions * **AI** - Configure AI autonomy settings and general agent behavior for the team * **Models** - Control which LLM models are available to team members, including AWS Bedrock -* **Platform** - Configure Oz cloud agent access and settings +* **Platform** - Configure cloud agent access and settings ## Security features for developers diff --git a/src/content/docs/enterprise/support-and-resources/billing.mdx b/src/content/docs/enterprise/support-and-resources/billing.mdx index 8110c6a..5a76c76 100644 --- a/src/content/docs/enterprise/support-and-resources/billing.mdx +++ b/src/content/docs/enterprise/support-and-resources/billing.mdx @@ -11,7 +11,7 @@ This page covers general information about credits, cloud agent costs, and BYOLL ## Credits -Warp uses a credit-based billing model. Any interaction with Oz agents consumes credits based on the complexity of the task, the model used, and the amount of context processed. +Warp uses a credit-based billing model. Any interaction with agents consumes credits based on the complexity of the task, the model used, and the amount of context processed. ### How credits work @@ -31,7 +31,7 @@ Credit allocations vary by contract. Contact your account manager for details on ## Cloud agent billing -Oz cloud agents consume credits that include a small hosting fee in addition to AI usage costs. +Cloud agents consume credits that include a small hosting fee in addition to AI usage costs. ### How credits are consumed @@ -65,7 +65,7 @@ Administrators can configure monthly spending limits and receive alerts to preve Enterprise administrators can set monthly spending limits across the following four categories: -* **Cloud spending limit** - Cap monthly spend on Oz cloud agent usage. +* **Cloud spending limit** - Cap monthly spend on cloud agent usage. * **Local spending limit** - Cap monthly spend on local agent usage in the Warp app. * **Total spending limit** - Cap combined monthly spend across both cloud and local agents. * **Per-user spending limit** - Cap monthly spend for any individual user. Set a default that applies to all users, or configure limits on a per-user basis for predictable individual spend. diff --git a/src/content/docs/enterprise/team-management/admin-panel.mdx b/src/content/docs/enterprise/team-management/admin-panel.mdx index be62cc2..a6dd8d7 100644 --- a/src/content/docs/enterprise/team-management/admin-panel.mdx +++ b/src/content/docs/enterprise/team-management/admin-panel.mdx @@ -102,7 +102,7 @@ The features available in the Admin Panel scale with your Warp plan: * **Full admin control** - Configure all available settings * **Enterprise secret redaction** - Custom regex patterns for secrets * **BYOLLM** - Route inference through your cloud infrastructure -* **Self-hosting cloud agent workers** - Deploy Oz cloud agent workers on your own infrastructure +* **Self-hosting cloud agent workers** - Deploy cloud agent workers on your own infrastructure * **Advanced compliance** - SOC 2, HIPAA, and custom data handling agreements * **Priority support** - Dedicated Slack/Teams channels @@ -248,11 +248,11 @@ For organizations with sensitive internal processes, disable "Anyone with link" ### Platform settings -Configure Oz cloud agent settings for your team, including GitHub authorization for automated workflows. +Configure cloud agent settings for your team, including GitHub authorization for automated workflows. **Enabled GitHub Orgs** -The **Enabled GitHub Orgs** setting associates your Warp team with one or more GitHub App installations, enabling Oz cloud agents initiated with a [team API key](/reference/cli/api-keys/) to clone repositories and open pull requests using the Oz by Warp GitHub App. +The **Enabled GitHub Orgs** setting associates your Warp team with one or more GitHub App installations, enabling cloud agents initiated with a [team API key](/reference/cli/api-keys/) to clone repositories and open pull requests using the Oz by Warp GitHub App. To configure: diff --git a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx index df5bd07..3481d09 100644 --- a/src/content/docs/enterprise/team-management/roles-and-permissions.mdx +++ b/src/content/docs/enterprise/team-management/roles-and-permissions.mdx @@ -44,7 +44,7 @@ Team Admins cannot demote or modify the Team Owner role. ### What members can do -* **Use agents** - Run Oz agents locally and in the cloud within the policies admins define. +* **Use agents** - Run agents locally and in the cloud within the policies admins define. * **Access team resources** - Use shared Workflows, Notebooks, Prompts, Rules, and Environment Variables in Warp Drive. * **Configure personal settings** - Adjust settings where admins have selected "Respect User Setting." * **Share sessions** - Collaborate via session sharing (if enabled by admins). diff --git a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx index d9d78fe..d3e7bcd 100644 --- a/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx +++ b/src/content/docs/guides/configuration/how-to-set-up-self-serve-data-analytics-with-skills.mdx @@ -19,7 +19,7 @@ Self-serve data analytics means anyone on your team can ask a data question and ## Walkthrough video -In this 40-minute livestream, Warp's data team demonstrates the workflow end-to-end, including the two Skills you'll install below and a third pattern (running the same Skills from Slack via an Oz cloud agent). Feel free to skip ahead if you prefer to follow the written steps. +In this 40-minute livestream, Warp's data team demonstrates the workflow end-to-end, including the two Skills you'll install below and a third pattern (running the same Skills from Slack via a cloud agent). Feel free to skip ahead if you prefer to follow the written steps. @@ -176,7 +176,7 @@ The `analysis-artifacts` Skill is largely stack-agnostic. It structures outputs, You installed two community Skills, customized the model index for your warehouse, and ran both a simple lookup and a full deep-dive analysis. -**Extend to Slack.** Wire the same two Skills into an Oz cloud agent configured with your dbt repo, and your teammates can ask data questions by @-mentioning Oz in a Slack channel, without opening a terminal. The Agent clones the repo, picks up the Skills from `.agents/skills/`, and replies in-thread. See the [Slack integration docs](https://docs.warp.dev/agent-platform/cloud-agents/integrations/slack/) and [Skills as Agents](https://docs.warp.dev/agent-platform/cloud-agents/skills-as-agents/) for setup. +**Extend to Slack.** Wire the same two Skills into a cloud agent configured with your dbt repo, and your teammates can ask data questions by @-mentioning Oz in a Slack channel, without opening a terminal. The agent clones the repo, picks up the Skills from `.agents/skills/`, and replies in-thread. See the [Slack integration docs](https://docs.warp.dev/agent-platform/cloud-agents/integrations/slack/) and [Skills as Agents](https://docs.warp.dev/agent-platform/cloud-agents/skills-as-agents/) for setup. Explore related guides and features: diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx index 3ffaf9b..8d32937 100644 --- a/src/content/docs/index.mdx +++ b/src/content/docs/index.mdx @@ -53,7 +53,7 @@ Local agents keep you in control. You can review changes, steer the agent mid-ta ### Cloud agents -Oz Cloud Agents run in the background on Warp's infrastructure (or your own) for automation at scale. +Cloud agents run in the background on Warp's infrastructure (or your own) for automation at scale. * **Triggers**: React to events from Slack, Linear, GitHub, or custom webhooks * **Schedules**: Run recurring tasks like dependency updates or dead code removal diff --git a/src/content/docs/knowledge-and-collaboration/warp-drive/workflows.mdx b/src/content/docs/knowledge-and-collaboration/warp-drive/workflows.mdx index baf7b73..132be52 100644 --- a/src/content/docs/knowledge-and-collaboration/warp-drive/workflows.mdx +++ b/src/content/docs/knowledge-and-collaboration/warp-drive/workflows.mdx @@ -19,7 +19,7 @@ You can create a new workflow from various entry points in Warp: * From Warp Drive, + > New workflow * Using Block Actions, Save as Workflow -* From Oz agent results, Save as Workflow +* From agent results, Save as Workflow * From the [Command Palette](/terminal/command-palette/), Create a New Personal Workflow Any of these entry points will open the workflow editor where you can: @@ -81,7 +81,7 @@ Once a workflow has been created, you can edit it at any time, as long as you ha #### AI Autofill -Workflows also have the option to use an [Oz agent](/agent-platform/local-agents/overview/) to automatically generate a title, descriptions, or parameters. +Workflows also have the option to use an [agent](/agent-platform/local-agents/overview/) to automatically generate a title, descriptions, or parameters. * Create or edit a Workflow, in the edit view you should see the option to AutoFill. * Warp will fill in the fields based on the Workflow you're creating. diff --git a/src/content/docs/quickstart.mdx b/src/content/docs/quickstart.mdx index 9275556..04f6ae8 100644 --- a/src/content/docs/quickstart.mdx +++ b/src/content/docs/quickstart.mdx @@ -116,5 +116,5 @@ Now that you have the basics, check out the features that make Warp a full devel * **[Customizing Warp](/getting-started/quickstart/customizing-warp/)** — Pick a theme, configure your prompt, choose your AI model, and import keybindings from another terminal. * **[Codebase Context](/agent-platform/capabilities/codebase-context/)** — Index your Git repositories so agents understand your code and give context-aware answers across large, multi-repo systems. -* **[Oz cloud agents](/agent-platform/cloud-agents/overview/)** — Run agents in the background for PR review, issue triage, dependency updates, and other tasks that don't need your immediate attention. +* **[Cloud agents](/agent-platform/cloud-agents/overview/)** — Run agents in the background for PR review, issue triage, dependency updates, and other tasks that don't need your immediate attention. * **[Keyboard shortcuts](/getting-started/keyboard-shortcuts/)** — The full shortcut reference for power users. diff --git a/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx b/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx index 776b2da..1eb31e6 100644 --- a/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx +++ b/src/content/docs/reference/api-and-sdk/demo-sentry-monitoring-with-sdk.mdx @@ -1,7 +1,7 @@ --- title: "Demo: Sentry monitoring with SDK" description: >- - Build a Sentry webhook handler that triggers Oz agents to investigate errors + Build a Sentry webhook handler that triggers agents to investigate errors and create draft PRs. --- import VideoEmbed from '@components/VideoEmbed.astro'; diff --git a/src/content/docs/reference/api-and-sdk/index.mdx b/src/content/docs/reference/api-and-sdk/index.mdx index 045ca86..9683881 100644 --- a/src/content/docs/reference/api-and-sdk/index.mdx +++ b/src/content/docs/reference/api-and-sdk/index.mdx @@ -24,7 +24,7 @@ This page is a high-level overview.\ For full API endpoint details, please refer to the [**Agents API Reference**](/api)**.** For schema definitions, see the SDK repos: [**Python SDK**](https://github.com/warpdotdev/oz-sdk-python) and [**TypeScript SDK**](https://github.com/warpdotdev/oz-sdk-typescript). ::: -### Oz Agent SDK +### Oz SDK Oz provides official [Python](https://github.com/warpdotdev/oz-sdk-python) and [TypeScript](https://github.com/warpdotdev/oz-sdk-typescript) SDKs that wrap the Oz API with: @@ -126,7 +126,7 @@ The API shares a set of reusable models across endpoints. Detailed JSON schemas, --- -## Oz Agent SDKs +## Oz SDKs ### Python SDK diff --git a/src/content/docs/reference/index.mdx b/src/content/docs/reference/index.mdx index 360872b..0747cdc 100644 --- a/src/content/docs/reference/index.mdx +++ b/src/content/docs/reference/index.mdx @@ -4,7 +4,7 @@ description: >- Technical reference documentation for the Oz CLI, API, and SDK. --- -This section covers the programmatic interfaces for running and managing Oz agents in CI pipelines, scripts, backend services, and custom tooling. +This section covers the programmatic interfaces for running and managing agents in CI pipelines, scripts, backend services, and custom tooling. ## CLI @@ -15,7 +15,7 @@ The [Oz CLI](/reference/cli/) lets you run and configure agents from any environ - [MCP Servers](/reference/cli/mcp-servers/) - Pass MCP server configuration to agent runs using the `--mcp` flag, by UUID, inline JSON, or file path. - [Skills](/reference/cli/skills/) - Run agents from reusable instruction sets stored in your repositories using the `--skill` flag. - [Warp Drive Context](/reference/cli/warp-drive/) - Reference saved prompts, notebooks, workflows, and rules from Warp Drive directly in CLI agent commands. -- [Integration Setup](/reference/cli/integration-setup/) - Configure environments and connect external tools like Slack and Linear so you can trigger Oz agents from outside the terminal. +- [Integration Setup](/reference/cli/integration-setup/) - Configure environments and connect external tools like Slack and Linear so you can trigger agents from outside the terminal. - [Troubleshooting](/reference/cli/troubleshooting/) - Find solutions to common CLI errors, including authentication issues, agent failures, environment problems, and Docker image issues. ## API & SDK diff --git a/src/content/docs/support-and-community/community/open-source-partnership.mdx b/src/content/docs/support-and-community/community/open-source-partnership.mdx index 077761a..8694c0a 100644 --- a/src/content/docs/support-and-community/community/open-source-partnership.mdx +++ b/src/content/docs/support-and-community/community/open-source-partnership.mdx @@ -1,21 +1,21 @@ --- title: Oz Open Source Partnership description: >- - Warp supports high-impact open source projects with free Oz agent credits + Warp supports high-impact open source projects with free agent credits through the Oz Open Source Partnership program. --- -Warp is committed to supporting the open source community. Through the Oz Open Source Partnership program, we offer free Oz agent usage credits to high-impact open source projects, helping maintainers and contributors accelerate their development workflows. +Warp is committed to supporting the open source community. Through the Oz Open Source Partnership program, we offer free agent usage credits to high-impact open source projects, helping maintainers and contributors accelerate their development workflows. ## What you get -* **Free Oz credits** - Receive complimentary credits to run Oz agents on your open source project -* **Oz agent access** - Use cloud agents to automate tasks like code review, bug triage, documentation, and more across your repositories -* **Ongoing support** - Warp partners with accepted projects to ensure they get the most value from Oz agents +* **Free Oz credits** - Receive complimentary credits to run agents on your open source project +* **Agent access** - Use cloud agents to automate tasks like code review, bug triage, documentation, and more across your repositories +* **Ongoing support** - Warp partners with accepted projects to ensure they get the most value from agents ## Who can apply -The Oz Open Source Partnership program is designed for actively maintained, high-impact open source projects. When reviewing applications, we consider factors like community size, project activity, and the potential impact of Oz agents on your workflow. +The Oz Open Source Partnership program is designed for actively maintained, high-impact open source projects. When reviewing applications, we consider factors like community size, project activity, and the potential impact of agents on your workflow. :::note Have questions about the program? Reach out to us at [support@warp.dev](mailto:support@warp.dev). @@ -26,5 +26,5 @@ Have questions about the program? Reach out to us at [support@warp.dev](mailto:s Tell us about your open source project by filling out the [application form](https://tally.so/r/LZWxqG). We'll review your submission and follow up with next steps. :::note -The Oz Open Source Partnership program provides free Oz agent credits for open source projects. This is separate from Warp's open source client — the Warp client is published under AGPL v3 at [`warpdotdev/warp`](https://github.com/warpdotdev/warp); see [Contributing to Warp](/support-and-community/community/contributing/). For sponsorship opportunities for your project, reach out to [partnerships@warp.dev](mailto:partnerships@warp.dev). +The Oz Open Source Partnership program provides free agent credits for open source projects. This is separate from Warp's open source client — the Warp client is published under AGPL v3 at [`warpdotdev/warp`](https://github.com/warpdotdev/warp); see [Contributing to Warp](/support-and-community/community/contributing/). For sponsorship opportunities for your project, reach out to [partnerships@warp.dev](mailto:partnerships@warp.dev). ::: diff --git a/src/content/docs/support-and-community/index.mdx b/src/content/docs/support-and-community/index.mdx index 3621713..c58f94b 100644 --- a/src/content/docs/support-and-community/index.mdx +++ b/src/content/docs/support-and-community/index.mdx @@ -43,7 +43,7 @@ We host [live events](https://luma.com/warpdotdev) year-round — product demos, * [**Warp Preview**](/support-and-community/community/warp-preview-and-alpha-program/) — Try experimental features before anyone else. Your feedback directly shapes what ships. * [**Refer a Friend**](/support-and-community/community/refer-a-friend/) — Send Warp to a developer you think would love it. Earn themes, swag, and gift cards. -* [**Oz Open Source Partnership**](/support-and-community/community/open-source-partnership/) — Free Oz agent credits for high-impact open source projects. +* [**Oz Open Source Partnership**](/support-and-community/community/open-source-partnership/) — Free agent credits for high-impact open source projects. :::note **Ambassador program** diff --git a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx index cd2f84c..37db3d1 100644 --- a/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/bring-your-own-api-key.mdx @@ -22,7 +22,7 @@ When you add your own model API keys in Warp, those keys are stored **locally on Warp uses these API keys to directly route your agent requests to the model provider you've configured. :::caution -BYOK does not apply to [Oz Cloud Agents](/agent-platform/cloud-agents/overview/). Because your API keys are stored locally on your device, they are not available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). +BYOK does not apply to [Cloud Agents](/agent-platform/cloud-agents/overview/). Because your API keys are stored locally on your device, they are not available to cloud-hosted agent runs. Cloud agent runs always consume [Warp credits](/support-and-community/plans-and-billing/credits/). ::: When a model is selected using your own key: @@ -77,7 +77,7 @@ Some AI-powered features are not affected by BYOK and are included as part of Wa | ----------------------------------------------------------------------------- | ------------------- | -------------------------------------------------------------------- | | [Active AI Recommendations](/agent-platform/local-agents/active-ai/) | No | Always included with Build and higher plans. | | [Codebase Context](/agent-platform/capabilities/codebase-context/) | Yes | Uses Warp's AI infrastructure and consumes credits. | -| [Oz Cloud Agents](/agent-platform/cloud-agents/overview/) | Yes | BYOK keys are stored locally and not available to cloud-hosted runs. | +| [Cloud Agents](/agent-platform/cloud-agents/overview/) | Yes | BYOK keys are stored locally and not available to cloud-hosted runs. | These features will continue to function normally regardless of whether you’ve configured BYOK. diff --git a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx index 5d9ddbe..50abbb0 100644 --- a/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx +++ b/src/content/docs/support-and-community/plans-and-billing/pricing-faqs.mdx @@ -164,7 +164,7 @@ Warp doesn’t currently offer discounts for students or non-profits. We recomme For open source teams, two paths are available: -* The [Oz Open Source Partnership](/support-and-community/community/open-source-partnership/) program offers free Oz agent credits to high-impact open source projects. +* The [Oz Open Source Partnership](/support-and-community/community/open-source-partnership/) program offers free agent credits to high-impact open source projects. * Warp's client itself is open source under [AGPL v3](https://github.com/warpdotdev/warp/blob/master/LICENSE-AGPL), so you can build, run, and contribute to it directly. See [Contributing to Warp](/support-and-community/community/contributing/) for the flow. ### Where is Warp Drive data for my team stored? diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx index e27cdac..92edb5c 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/known-issues.mdx @@ -23,7 +23,7 @@ To enable Blocks over SSH, Warp uses an SSH Wrapper function; navigate to settin ### Online features don't work -There is a known issue that can occur that causes online features to break ([Oz agent](/agent-platform/local-agents/overview/), [Generate](/agent-platform/local-agents/overview/), [Block Sharing](/terminal/blocks/block-sharing/), [Refer a Friend](/support-and-community/community/refer-a-friend/) ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps: +There is a known issue that can occur that causes online features to break ([Agent](/agent-platform/local-agents/overview/), [Generate](/agent-platform/local-agents/overview/), [Block Sharing](/terminal/blocks/block-sharing/), [Refer a Friend](/support-and-community/community/refer-a-friend/) ). This is due to the login token going stale, typically due to a password change, and can be resolved by the following steps: diff --git a/src/content/docs/support-and-community/troubleshooting-and-support/using-warp-offline.mdx b/src/content/docs/support-and-community/troubleshooting-and-support/using-warp-offline.mdx index 3a071c2..b467296 100644 --- a/src/content/docs/support-and-community/troubleshooting-and-support/using-warp-offline.mdx +++ b/src/content/docs/support-and-community/troubleshooting-and-support/using-warp-offline.mdx @@ -17,7 +17,7 @@ Warp is "Offline" when you aren't connected to the internet, or if you're blocki Warp’s cloud-based features which require an internet connection will not work in offline mode. Those features include: * [Warp Drive](/knowledge-and-collaboration/warp-drive/#using-warp-drive-offline) (Some files may be read-only in offline mode) -* [Oz agent](/agent-platform/local-agents/overview/) +* [Agent](/agent-platform/local-agents/overview/) * [Agent Mode](/agent-platform/local-agents/interacting-with-agents/) * [Generate](/agent-platform/local-agents/overview/) * [AI Autofill](/knowledge-and-collaboration/warp-drive/workflows/#warp-ai-autofill) diff --git a/src/content/docs/terminal/input/classic-input.mdx b/src/content/docs/terminal/input/classic-input.mdx index 3519599..bdc1bd6 100644 --- a/src/content/docs/terminal/input/classic-input.mdx +++ b/src/content/docs/terminal/input/classic-input.mdx @@ -29,22 +29,22 @@ You can enter Agent Mode in a few ways: - * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an Oz agent. + * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an agent. * Use the keyboard shortcut `⌘+I` to toggle into Agent Mode, or type `*+Space`. * Click the “AI” sparkles icon in the menu bar, and this will open a new terminal pane that starts in Agent Mode. - * From a block you want to ask an Oz agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". + * From a block you want to ask an agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". - * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an Oz agent. + * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an agent. * Use the keyboard shortcut `Ctrl+I` to toggle into Agent Mode, or type `*+Space`. * Click the "AI" sparkles icon in the menu bar, and this will open a new terminal pane that starts in Agent Mode. - * From a block you want to ask an Oz agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". + * From a block you want to ask an agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". - * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an Oz agent. + * Type any natural language, like a task or a question, in the terminal input. Warp will recognize natural language with a local auto-detection feature and prepare to send your query to an agent. * Use the keyboard shortcut `Ctrl+I` to toggle into Agent Mode, or type `*+Space`. * Click the "AI" sparkles icon in the menu bar, and this will open a new terminal pane that starts in Agent Mode. - * From a block you want to ask an Oz agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". + * From a block you want to ask an agent about, you can click the sparkles icon in the toolbelt, or click on its block context menu item "Attach block(s) to AI query". diff --git a/src/content/docs/terminal/windows/vertical-tabs.mdx b/src/content/docs/terminal/windows/vertical-tabs.mdx index 2137af1..dcee474 100644 --- a/src/content/docs/terminal/windows/vertical-tabs.mdx +++ b/src/content/docs/terminal/windows/vertical-tabs.mdx @@ -33,7 +33,7 @@ Vertical tabs are especially useful when running multiple coding agents side by ### Tab management * **Search, drag and drop, and renaming** - Filter panes by title, directory, or branch; reorder tabs or move panes between tabs by dragging; double-click a tab to rename it inline. -* **New tab menu** - Create agent tabs, terminal tabs, Oz cloud agent sessions, worktree configs, and [Tab Configs](/terminal/windows/tab-configs/) from a unified **+** menu. +* **New tab menu** - Create agent tabs, terminal tabs, cloud agent sessions, worktree configs, and [Tab Configs](/terminal/windows/tab-configs/) from a unified **+** menu. ## Enabling vertical tabs @@ -141,7 +141,7 @@ Click the **+** button in the control bar to open the new tab menu. The menu inc * **Agent** - Open a new agent tab. * **Terminal** - Open a new terminal tab. -* **Oz cloud agent** - Open a new Oz cloud agent session tab. +* **Cloud agent** - Open a new cloud agent session tab. * **Tab Configs** - Any [Tab Configs](/terminal/windows/tab-configs/) you've created appear as menu items for one-click setup. * **New worktree config** - Create a new worktree-based Tab Config. * **New tab config** - Create a new Tab Config from a starter template. diff --git a/src/pages/api.astro b/src/pages/api.astro index 84c4d00..2bff103 100644 --- a/src/pages/api.astro +++ b/src/pages/api.astro @@ -2,7 +2,7 @@ // Standalone Scalar API reference — not embedded in Starlight. // Accessible at docs.warp.dev/api // Spec lives at `developers/agent-api-openapi.yaml`, synced from the -// upstream Oz Agent API source. Re-sync that file when the API changes +// upstream Agent API source. Re-sync that file when the API changes // and this page picks it up at the next build. // // Note on `set:html={specJson}` below: the injected value is JSON.stringify() @@ -27,24 +27,24 @@ const specJson = JSON.stringify(specObject); - Oz Agent API Reference | Warp - + Agent API Reference | Warp + - - + + - + - - + + {/* PushFeedback CSS + JS are NOT loaded here — the lazy loader inside @@ -206,8 +206,8 @@ const specJson = JSON.stringify(specObject); // doesn't show a fake "interactive" affordance (per scalar/scalar#5079). defaultOpenAllTags: true, metaData: { - title: 'Oz Agent API Reference', - description: 'Interactive API reference for the Oz Agent API.', + title: 'Agent API Reference', + description: 'Interactive API reference for the Agent API.', }, // --------------------------------------------------------------- // Scalar consumes `customCss` as a runtime string, so we can't