A task typed on Home can land in another project's repository
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 68/100
Línea de trabajo
Start at internal/tui3/home.go:3396 (homeStart) and homeStartWithProject at :3406, then trace /task dispatch and hosted engine selection. Reproduce through codeaf chat in tmux with two projects and an existing engine, then add the unit and e2e coverage described in the issue. Done means Home tasks and plain messages resolve the same project, commits stay in B, the conversation workspace names B, and the Home/task manual and invalidates are updated.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Seen on dev@debffabf6.
What happened
On 2026-09-24, a /task typed directly on Home while Home showed project B opened a conversation attached to project A's still-running engine. The task commit landed in A; B was untouched. The same result occurred on #1410's merge-base. A plain message typed on Home stayed in B. One run also showed could not start the task · the engine did not answer in time despite the task having started elsewhere; that notice was observed once, not independently reproduced.
Replication
Deterministic (no model). None yet: both launches need a conversation with a live engine, which today means a model.
Field (real models). OPENROUTER_API_KEY, deepseek/deepseek-v4-flash, tmux; a few minutes and a few cents.
export CODEAF_HOME=$(mktemp -d) HOME=$(mktemp -d)
A=$(mktemp -d) && git -C "$A" init -q && git -C "$A" commit -q --allow-empty -m init
B=$(mktemp -d) && git -C "$B" init -q && git -C "$B" commit -q --allow-empty -m init
cd "$A" && codeaf chat, send any message, then close the window. A's engine stays up.cd "$B" && codeaf chat. Home's seam readsproject:with B's folder.- On Home, type
/task write h0.txt containing h0and press enter.
Today the conversation opens in A (its meta.json workspace is A) and the commit task: write h0.txt containing h0 lands in A; git -C "$B" log is unchanged. Control: a plain message typed on Home in step 3 opens in B.
Where
internal/tui3/home.go:3396 at dev@debffabf6, homeStart, begins Home submissions; homeStartWithProject at :3406 delegates to target opening. Search /task dispatch through that path and the hosted engine selection.
The fix
Bind the Home draft's project to the new conversation and its engine before dispatching /task. Refuse visibly if that binding cannot be established; never let an existing engine from another project answer it.
Acceptance
- e2e: through
codeaf chatin tmux, a Home/taskissued while A's engine lives creates and commits only in B; the conversation workspace field names B. - e2e: a plain Home message still opens in B.
- Unit: the Home task command and plain-message paths resolve the same target project.
- Update the Home/task manual and
invalidates.
- Lenguaje dominante
- Go
- Estrellas
- 115
- Forks
- 14
- Merge medio
- 9 h 35 min
- PR fusionados (30 d)
- 752
Preparar el entorno
Aún no hemos revisado los archivos de configuración de este proyecto. Empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
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 Agent-Field/CodeAF
-
area:chat bug sev:papercut
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
Agent-Field/CodeAF#1592 ·
Los mantenedores suelen responder en 1 día
-
area:headless bug sev:critical
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1566 ·
Los mantenedores suelen responder en 1 día
-
tui3: slash command completion inserts bare command prefix into prompt instead of navigatingAbiertoarea:chat bug sev:critical
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Agent-Field/CodeAF#1548 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:chat feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
Agent-Field/CodeAF#1510 ·
Los mantenedores suelen responder en 1 día
-
area:tests bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Agent-Field/CodeAF#1489 ·
Los mantenedores suelen responder en 1 día
Todos los issues de Agent-Field/CodeAF
Issues similares
-
area/proxy kind/bug priority/backlog triage/accepted
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
lexfrei/cloudflare-tunnel-gateway-controller#840 ·
Los mantenedores suelen responder en 1 día
-
kind/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 7 días
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug P2 reliability
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
afreidah/s3-orchestrator#1564 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
blinklabs-io/gouroboros#2577 ·
Los mantenedores suelen responder en 1 día