Dispatch the right workflow
Use exploration for read-only analysis, task for bounded implementation, or project for broader build-and-repair work.
Open-source skill for Codex and Claude Code
Delegate coding work. Verify before you trust it.
agy-worker lets Codex and Claude Code hand bounded repository work to Antigravity CLI, then independently review the resulting Git scope and run driver-owned checks before accepting the candidate.
- Bounded worktrees
- Git-derived scope
- Driver-owned checks
- No autonomous publishing
A bounded workflow
One delegation loop, three clear responsibilities.
Review the actual candidate
The driver inspects the Git diff and derives scope from repository state instead of trusting a worker summary.
Verify and report honestly
Driver-owned checks determine whether delivery is verified, partially verified, or blocked—with the candidate preserved for review.
Choose by intent
Useful from first inspection to project-scale work.
Explore
Understand unfamiliar repositories
Request broad, read-only exploration while the driver spot-checks material claims and labels coverage limits.
Task
Implement bounded changes
Delegate a feature, refactor, or test change inside a disposable worktree, then verify the exact diff.
Project
Run broader quality loops
Allow repo-wide candidate changes, build and test them, and request bounded same-conversation repair when checks fail.
Proof
Inspect the trust boundary offline
Use the synthetic proof demo to see a valid candidate pass and an out-of-scope candidate get rejected.
Evidence before acceptance
Four signals keep provider output in its proper place.
Worker output is input
A worker envelope is never treated as final acceptance evidence.
Git is the scope authority
The actual repository diff—not a narrated file list—defines what changed.
Checks belong to the driver
The driver runs the relevant commands itself and reports the assurance level reached.
Publication stays human-owned
Commit, push, pull request, release, and other external writes remain separate approval gates.
Transmission boundary
Write scope and provider read scope are different controls.
Whole-worktree approval
No initial launch path has an implicit provider-read mode. --approve-whole-worktree binds current content, file kinds, permissions, symlink targets, and isolation and acknowledges that the disposable worktree is potentially readable and transmissible.
Selected-content approval
The recommended bounded-job path is --provider-scope plus the full launch_approval_sha256. It binds reviewed read/write entries and stages only the selected content in a private, Gitless provider directory. The digest also binds the task, model/effort, mode, budgets, repair, self-verification, and provider environment names.
Authority remains separate
Session mode uses the existing AGY session; explicit native mode requires supported macOS containment and fails closed when the driver host's sandbox forbids nested Seatbelt (observed with Codex workspace-write). Scope approval alone grants no provider execution, Git, acceptance, or publication authority.
Get started
Install from the repository source of truth.
Use the GitHub repository as the source of truth. Install the reviewed marketplace source, follow the installation guide, and review the trust and privacy boundaries before your first provider-backed dispatch.
# Codex
codex plugin marketplace add cagdasyurekli/agy-worker
codex plugin add agy-worker@agy-worker
# Claude Code
claude plugin marketplace add cagdasyurekli/agy-worker
claude plugin install agy-worker@agy-workerDocumentation
Go deeper without losing the boundary.
Verification tutorial
Understand why worker output is not acceptance evidence.
Usage guide
Choose workflows and understand their delivery semantics.
Privacy guide
Review provider transmission and local boundary considerations.
Source and tests
Inspect the implementation, checks, release notes, and open issues.