docs: clarify the Agent picker and its effect on PR authorship - #436
docs: clarify the Agent picker and its effect on PR authorship#436rachaelrenk wants to merge 2 commits into
Conversation
The New schedule form's Agent setting determines which identity a scheduled agent runs as, which in turn determines who GitHub records as the author of any PR the agent opens. Quick run (the default) runs as the schedule's creator, so PRs are authored by that person rather than by the Oz by Warp GitHub App. That consequence was undocumented, and the quickstart also mislabeled the Skills field as Agent, making the real setting easy to miss. - Correct the quickstart steps: Agent and Skills are separate fields - Add "Who the schedule runs as" explaining both options and when to pick a cloud agent - Note in the CLI reference that neither schedule create nor update can set Agent, so CLI-created schedules run as their creator - Spell out the authorship consequence on the Agent picker bullet Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR clarifies how the Agent picker affects scheduled run identity and GitHub PR authorship, and it corrects the quickstart’s separation of Agent and Skills fields. I found no correctness, security, link, or spec-alignment issues that should block the docs change.
Concerns
- Non-blocking: the new copy continues adding variable-backed Oz product names and URLs (
Oz CLI,Oz web app, andoz.warp.dev) as literals in existing pages. The PR description calls this out as a consistency choice; consider a follow-up to importVARSin these pages so future rename updates propagate.
Verdict
Found: 0 critical, 0 important, 1 suggestions
Approve with nits
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
1 participant
Summary
The Agent setting on a schedule determines which identity the run executes as, which in turn determines who GitHub records as the author of any PR the agent opens. Quick run — the default — runs as the person who created the schedule, so PRs are authored by that person rather than by the Oz by Warp GitHub App.
That consequence wasn't documented anywhere. The quickstart also mislabeled the Skills field as Agent, which made the real setting easy to miss entirely.
This surfaced when six scheduled docs agents were found opening PRs under an individual's GitHub account. The underlying cause was configuration (unpinned schedules), but the docs gap is what let it go unnoticed.
Changes
platform/triggers/scheduled-agents-quickstart.mdxplatform/triggers/scheduled-agents.mdxoz schedule createhas no flag for Agent, so CLI-created schedules run as their creator.oz schedule updatecan't change it either.platform/agents.mdxVerification
npm run buildpasses.who-the-schedule-runs-asanchor is present in the built HTML, and both inbound cross-page links resolve to it.style_lint.py --changedreports 34 issues across the three files, against 24 onmainfor the same files. See below.Notes for review
UNRECOGNIZED-TERMfor bolded UI/product names not in the glossary: Skills (a real field name) and Oz by Warp ×3 (bolded the same way inteam-access-billing-and-identity.mdx). The other six areHARDCODED-VARfor "Oz web app" / "oz.warp.dev" in new sentences.WEB_APPandWEB_APP_URLexist invars.ts, but none of these three pages importVARS— all 24 pre-existing issues are hardcoded names. I kept the new text consistent rather than introduce mixed usage within a file. Converting these pages toVARSlooks like a worthwhile separate cleanup.This PR was generated with Oz.