Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

A new window's wall shows another window's conversation as open here

Abierto
  • ¿Algo no está bien?
#1,583 0 comentarios 0 reacciones 1 asignado Ver en GitHub

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
52/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
cli

Línea de trabajo

Start by reproducing the two-window flow from the issue using the dev build, isolated HOME, and the alt+v wall. Trace how the wall determines “open in this window” and how making a team changes held conversations; done means an e2e check shows B has 1 open and leaves A’s conversation in A.

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

Descripción

area:chat bug sev:serious

Seen on: dev 837b2b0.

Behaviour

In a fresh window the wall read 2 open and showed a conversation held by another window as a tile, already selected once space was pressed on this window's own tile. After clearing it and making a team, the other window was on home with moved to another window · enter on home brings it back. The wall of a window should show only that window's conversations as open here, and working the wall must not move another window's conversation.

Replication

  1. Build dev 837b2b0 (git checkout 837b2b0 && make build, binary bin/codeaf), or install the dev build with curl -fsSL https://agentfield.ai/get/devaf | bash.
  2. Use an isolated profile: export HOME=$(mktemp -d), export OPENROUTER_API_KEY, and keep the default model (~deepseek/deepseek-v4-flash-latest, crew on auto).
  3. On a busy machine set task.max_load to 0 (/settings, Tasks) so the busy-machine gate does not hold tasks.
  4. Window A: cd $(mktemp -d) && git init -q && codeaf, start a conversation and send a message.
  5. Window B (same HOME): cd $(mktemp -d) && git init -q && codeaf, send a message.
  6. In B, alt+v: count the tiles (2 open), press space on B's own tile, then s and make a team.
  7. Look at window A.

Evidence

  • B's wall: 2 open, A's conversation listed as a tile and selected.
  • Window A afterwards: moved to another window · enter on home brings it back; A's home lists its conversation as another window.
  • Code path not traced in this pass; the exact key that moved it was not isolated.

Guessed cause

A guess from reading the code, not a confirmed diagnosis. open in this window is read from the HOME's held set, not from the window's own.

Acceptance

  • e2e: with two windows as above, B's wall shows 1 open, and making a team from B's wall leaves A's conversation in A.

Found while writing the public docs; manual text differences are in #1545.

🤖 Generated with Claude Code

Lenguaje dominante
Go
Estrellas
115
Forks
14
Merge medio
9 h 37 min
PR fusionados (30 d)
755

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

  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 Agent-Field/CodeAF

Todos los issues de Agent-Field/CodeAF

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.