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

A direct sub-agent chat gives no sign that the main agent is not in it, and the handoff count it already serves is never shown

Aperta
  • Qualcosa non va?
#460 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
frontend

Direzione di ricerca

Start in the ui-web instance surface, especially the instance composer, and inspect how the subagents.instances response is consumed. Use pending_handoff_count to show the non-zero count and add the proposed explanation of direct-chat context and handoff timing. Done means both messages appear correctly without backend changes.

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

Descrizione

Problem

Chatting with a sub-agent instance produces no visible reaction from the main agent, and the page says nothing about why. The behaviour is deliberate and documented in the code -- "Nothing here touches the session transcript. A direct chat exists to keep these exchanges out of the main agent's context" (raven/agent/subagent/manager.py:984) -- but nothing on screen tells the reader that, so it reads as the main agent having missed the message.

There is a handoff: DirectChatHandoff appends an entry as each direct turn lands, and the rendered block is prepended to the user's next message to the main agent (raven/agent/subagent/direct_chat.py). So the main agent does learn, after the fact, on the next thing the user says to it. That is a reasonable design; it is just invisible.

The count is already served and already unused. subagents.instances returns pending_handoff_count (raven/rpc/methods/instances.py:318, modelled at raven/rpc/models.py:2183), and no caller in ui-web/src reads it.

Proposal

Two small things, either independently useful:

  1. Say once, on the instance surface, that this exchange stays out of the main agent's context and reaches it as a summary on the next message to it. One line, where the instance composer is.
  2. Show pending_handoff_count when it is non-zero -- "N exchanges will be reported to the main agent" or similar. The number exists; nothing renders it.

Alternatives considered

  • Mirror direct turns into the session transcript: this is exactly what the design refuses, and for a good reason (context cost, and the main agent being steered by details it was deliberately not given). Not proposed.
  • Show nothing and let people learn the model: what happens today, and it produced this report.

Area

ui-web (the instance surface); no backend change needed for either item.

Additional context

The handoff already handles two edges worth knowing about, which is part of why surfacing it is cheap and honest: an instance created but never spoken to is an entry in its own right ("the case worth reporting is precisely the one where nothing has been said to it yet"), and a turn still answering is reported through live_direct_turns rather than being invisible until it lands -- a fix whose comment records that "a five-minute direct chat was reported to the main agent as an instance with no turns yet (2026-09-08)".

Lingua principale
Python
Stelle
4.1k
Fork
94
Merge medio
9h 54m
PR unite (30g)
370

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 EverMind-AI/Raven

Tutte le issue di EverMind-AI/Raven

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.