One-stop situational awareness: who is online, what each agent is running, which paths are locked, open tasks, and unread notes addressed to you. Call this before starting work or editing files so you do not collide with the other agent.

Hand a task to Antigravity. Starts agy headlessly as a detached background job and returns immediately with a task_id -- it does NOT block, so keep working on your own part meanwhile.

Write prompt as a complete, self-contained brief: Antigravity cannot see your conversation or your context. State the goal, the stack and conventions actually in use, the files it owns, what it must NOT touch, and the API/prop contract it must code against.

claim locks paths for Antigravity up front so you stay off them. auto_approve passes --dangerously-skip-permissions so it can edit unattended.

Check a delegated Antigravity task: running / done / failed, plus its final response and conversation_id once finished.

Block until a delegated Antigravity task finishes, or until timeout. Prefer ag_task_status and doing your own work in between -- only wait when you genuinely cannot proceed without Antigravity's result.

Send a follow-up into the SAME Antigravity conversation as a finished task, so it keeps its context (e.g. 'now make the header responsive'). Use this rather than a fresh ag_delegate whenever the request builds on work it just did.

Stop a running delegated Antigravity task and release any paths it held.

Put an item on the shared board WITHOUT executing it -- a plan entry, a hand-off, or an announcement that you are about to do something, so the other agent can see it. Use ag_delegate instead when you want Antigravity to run it now.

Update a board item's status or owner, or attach a progress note. Keep your own items current here so the other agent is not guessing.

List board items and delegated tasks. Filter by owner to see just one lane.

Lock files or directories you are about to edit, so the other agent stays off them. A directory lock covers everything under it. Returns granted vs conflicts -- if a path is held by the other agent, do NOT edit it; pick different work or send a note asking for a hand-off.

Release path locks you hold. Pass all_mine=true to drop every lock you own -- do this when you finish a chunk of work so the other agent is not blocked.

Ask whether specific paths are free before touching them. Cheaper than claiming when you only want to read the situation.

Leave a message for the other agent -- an interface contract, a hand-off, a heads-up that you changed something they depend on. Make it self-contained and concrete: 'POST /api/orders is live, returns {id, status}. Wire the form to it.'

Read messages the other agent left for you.

Announce what you are doing right now, so the other agent's coop_status shows it. Call when you start and finish a chunk of work.

Recent timeline of what both agents have done -- delegations, claims, releases, notes, status changes.

Clear the whole board -- tasks, locks, notes, events, presence. Destructive; requires confirm=true. Use when starting a fresh project.