The inbox is a queue of work waiting for whoever handles it: a person on your team or an agent. Items arrive as screenshots someone annotated on their screen, as tasks an agent filed, or as posts on your feedback boards. Each one carries a note, a status and, optionally, an image with numbered pins.The inbox is free on every plan. In the dashboard, Inbox lists items by view (open, waiting for a reply, done, dismissed) and destination, and each item page shows the note, the screenshot with its pins and the board conversation.
kind is bug, task, idea or question (default task). Pin positions are fractions of the image. The image is a PNG, JPEG or WebP data URL, up to 3.2 MB decoded. The answer is 201 with the item, or 200 with the earlier one when the idempotency key was already used.
Destinations and routing
A destination is where work goes: a product, a repository, a team. Create one with POST /api/v1/inbox-destinations, { slug, name, description, hints }, where hints are lists of apps, domains and keywords. GET /api/v1/inbox-destinations lists them. In the dashboard, they live under Settings › Inbox routing.
An item that names a destination goes there. Otherwise the hints score it: a domain or host/path prefix matching the source URL counts 3, an app in the app or window title 2, each keyword in the note, pins or title 1. The best destination wins with at least 2 and a clear lead. Anything else stays unsorted (destination: null) for the first agent to route.
Work the queue
GET /api/v1/inbox?destination=acme&status=new,planned&limit=50 lists items, newest first, open statuses by default. Use destination=unsorted for unrouted items, needsReply=true for board posts whose last word is a user's, and paid=true for paying reporters only.
GET /api/v1/inbox/:id adds the screenshot as imageUrl, signed for an hour, and the board thread.
POST /api/v1/inbox/:id changes status, destination, claimedBy, planRef or resolution, and for board posts public, title and needsReply.
GET|POST /api/v1/inbox/:id/comments reads a board post's thread or answers it publicly.
Statuses are new, planned, in_progress, done and dismissed. On a board they are the roadmap's columns.
Plan with items, not just acknowledge them
Set planned with a planRef naming the milestone or thread the work went into, in_progress when it starts, done with a one-line resolution, or dismissed with the reason. Whoever looks next can see what happened without asking.
From an agent
The MCP server has list_inbox, get_inbox_item (which returns the screenshot as an image with its pins), update_inbox_item, create_inbox_item, reply_to_inbox_item, list_inbox_destinations and set_inbox_destination.