The five texts to try first
- how's it going
Goes to the current agent in the current session. It answers from what it is doing and from shared memory, so it knows what was decided this morning even if you decided it with the other agent.
- send me the diff as a file
The agent writes the diff to its outbox and it arrives as a real attachment. Big code blocks in any reply also come as files instead of a wall of text.
- codex, review what claude just did
Addressing an agent by name switches to it. Codex sees the recent Claude turns from this thread and the repo's shared memory, so "what claude just did" means something.
- every morning at 7, audit deps and open a PR if there's a CVE
Creates a schedule. It runs at 7:00 every day on your Mac, with that day's memory, and texts you the result.
- pull the stripe invoice for last month and send me the pdf
Uses browser hands: a real Chrome on your Mac with your logins. The PDF lands in the thread.
What you will see
- Progress, not spam. Short runs just answer. Longer runs post one status message that updates in place with the steps ("shell: npm test", "edit: src/app.ts").
- A tap when it matters. Anything that touches money, prod, messaging, or deletes arrives as a message with the command or diff and three buttons: Approve, Deny, Always. Nothing waits for you otherwise.
- Files back. Anything the agent drops in its outbox arrives when it finishes.
- A queue, not a collision. Text again while it is working and the new message waits its turn.
/stopcancels the run and anything queued.
Close the lid
The background service keeps running with no terminal open. While an agent is working it keeps the Mac awake. If the Mac sleeps anyway, schedules that were due run once when it wakes, marked as catch-up. If your phone loses signal, nothing on the Mac stops; the thread catches up when you are back.