Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,583 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
cli

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Go
Stelle
115
Fork
14
Merge medio
9h 44m
PR unite (30g)
766

Preparare l'ambiente

Non abbiamo ancora controllato i file di configurazione di questo progetto. Parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Agent-Field/CodeAF

Tutte le issue di Agent-Field/CodeAF

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.