[Feature Request] Claude Code mod: turn the Inbox off for one session

Aperta
  • Qualcosa non va?
#2,898 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
developer-experience

Direzione di ricerca

Read the Claude Code mod code that registers /plannotator-inbox, adds the per-message reminder, and handles Inbox replies and plannotator_inbox responses. First trace where session startup loads the Inbox settings and how resumed sessions are identified. Define the command and persistence behavior with maintainers; done when toggling off and on controls all three behaviors for one session, with the agreed behavior on resume.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

Sometimes I want one Claude Code session to keep its decisions in the chat (a quick fix, or pairing live) while my other sessions keep using the Inbox. Today the switches are global: PLANNOTATOR_INBOX_TOOL, inboxTool / inboxReminder in config.json, or Settings → Agents. All of them are read when a session starts.

My workaround is a pair of slash commands (below) that tell the agent to ignore the Inbox for the rest of the session. That's only a prompt: the mod still adds the "Plannotator Inbox is on" reminder to every message, and replies still arrive as turns, so the agent is told one thing by the hook and the opposite by me.

Proposal

A mod command, /plannotator-inbox off and /plannotator-inbox on, that for this session only:

  • stops (or restarts) the per-message reminder;
  • stops waking the session with replies (they stay in the Inbox to read later);
  • makes plannotator_inbox answer that the Inbox is off for this session, since the tool can't be removed once registered.

Why

It matches how people work: the Inbox for long-running work, the chat for a session you're sitting in. And it replaces a prompt-level override with a real switch the mod honors.

Happy to send a PR

I have a good idea of how to build this and I'm happy to send a PR, but I'd like your take on the direction first:

  • The command: one /plannotator-inbox on|off, or two commands?
  • What "off" covers: the reminder, the reply wake, and the tool's answers, or only some of them?
  • How long it lasts: only this process, or kept for the session, so a claude --continue or resume stays off?

Related

  • #2194 asks for control over when agents use the Inbox and how they write to it. This one is narrower: an on/off switch for a single session.

My workaround today

Two slash commands that only change what the agent is told:

  • /plannotator-inbox-disable asks the agent to leave the Inbox alone for the rest of the session:
Stop using the Plannotator Inbox for the rest of this session, until the person runs `/plannotator-inbox-enable`:

1. Send no Inbox messages and touch no Board cards.
2. Ignore the "Plannotator Inbox is on" reminder. The plugin's hook keeps adding it to every message, and this command overrides it.
3. Ask decisions in the chat. A blocking question tool is fine again.
4. If a question you sent to the Inbox is still open, name it once in the chat with its thread link, so the person can answer it in either place.
  • /plannotator-inbox-enable undoes that: it loads the live Inbox reminder into the session (the text GET /api/inbox/settings returns under prompts.reminder) and asks the agent to follow it again.

Both commands only change what the agent is told. The mod itself still adds the reminder to every message and still wakes the session with replies, which is what a real per-session switch would stop.

Lingua principale
TypeScript
Stelle
8.7k
Fork
649
Merge medio
11h 7m
PR unite (30g)
862

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di backnotprop/plannotator

Tutte le issue di backnotprop/plannotator

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.