Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Inbox: let users customize when agents use the Inbox and how they write to it

Aperta
  • Qualcosa non va?
#2,194 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
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
developer-experience

Direzione di ricerca

Start by locating the configuration and prompt handling for the Inbox reminder, the plannotator inbox --notes command, and the send_message tool description; the issue does not name files or tests. Read how other prompts sections support per-runtime overrides, then trace how Inbox notes and tool descriptions are assembled. Done means at least one requested customization works without conflicting with the built-in Inbox guidance.

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

Descrizione

enhancement

What we need

We want to decide ourselves when an agent should use the Inbox and how it should write to it, and have that guidance come from Plannotator's own Inbox surfaces instead of fighting them.

Our setup: several agent sessions run at once. Many are started by a coordinating session, so they have an "upstream" session to report to. Our rules are:

  • An agent first decides what it can within its authorization; what it can't decide goes to its upstream session, not to the person.
  • Only a session with no reachable upstream (one the person started directly, or one whose upstream is gone) sends to the Inbox.
  • Reviewer sessions never use the Inbox.
  • Messages follow one format: the first line says why the person is needed, every question carries a recommendation, long material goes in attachments, diagrams/screenshots when a flow or UI is involved, one thread per work item.

What we found (0.28.30)

Surface What can be changed today
The one-line Inbox reminder at session start Fixed text; only on/off via inboxReminder
prompts config Covers plan / review / annotate feedback, not the Inbox
plannotator inbox --notes Writes fixed v1 text; a block the person edited is not overwritten — but on hosts whose instructions file is regenerated by a sync tool (e.g. a generated ~/.pi/agent/AGENTS.md), the block is wiped on the next regeneration
send_message tool description Fixed

So today we turn the reminder off and put our own guidance in our global instructions. It works, but the built-in text ("send when the person isn't here") and ours can disagree, and the guidance is not where the model looks at the moment it sends.

Request

  1. Customizable Inbox reminder text, e.g. prompts.inbox.reminder (with the same per-runtime overrides the other prompts sections have), replacing the fixed line instead of only switching it off.
  2. Custom note content for --notes: let the note body come from a user file (or config), and/or write it to a separate file the host loads, so generated instruction files don't erase it.
  3. Optional extra guidance on send_message: a config string appended to the tool description, since that is what the model reads right when it sends.

Any one of these would let us keep a single source of truth for "when to use the Inbox and how to write to it". Happy to test a build.

Lingua principale
TypeScript
Stelle
8.7k
Fork
649
Merge medio
4h 16m
PR unite (30g)
468

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.