Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

`--once` against an open conversation is refused with a sentence nothing documents

オープン
  • 何か問題がありますか？
#1,338 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
76/100
issue の種類
ドキュメント
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
go
領域
cli, documentation

調査の方向性

Start with errExecutionMode and its check in internal/remote/server.go, then read internal/manual/chat/running-from-the-terminal.md and docs/changes/unreleased/1071-approvals-wheel.md. Run the manual probe in internal/manual/chat_test.go and the stated interactive and control e2e cases. Done means the refusal wording, manual explanation, probe, and invalidates entry agree exactly.

索引モデルが issue の本文から書いたものです。

説明

area:headless area:remote bug sev:papercut

What happened

2026-09-21, PR #1071 at 78ddda475 (on dev@49b4a58fb). The fix round on that PR made headless roads (codeaf chat --once, and any Hello with Headless set) build their own approval gate and refuse to attach to an agent that was built interactive, or the reverse. The refusal is one sentence, errExecutionMode in internal/remote/server.go:

this conversation is already open in a different interactive or headless mode; close it before retrying

It is the right default: a headless caller reusing an already-open interactive agent would inherit that agent's gate, which is the bypass the fix exists to close. But it is a new refusal on a road people script against, nothing documents it, and the sentence does not say which mode holds the conversation, where, or what "close it" means for someone who has the interactive session open in another terminal on purpose. Neither docs/changes/unreleased/1071-approvals-wheel.md nor any page under internal/manual/chat/ mentions it, so the chat cannot answer "why does --once say the conversation is already open".

Replication

Deterministic (no model).

The errExecutionMode path in internal/remote/server.go is reached whenever a hello's Headless disagrees with the mode the agent was opened in; a unit case beside it with a stub engine shows the refusal and its exact bytes. Through the real door: internal/manual/chat_test.go with the probe why does --once say the conversation is already open reaches no page today.

Field (real models).

Open a workspace interactively with codeaf, then from a second shell run codeaf chat --once "say hi" in the same workspace. The second command exits non-zero and prints the sentence above. Needs a provider key only for the first process; the refusal itself costs nothing.

Where

errExecutionMode and its check in internal/remote/server.go; Hello.Headless in internal/remote/wire.go; the --once flag in cmd/codeaf/chatv3.go; internal/manual/chat/running-from-the-terminal.md for the page that should carry it; docs/changes/unreleased/1071-approvals-wheel.md for the entry.

The fix

Three things, all wording:

  1. The refusal names the other side and the way out, on the model of the product's other refusals: this conversation is open interactively in another terminal; --once cannot join it. Close it there, or run --once in a different session. and the mirror sentence when an interactive launch finds a headless holder.
  2. internal/manual/chat/running-from-the-terminal.md gets a ## heading in the asker's words (--once says the conversation is already open) that quotes the sentence and says why it exists: a headless run answers its own approvals and never borrows an open session's gate.
  3. The #1071 change entry's invalidates says that --once used to join an open conversation and now refuses.

Acceptance

  • e2e: an interactive codeaf holding a workspace, then codeaf chat --once "say hi" in the same workspace from a second process: exit code non-zero and the new sentence printed in full.
  • e2e: control: codeaf chat --once "say hi" in a workspace nobody holds runs, prints the reply and exits zero; --once without --yolo still refuses a tool call with needs approval but no resolver is attached.
  • Unit: the manual probe why does --once say the conversation is already open reaches running-from-the-terminal.
  • The manual page quotes the wording exactly as internal/remote/server.go spells it, and the change entry's invalidates names what people believed before.
主要言語
Go
スター
115
フォーク
14
平均マージ
9時間 38分
マージ済み PR（30日）
749

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Agent-Field/CodeAF のほかの issue

Agent-Field/CodeAF の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。