Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Fermée
  • Quelque chose ne va pas ?
#1,583 0 commentaires 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@santoshkumarradha y travaille déjà.

Depuis le 27/9/2026.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
52/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
cli

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Go
Étoiles
115
Forks
14
Merge moyen
16 h 30 min
PR mergées (30 j)
238

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Agent-Field/CodeAF

Toutes les issues de Agent-Field/CodeAF

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.