Coding agents
The main use case, coding agents in T3 Code telling you when they are done or need you.
Most notifier messages will come from coding agents (Claude, Codex) running in T3 Code. An agent publishes when a task is done, when it is blocked on a decision, or when something fails, so you can step away from the screen and come back only when needed.
How agents connect
Decided The primary path is the notifier MCP server. You add it once per agent and sign in through the browser:
claude mcp add --transport http pocket-notifier https://notifier.bartuozel.com/api/mcp
codex mcp add pocket-notifier --url https://notifier.bartuozel.com/api/mcp && codex mcp login pocket-notifierThe agent then calls list_projects, list_features and send_notification. The pocket-notifier skill tells it when and how.
Decided agent-notify over the REST API stays as the fallback for scripts and agents without MCP. See Fallback: agent-notify over REST.
Projects and features
Decided Agents and the app use two words:
- Project: the product or repository, for example
rezme. Projects hold members, roles and retention. - Feature: the workstream inside a project, for example "Improving performance". In the app each feature is a chat thread (a conversation).
Agents check that the project and feature exist and create them if not. A notification without a project goes to your private General project. See Projects and features.
What it looks like
┌──────────────────────────────────────────────┐
│ [NO]◖C notifier · Claude 2m │
│ Which database for the cache layer? │
│ │
│ [RZ]◖X rezme · Codex 9m │
│ Build failed: 3 tests in auth.spec │
└──────────────────────────────────────────────┘
NO / RZ project avatar (generated, or the project's icon)
C / X agent badge (Claude, Codex)Decided Each feature is a conversation: its avatar is the large icon, and its messages stack together. The agent is the sender: a small badge on the avatar and its name (the OAuth client name, for example "Claude Code") next to the title. See Conversations and avatars.
Decided Tapping opens the url the agent sent, for example its T3 Code thread. Agents can ask a question with ask and you can answer in the app, but agents cannot read replies through MCP yet.
Project layout
Decided With MCP, each repository or product is a project, and each feature a conversation in it. Muting a project silences its agents.
With the REST fallback, agents publish to one project, agents, and the repository name in conversation.id does the grouping.
The agent skill
skills/pocket-notifier/SKILL.md at the repository root is an agent skill: how to connect, when to notify, how to name project and feature, title and body style, priorities, and to never send secrets. The MCP server sends a short version of it as its instructions.
Fallback: agent-notify over REST
Message kinds
The kinds agent-notify uses today map onto notifier fields like this:
| Kind | When | Priority | Tag |
|---|---|---|---|
done | Task finished and verified | 3 | done |
ask | Blocked on your decision | 4 | ask |
fail | Failure the agent cannot fix | 4 | fail |
urgent | Production or data at risk | 5 | urgent |
build-ok | Long build or CI run passed | 3 | build |
build-fail | Long build or CI run failed | 4 | build, fail |
The request an agent sends
curl -X POST "$NOTIFIER_URL/v1/projects/agents/messages" \
-H "Authorization: Bearer $NOTIFIER_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "Needs your decision",
"body": "Which database for the cache layer?",
"priority": 4,
"tags": ["ask"],
"clickUrl": "<T3 Code thread URL>",
"conversation": { "id": "notifier" },
"sender": { "id": "claude", "name": "Claude" }
}'conversation.idis the repository name, for example the repository folder. AddiconUrl(HTTPS) to use the repository's real logo instead of the generated avatar.senderis the agent.agent-notifyalready detects Claude or Codex, so it sets this automatically.- Title. The repository now shows in the conversation header, so the title no longer needs the
<repo>:prefix.
Moving agent-notify over
The script keeps its interface (agent-notify <kind> <title> <body> [--url] [--action] [--image]), its length checks and its 10-minute duplicate check. Only the request changes:
- Read
NOTIFIER_URL(the API base,https://notifier.bartuozel.com/api) andNOTIFIER_TOKENinstead ofAGENT_NTFY_PROJECT. The token is a notifier access token scoped to theagentsproject. - Send the JSON above instead of ntfy headers.
--imagebecomes an attachment upload followed by the publish.
Open questions
- Getting the thread URL. The agent needs its own T3 Code thread URL to pass as
clickUrl. Whether T3 Code provides it to agents (for example in an environment variable) still needs checking. Until then--urlstays a manual argument. Open - Project icons. Where a project's real icon comes from, for example the repository owner's GitHub avatar or a favicon. The generated avatar works until then. Open