Background agent sessions should be fully exportable and inspectable
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
### Describe the feature or problem you'd like to solve
background agents launched via the task tool don't persist their tool calls or outputs. /share captures reasoning blocks but not the actual grep, edit, and shell commands. /tasks empties once agents complete. session store database has no record of the subtask. you can follow the agent's thinking but can't verify its actions.
### Proposed solution
1. persist completed background agent sessions as inspectable child sessions linked to the parent
2. /tasks should list completed agents (not just running ones) with their session ids
3. /share should include subagent tool calls and outputs (inline or as linked sections) - currently only reasoning blocks are captured
4. /resume should allow browsing a completed agent's full conversation read-only
5. alternatively, a /share --include-subtasks flag for full recursive export
### Example prompts or workflows
1. launch a background agent that modifies multiple files, creates a branch, and opens a PR. after it completes, try to inspect what it actually did step by step - you can't
2. /share after a session with background agents - the export shows the agent's reasoning but not its tool invocations or their outputs
3. /tasks after a background agent finishes - empty list, no way to get back to it
### Additional context
_No response_
Guía de contribución
Línea de trabajo
Empieza por rastrear los puntos de entrada /tasks, /share y /resume, así como el comportamiento de la base de datos del almacén de sesiones para los agentes en segundo plano completados. Define cómo se conservan, enumeran, exportan y consultan en modo de solo lectura las sesiones secundarias y sus llamadas a herramientas y salidas; se considera terminado cuando los flujos de trabajo del issue pueden inspeccionar los agentes completados y sus acciones.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- shell
- Área
- cli, database
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100