session-flow: remove a delivered absence's away state so idle hook cost returns to the cheap path

Abierto
#17,389 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@kyle-sexton ya está trabajando en esto.

Desde el 19/11/2026.

  • #17396 de @kyle-sexton — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python, shell

Línea de trabajo

Start with the session-flow away hooks and the deliver and end paths that write the away/<session> state under the plugin data dir. Check whether the Python startup cost only appears once that directory exists. Done means a delivered absence leaves no away/<session> directory (or one within the stated retention), the report stays readable as long as that retention allows, tests cover the cleanup, and the idle hook timing is recorded. Linked PR #17396 is already open, so coordinate there first.

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

Descripción

Problem

session-flow's always-registered away hooks cost about 0.02 s per prompt and turn end when no away state exists (Python never starts). Once any away/ directory exists under the plugin data dir, the cost is about 0.09 s. A finished absence's state stays in place, so every later session pays the higher cost.

Done looks like

  • deliver (or end) removes a finished absence's state, or keeps it for a stated bounded retention.
  • After a delivered absence, no away/<session> directory remains (or only within the retention bound).
  • Measured idle hook cost in a session with no active absence is back to about 0.02 s, with the measurement recorded in the PR.
  • Tests cover the cleanup, and the report remains readable after delivery for as long as the retention says.

Refs: #17337

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
1 h 47 min
PR fusionados (30 d)
942

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 melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.