From f124bfacd205ed1f513c2019a162ad08a98a814f Mon Sep 17 00:00:00 2001 From: rachaelrenk Date: Mon, 15 Jun 2026 09:04:38 +0000 Subject: [PATCH 1/4] docs: add AEO cross-links for agents and orchestration Add high-confidence internal cross-links for the agents, cloud agents, and orchestration topic area, grounded in Peec AEO signals (scheduling, managing and observing multiple agents) and existing docs: - Scheduled Agents reference now links to the Scheduled Agents quickstart for a guided, no-CLI setup path. - Run multiple agents at once guide now links to Agent notifications and the Agent Management Panel for notification setup and run observability. Co-Authored-By: Oz --- .../agent-platform/cloud-agents/triggers/scheduled-agents.mdx | 2 ++ .../running-multiple-agents-at-once-with-warp.mdx | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx index a6f7f11b..9bc88ecd 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx +++ b/src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx @@ -14,6 +14,8 @@ Warp's Scheduled Agents let you run cloud agents automatically on a **recurring Scheduled Agents run in the background on Warp’s infrastructure. Each run starts from a clean session, executes a fixed prompt, and produces its own task and session history that can be inspected after the fact. +For a guided, no-CLI walkthrough that creates a recurring agent from the Oz web app, see the [Scheduled Agents quickstart](/agent-platform/cloud-agents/triggers/scheduled-agents-quickstart/). This page is the full reference for managing schedules with the Oz CLI. + If you're deciding whether to use a schedule, Slack or Linear trigger, GitHub Actions, the Oz CLI, or the API, see [Run agents unattended with schedules and triggers](/guides/agent-workflows/how-to-run-unattended-agents/). --- diff --git a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx index b20db6fe..f5f8ca93 100644 --- a/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx +++ b/src/content/docs/guides/agent-workflows/running-multiple-agents-at-once-with-warp.mdx @@ -29,7 +29,7 @@ Each agent runs in its own thread, complete with: * Notifications when blocked or completed * Separate command histories -Because Warp is a desktop app, it can send system notifications to alert you when an agent finishes or when it needs review. +Because Warp is a desktop app, it can send system notifications to alert you when an agent finishes or when it needs review. To set up notifications for Claude Code, Codex, and OpenCode, see [Agent notifications](/agent-platform/capabilities/agent-notifications/). --- @@ -94,6 +94,6 @@ Open the Agent Mode Dashboard to see: * Completed tasks * Logs and outputs -You can refine or cancel tasks mid-run if needed, or switch back to manual commands. +You can refine or cancel tasks mid-run if needed, or switch back to manual commands. To track these runs across your account and team, including cloud agent runs, open the [Agent Management Panel](/agent-platform/cloud-agents/managing-cloud-agents/) in the Warp app. For a workflow-oriented setup guide that covers task decomposition, worktrees, cloud orchestration, validation, and review handoff, see [How to run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/). From a7e19283a1af8a8d4fd2d2ba19aa918f87948758 Mon Sep 17 00:00:00 2001 From: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Date: Tue, 16 Jun 2026 14:41:23 -0600 Subject: [PATCH 2/4] docs: add AEO cross-links for integrations and triggers pages Transfer changes from PR #232 (docs/aeo-crosslinks-agents-orchestration-20260616): - integrations/index.mdx: add managing-cloud-agents cross-link - triggers/index.mdx: add managing-cloud-agents cross-link after trigger types Co-Authored-By: Oz --- .../docs/agent-platform/cloud-agents/integrations/index.mdx | 1 + src/content/docs/agent-platform/cloud-agents/triggers/index.mdx | 2 ++ 2 files changed, 3 insertions(+) diff --git a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx b/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx index 1f265b06..dd46a026 100644 --- a/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/integrations/index.mdx @@ -35,3 +35,4 @@ Use the setup walkthrough below for a quick look at how environments connect to * [GitHub Actions](/agent-platform/cloud-agents/integrations/github-actions/) - Run agents from CI workflows and repository events. * [GitLab](/agent-platform/cloud-agents/integrations/gitlab/), [Bitbucket](/agent-platform/cloud-agents/integrations/bitbucket/), and [Azure DevOps](/agent-platform/cloud-agents/integrations/azure-devops/) - Connect non-GitHub repositories with tokens and Warp-managed secrets. * [AWS, GCP, and other cloud providers](/agent-platform/cloud-agents/integrations/cloud-providers/) - Give cloud agents short-lived access to cloud services. +* [Managing cloud agents](/agent-platform/cloud-agents/managing-cloud-agents/) - Monitor and review integration-triggered runs across your team by source, status, or creator. diff --git a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx b/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx index 9fae1b70..cf13dc1c 100644 --- a/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx +++ b/src/content/docs/agent-platform/cloud-agents/triggers/index.mdx @@ -17,3 +17,5 @@ If you're choosing between schedules, Slack, Linear, GitHub Actions, the Oz CLI, * **[CLI](/reference/cli/)** - Trigger cloud agents directly from your terminal using the Oz CLI. * **[API & SDK](/reference/api-and-sdk/)** - Programmatically trigger agents via the Warp API or SDK. * **[Integrations](/agent-platform/cloud-agents/integrations/)** - Trigger agents from external services like Slack, Linear, or GitHub Actions. + +After a trigger fires, track and review the resulting runs across your team from the [Agent Management Panel and Oz web app Runs page](/agent-platform/cloud-agents/managing-cloud-agents/), where you can filter by source, status, day, or creator. From 12f20e4b025d2e4fbc917e9f97edaf9abdfdae95 Mon Sep 17 00:00:00 2001 From: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Date: Tue, 16 Jun 2026 15:14:49 -0600 Subject: [PATCH 3/4] feat: add run logging and Slack notifications to aeo_crosslink_audit skill - Add .agents/logs/aeo_crosslink_audit_runs.md as a durable run log committed to main after every scheduled run (PR or no-change) - Add Environment requirements section documenting SLACK_BOT_TOKEN and SLACK_CHANNEL_ID (same secrets already used by weekly-404-monitor) - Add workflow steps 7 and 8: write run log entry, then post simple text notification to #growth-docs; both fall back to run output gracefully - Add Run log format and Slack notification format reference sections - Update stale manual-sharing note in no-change report section Co-Authored-By: Oz --- .agents/logs/aeo_crosslink_audit_runs.md | 9 +++ .agents/skills/aeo_crosslink_audit/SKILL.md | 67 ++++++++++++++++++++- 2 files changed, 75 insertions(+), 1 deletion(-) create mode 100644 .agents/logs/aeo_crosslink_audit_runs.md diff --git a/.agents/logs/aeo_crosslink_audit_runs.md b/.agents/logs/aeo_crosslink_audit_runs.md new file mode 100644 index 00000000..0d6237c0 --- /dev/null +++ b/.agents/logs/aeo_crosslink_audit_runs.md @@ -0,0 +1,9 @@ +# AEO crosslink audit run log + +Appended by each scheduled agent run. Most recent entry first. + +This log tracks every run of the `aeo_crosslink_audit` skill — both runs that opened a PR and runs that wrote a no-change report — so the team can answer questions like "how many crosslink PRs have we opened in the last month?" without replaying individual Oz runs. + +**Format**: see the `## Run log format` section in `.agents/skills/aeo_crosslink_audit/SKILL.md`. + +--- diff --git a/.agents/skills/aeo_crosslink_audit/SKILL.md b/.agents/skills/aeo_crosslink_audit/SKILL.md index cd9badeb..0d3bdf14 100644 --- a/.agents/skills/aeo_crosslink_audit/SKILL.md +++ b/.agents/skills/aeo_crosslink_audit/SKILL.md @@ -24,6 +24,15 @@ Do not: - Add keyword-stuffed text. - Force Peec or Google Search Console signals into docs when they do not support a useful reader journey. +## Environment requirements + +The following environment secrets should be set in the Oz cloud agent environment: + +- `SLACK_BOT_TOKEN` — Slack bot token for posting to `#growth-docs`. If unavailable, write the notification body to the run output instead and skip Slack posting. +- `SLACK_CHANNEL_ID` — Slack channel ID for `#growth-docs`. Find it in Slack by right-clicking the channel → Copy link (the ID begins with `C`). If unavailable, skip Slack posting. + +Do NOT print, log, commit, or include secret values in reports or Slack messages. + ## Source data Use the smallest reliable set of source data needed to justify link changes: @@ -46,6 +55,16 @@ If Peec snapshot or Google Search Console data is unavailable, say what could no 5. **Run self-review.** Apply the quality gates in this skill before opening a PR or writing a no-change report. 6. **Open a PR or report no changes.** Open a PR only when there are at least 2 high-confidence link additions. Otherwise, write a no-change report in the Oz run output. +7. **Write run log entry.** After completing step 6, prepend a new entry to `.agents/logs/aeo_crosslink_audit_runs.md` using the format in the "Run log format" section below. Commit the updated log file directly to `main` with this commit message: + + ```text + chore: log aeo crosslink audit run YYYY-MM-DD + ``` + + If the git push fails, write the log entry to the run output instead and continue to step 8. + +8. **Post Slack notification.** After writing the log entry, post a brief message to `#growth-docs` using `SLACK_BOT_TOKEN` and `SLACK_CHANNEL_ID`. Use the format in the "Slack notification format" section below. If either secret is unavailable, write the notification body to the run output instead. + ## Link quality rules When adding links, follow the link style guidance in `AGENTS.md` and validate with `style_lint`. @@ -140,7 +159,7 @@ Use this format: - [One specific improvement for the next run.] ``` -For the pilot, no-change reports stay in the Oz run output. If team input is needed, share the Oz run link manually in `#growth-docs`. +No-change reports stay in the Oz run output. The Oz run link is posted automatically to `#growth-docs` as part of step 8. ## Human review expectations @@ -150,6 +169,52 @@ The human reviewer should be able to understand the PR or no-change report witho - Flag any uncertainty directly. - Avoid hiding product or terminology questions in the diff. +## Run log format + +Prepend each new entry at the top of `.agents/logs/aeo_crosslink_audit_runs.md`, immediately after the `---` separator line. Use this format: + +```markdown +## YYYY-MM-DD — [PR opened | No change] + +- **Run**: [Oz run URL if available, otherwise the run ID] +- **Source signals**: Peec [available | unavailable], GSC [available | unavailable] +- **PR**: [PR URL | N/A] +- **Links proposed / added**: [N proposed, N added | N/A] +- **Pages touched**: [comma-separated file paths | N/A] +- **Themes**: [one sentence on recurring content gaps or topics observed, or "none observed"] +- **No-change reason**: [low confidence | lack of signals | [other reason] | N/A] +``` + +Keep each entry to 7 fields and under 10 lines. Do not add narrative prose. + +## Slack notification format + +Use a simple text message (not Block Kit). The message should be scannable in under 30 seconds. + +**PR opened:** + +``` +✅ AEO crosslink audit · YYYY-MM-DD +PR opened: [PR URL] +Links added: [N links] across [N pages]: [page names] +Signals: [Peec | GSC | Peec + GSC] +Oz run: [run URL] +``` + +**No change:** + +``` +ℹ️ AEO crosslink audit · YYYY-MM-DD — No changes +Checked: agents, cloud agents, and orchestration docs +No PR: [brief reason — e.g., "fewer than 2 high-confidence opportunities"] +Oz run: [run URL] +``` + +Rules: +- Post on every run, including no-change runs. +- Never include raw secret values, personal access tokens, or credential file paths in the Slack message. +- If the Oz run URL is unavailable, omit that line rather than posting a broken link. + ## Future expansion boundaries Do not implement future expansion ideas in this pilot skill. If the audit finds opportunities outside internal cross-linking, mention them only as follow-up recommendations in the PR body or no-change report. From a12126f5de97dba17ad652e5b97308749e94b994 Mon Sep 17 00:00:00 2001 From: Rachael Rose Renk <91027132+rachaelrenk@users.noreply.github.com> Date: Tue, 16 Jun 2026 15:24:46 -0600 Subject: [PATCH 4/4] fix: address PR review comments - Step 7: specify clean main checkout/worktree and path-limited staging to prevent accidentally pushing PR branch edits to main alongside log - Log file header: 'Appended' -> 'New entries are prepended' to match the skill's actual prepend instruction Co-Authored-By: Oz --- .agents/logs/aeo_crosslink_audit_runs.md | 2 +- .agents/skills/aeo_crosslink_audit/SKILL.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.agents/logs/aeo_crosslink_audit_runs.md b/.agents/logs/aeo_crosslink_audit_runs.md index 0d6237c0..90f884a2 100644 --- a/.agents/logs/aeo_crosslink_audit_runs.md +++ b/.agents/logs/aeo_crosslink_audit_runs.md @@ -1,6 +1,6 @@ # AEO crosslink audit run log -Appended by each scheduled agent run. Most recent entry first. +New entries are prepended by each scheduled agent run. Most recent entry first. This log tracks every run of the `aeo_crosslink_audit` skill — both runs that opened a PR and runs that wrote a no-change report — so the team can answer questions like "how many crosslink PRs have we opened in the last month?" without replaying individual Oz runs. diff --git a/.agents/skills/aeo_crosslink_audit/SKILL.md b/.agents/skills/aeo_crosslink_audit/SKILL.md index 0d3bdf14..13dd154a 100644 --- a/.agents/skills/aeo_crosslink_audit/SKILL.md +++ b/.agents/skills/aeo_crosslink_audit/SKILL.md @@ -55,7 +55,7 @@ If Peec snapshot or Google Search Console data is unavailable, say what could no 5. **Run self-review.** Apply the quality gates in this skill before opening a PR or writing a no-change report. 6. **Open a PR or report no changes.** Open a PR only when there are at least 2 high-confidence link additions. Otherwise, write a no-change report in the Oz run output. -7. **Write run log entry.** After completing step 6, prepend a new entry to `.agents/logs/aeo_crosslink_audit_runs.md` using the format in the "Run log format" section below. Commit the updated log file directly to `main` with this commit message: +7. **Write run log entry.** After completing step 6, update `.agents/logs/aeo_crosslink_audit_runs.md` from a clean checkout or worktree based on the latest `main`, prepend the new entry using the format in the "Run log format" section below, stage only `.agents/logs/aeo_crosslink_audit_runs.md`, and commit it directly to `main` with this commit message: ```text chore: log aeo crosslink audit run YYYY-MM-DD