mcpField
P
plannotator-inbox

plannotator-inbox

github.com/backnotpropAgent workflows11.8k110 installsUpdated today
Repository

About plannotator-inbox

plannotator-inbox is a usage guide for Agents working with Plannotator Inbox. It covers asynchronous messages, decision questions, files, and replies, keeping pending decisions in separate threads so work can continue.

Key features

  1. 01Send messages and files asynchronously
  2. 02Collect decisions with question blocks
  3. 03Keep one thread per work stream
  4. 04Check whether replies arrive automatically
  5. 05Send through the MCP server

Use cases

  1. 01Request a decision to be made later
  2. 02Report completion of lengthy work
  3. 03Share summaries with images and attachments

MCP support

The guide describes sending messages through the plannotator_inbox tool or the Plannotator Inbox MCP server.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/backnotprop/plannotator --skill plannotator-inbox

After installing, type/plannotator-inboxin Claude Code to confirm it loaded.

Details

From the project README

Plannotator Inbox

Inbox address

!plannotator inbox --open

Using the Inbox

The Plannotator Inbox is one window on this computer where you leave the person messages, :::question blocks they answer with a click, and files. They answer when they can. Nothing blocks: you send, then keep working or end your turn.

  • Use it for a decision only they can make (a :::question block; go on with other work), finished long work (a short summary with its pictures inline, files in attachments), or when they ask.
  • One thread per work stream, unless the person says otherwise.
  • Send with a plannotator_inbox tool when you have one (it can be listed with a prefix and may need loading through tool search first): action send_message, with a markdown body. Otherwise call send_message on the Inbox's MCP server, plannotator inbox mcp.
  • send_message's result says whether the person's reply arrives in this session by itself. When it does, do not wait or poll for it: end your turn or go on with other work. When it does not, go on with your work and read the thread later with read_thread.
  • A decision in the Inbox stays there: when the person writes in the chat, say what waits and link its thread, but never also ask it in the chat with a blocking question tool (AskUserQuestion or similar). Ask in the chat only about something new they raised there that needs no pictures or files, or when they ask.
  • Be proactive about Inbox updates and about replying to the person through the Inbox when you think they would want you to. Don't withhold important updates or decisions, and don't batch updates to send later: proactivity is better than procrastination.
  • Never run plannotator inbox just to send: send_message starts a stopped Inbox itself, and bare plannotator inbox opens the window for the person.
  • Before your first send, run plannotator inbox --help and read it: every field, the full question syntax, and how to connect the MCP server.
  • The plannotator skill, where you have it, has more.

Your task

The output above is the Plannotator Inbox's address; it opened in the person's browser unless the output says why not. Tell them the address in one sentence, with that reason when there is one. If the output is an error, tell them what it says; Unknown inbox option: --open means their Plannotator is older than this command (update with plannotator update, or run plannotator inbox in a terminal).

This command starts no new work and resumes none: do anything else the person asked in the same message, otherwise stop there. For the rest of this session, use the Inbox as above: for a decision the person is not here to make, and to hand over long work you finished.

Comments

Markdown supported