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

Abierto
  • ¿Algo no está bien?
#2,898 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
developer-experience

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
8.7k
Forks
649
Merge medio
11 h 7 min
PR fusionados (30 d)
862

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de backnotprop/plannotator

Todos los issues de backnotprop/plannotator

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.