Channels and the agent inbox

When you share something from your phone, it lands in your agent's inbox. This page explains what the inbox is, how an agent works through it, and the two ways an agent picks up new items — so you can decide which one you want.

The inbox

Every agent (every coding session you've wired up) has its own inbox. Things flow both directions:

• Phone → agent — screenshots, notes, links, your live iPhone screen, and events from connected services (Coolify, CI).
• Agent → phone — questions, results, and previews the agent sends back. These arrive as push notifications on your phone, even when the PWA is closed.

You send to an agent from the phone app at share.agentics.dk (or the Windows Share panel) by picking which agent to share to. The agent reads what you sent and acts on it.

New vs. handled

Items start out new. Once the agent has acted on something, it marks it handled — so both you and the agent can tell what's already been dealt with.

Two things are deliberate here:

• Reading an item doesn't mark it handled. The agent only marks it when it's actually done with it, so nothing quietly disappears before it's acted on.
• Handled doesn't mean deleted. Handled items stay in the inbox and can be revisited later — they just drop out of the "new" view.

By default an agent looks at new items only, so it isn't re-reading things it already took care of.

Two ways an agent picks up your shares

This is the choice that matters. An agent can either check its inbox when you point it there, or — with Claude Code — have shares pushed into the live session the moment you send them.

1. Check on demand (works everywhere)

The agent looks at its inbox when you ask it to — e.g. "did anything come in from my phone?" or "look at the screenshot I just shared." It won't be interrupted mid-task by an incoming share; you bring it in when you're ready.

This works in any MCP-capable agent (Claude Code, Cline, Cursor) and needs no special flags. It's what you get from agent-share init (your personal inbox) or agent-share install.

2. Channels — pushed live into Claude Code (research preview)

With channels, the moment you share from your phone it pops straight into the running Claude Code session — you don't have to ask. Claude sees it mid-conversation and can react right away.

Research preview. Channels is a Claude Code–specific feature. It needs Claude Code v2.1.80 or newer, an Anthropic login (not Bedrock, Vertex, or Foundry), and a launch flag (below). The feature is still evolving, so treat it as preview rather than something to depend on in a critical workflow.

Which should I use?

• Just getting started, or using Cline/Cursor? Use check-on-demand. It's the stable path and there's nothing extra to enable.
• Want your agent to react the instant you share, hands-free, in Claude Code? Turn on channels.

Turn on channels

1. Wire your repo for channel mode. Either enroll a named inbox (recommended, so you can tell agents apart when sharing) or just switch an existing repo to channel mode:

   # Enroll + name an inbox and wire channel mode to it (prints the launch line)
   agent-share register "my session"
   
   # Or switch an already-wired repo to channel mode
   agent-share install channel
   

   Copy

2. Launch Claude Code against the channel:

   claude --dangerously-load-development-channels server:agent-share --dangerously-skip-permissions
   

   Copy

3. Share from your phone. While that session runs, anything you send from share.agentics.dk shows up in the conversation on its own — no prompt needed.

A register-wired ./.mcp.json contains a token for that inbox. Don't commit it. (The init / install files carry no secret and are safe to commit.)

See also

• Use it with Claude Code — full setup walk-through.
• CLI reference — every command and flag.
• MCP tools reference — the tools an agent calls, and how delivery works under the hood.