session-flow: continue-in-background dirty-tree gate ignores worktree.bgIsolation
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 76/100
Línea de trabajo
Lee plugins/session-flow/skills/continue-in-background/SKILL.md, especialmente el paso 1, «Dirty-tree gate», y compara cómo el plugin source-control lee la configuración en plugins/source-control/hooks/worktree-create-gate.sh. Actualiza la barrera y el informe de inicio para tener en cuenta worktree.bgIsolation cuando se establece en none; verifica que el motivo del rechazo y la advertencia coincidan con el comportamiento esperado del issue.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
/session-flow:continue-in-background's dirty-tree gate assumes a background session always moves into an isolated git worktree before editing, unless the current session is already in a linked worktree. The worktree.bgIsolation setting can turn that isolation off, and then the background session edits the working copy directly. The gate does not read the setting, so its reasoning and outcome are wrong in that configuration.
Affected area / component
plugins/session-flow/skills/continue-in-background/SKILL.md (step 1, "Dirty-tree gate")
Steps to reproduce
- In a git repository, set
"worktree": {"bgIsolation": "none"}in.claude/settings.json. - Leave an uncommitted change in the checkout.
- Run
/session-flow:continue-in-background.
Expected behavior
The gate accounts for worktree.bgIsolation. With isolation off, the launched session sees the uncommitted changes, so the "changes won't carry over" reason for refusing does not apply. The real risk is different: the background session and the user would edit the same checkout at the same time, and the launch report should say so.
Actual behavior
SKILL.md:124-130: "Background sessions move into an isolated git worktree (a fresh checkout) before editing files (https://code.claude.com/docs/en/agent-view), so OTHER uncommitted changes in this checkout would NOT carry into the launched agent's edits. Any such changes → do NOT launch". The only exception is a session already inside a linked worktree.- Live docs, https://code.claude.com/docs/en/agent-view#how-file-edits-are-isolated (read 2026-10-12): "To turn off worktree isolation for a repository where git worktrees are impractical, set
worktree.bgIsolationto"none". Background sessions then edit your working copy directly without moving into a worktree first." The same section lists other skip cases (a session moved to the background with/background, a write outside the working directory). - Nothing in
plugins/session-flow/mentionsbgIsolation(grep -rn bgIsolation plugins/session-flowreturns nothing). The source-control plugin already names the setting (plugins/source-control/hooks/worktree-create-gate.sh:64).
Suggested fix
Read the effective worktree.bgIsolation value before the dirty-tree check. When it is "none", skip the "changes won't carry over" refusal and instead warn that the launched session will edit this checkout in place, alongside the user. This is a gate-logic change, not a pointer fix.
Environment
session-flow on main as of 2026-10-12.
Found during the upstream-pointer sweep (PRs #7061-#7274).
- Lenguaje dominante
- Shell
- Estrellas
- 22
- Forks
- 2
- Merge medio
- 8 h 27 min
- PR fusionados (30 d)
- 957
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de melodic-software/claude-code-plugins
-
priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
melodic-software/claude-code-plugins#7351 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
agent-ready priority: high work-class: scoped
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
melodic-software/claude-code-plugins#7312 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail thresholdAbiertoneeds-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
melodic-software/claude-code-plugins#7286 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
melodic-software/claude-code-plugins#7282 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
needs-triage priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
melodic-software/claude-code-plugins#7273 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
e2e-failure ready-to-code
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
redhat-developer/rhdh-plugin-export-overlays#4391 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
documentation good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
graygarbage/HermesKey#20 ·
-
review-bot
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
midagedev/bloomery#151 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
mattpocock/skills#1269 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 2 días