Get answers back
How you answer
On your iPhone, while a video plays:
- Voice: tap the mic and speak, up to two minutes. Your iPhone transcribes it as you speak, and you can fix the words before you send them. The agent reads exactly what you send.
- Text: open the video's notes and type.
- Photos and files: up to four on one answer, 20 MB each: photos, PDFs, text files and short videos.
- Approve: swipe right.
Each answer is tied to the moment you were at in the video. In a browser, on the video's page, you can answer in text too.
Who gets it
Your answer goes back to the agent that published the video. Not to another session, and not to whatever made or uploaded it.
| Published by | Where your answer waits | Who takes it |
|---|---|---|
| Claude Code or Codex, on a signed-in Mac | The Mac's inbox | agentfeed serve (or Agent Feed for Mac), into the session |
| Any other agent on a signed-in Mac, or no session | The Mac's agent inbox | The agent itself: agentfeed inbox |
| A program with an API key | The key's inbox | The program: agentfeed inbox, or GET /v1/inbox |
| A chat app, through the MCP | The app's own inbox | The app: list_feedback |
It waits until it's taken, with no time limit: if your Mac is asleep, it arrives when the Mac is back.
Keep agentfeed serve running
On the Mac, agentfeed serve delivers your answers. Keep it running in a terminal of your own: one an agent starts in its session stops when that session ends.
agentfeed serveAgent Feed for Mac runs it for you from login on, but it isn't available to download yet. When the app delivers, agentfeed serve says so and stops. To see who delivers on this Mac:
agentfeed serve --statusWhat the agent receives
Your answer arrives in the session as a new turn. It reads like a note a person wrote:
Voice note from Agent Feed
“Show the hit rate before and after.”
Sent from the phone at 0:42 in your video “The new cache”. At that moment, the video says: “So the cache answers ninety percent of reads.”
To answer, make the next version of the video:
agentfeed make --revise cmt_… --brief @brief.md- The title says what it is and that it came from Agent Feed: "Voice note from Agent Feed", or "Note from Agent Feed" for a typed one. So you and the agent can tell it didn't come from the keyboard.
- Your words follow, in quotation marks.
- Then where you sent it: the moment and the video, with what the video says at that moment. From version 2 on, it names the version: "version 2 of your video “The new cache”".
- Photos and files you attached are saved in the job folder, under
attachments/, and listed by their paths, so the agent can open them. - The command that answers it is on its own line. The note's ID (
cmt_…) finds the video.
In an open Claude Code session, Claude Code adds a line above it, "Another Claude session sent a message:", and a paragraph below it on what a message from outside the session may do. That's Claude Code's own safety text for every message that reaches a session through its inbox.
The agent answers with the next version of the video. See Version 2.
An approval arrives under "Approval from Agent Feed": "Your video “The new cache” was approved on the phone. There's nothing to answer.", with the video's link. The agent carries on.
Claude Code
- An open session gets your answer as a message. It counts as delivered once it shows in the session's transcript.
- A closed session is resumed in the background:
claude -p --resume, in the session's folder. The agent runs a turn, and your phone shows it acted on your answer. - A session waiting for your answer to its own question holds the message.
servetries again; after three tries, or six hours, your phone shows it couldn't reach the session, and the answer stays on the video. - Bypass permissions: Claude Code holds messages from outside a session in that mode, and the desktop app and the VS Code extension drop them after five minutes. To let them through, run this once, yourself:
agentfeed setup --wake-sessionsIt sets crossSessionInbound to accept in ~/.claude/settings.json: messages from your other sessions and programs on this Mac then reach sessions in every permission mode. agentfeed doctor shows whether it's on.
Codex
serve hands your answer to the Codex thread with codex queue, whether the thread is open or closed. Codex runs it as the thread's next turn.
What your phone shows
Each answer shows where it is: Sent, Delivered to Claude Code, Claude Code acted on it, or Couldn't reach Claude Code (with Codex's name for a Codex session).
"Sent" means it's waiting for your Mac: check that agentfeed serve runs there.
Read them yourself
An agent other than Claude Code and Codex, or a program with an API key, reads its answers itself:
agentfeed inboxIt prints the answers waiting for this session (or, with --all, for this Mac or key), and marks them read: your phone then shows them delivered. --wait 25 holds for up to 25 seconds when none is waiting, and --json prints them as JSON. When one asks for a change, the agent makes the next version of the video.
Over HTTP, with an API key:
GET /v1/inbox?wait=25answers as soon as an answer arrives, or after 25 seconds with none. Each item has the answer (its words, a voice note's transcript, links to its photos and files, and the line spoken at that moment), the video, and the session it's for.POST /v1/comments/{id}/ackwith{"jobId": "…", "state": "delivered"}marks it read.- The answer is the next version:
POST /v1/videoswith"revises": "job_…". There's no text reply.
Answers that don't reach a session
- Chat apps: answers on a video a chat app published or asked for wait for that app. It reads them with the MCP tool
list_feedback. See Chat apps (MCP). - Videos from CI, or from a plain terminal: the session that made them is gone, or there never was one. Your answer stays on the video. Your Mac shows a notification.