Repository navigation
Conversation
…fold Claude messages carry no answer phase, so clients fold every message but a turn's last one under Worked for. An answer followed by more work (a tool call, a question card, a stop-hook continuation) then disappears and reads as no reply. With T3CODE_CLAUDE_ANSWERS_VISIBLE=1, a finished Claude message that reads as an answer (at least 400 characters, or 150 with a heading, list or table) is tagged final_answer, which web and mobile already keep outside the fold. Short progress notes still fold. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
omar7550
force-pushed
the
feat/claude-answers-visible
branch
from
November 17, 2026 16:57
d7b51ce to
7f8a6b3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
A reply to a message often looked as if it never arrived. The agent wrote the full answer, then did more work in the same turn (a tool call, a question card, or a stop-hook continuation) and ended with a short closing note. Clients keep only a turn's last assistant message outside Worked for, unless the message is tagged
phase: "final_answer". Codex tags its answers that way. Claude messages carry no phase, so the answer was folded away, and the user resent the question to see it. The same answer then came back as a new turn.Upstream issue: pingdotgg#8879. Earlier client-side attempts were closed (pingdotgg#29859 showed every assistant message; pingdotgg#8075 used a length rule). This patch stays local for that reason.
Change
With
T3CODE_CLAUDE_ANSWERS_VISIBLE=1in the server's environment, a finished Claude message that reads as an answer is taggedfinal_answer. "Reads as an answer" means at least 400 characters, or at least 150 with a heading, list or table. Web and mobile already keepfinal_answermessages outside the fold, so no client change is needed. Short progress notes ("Now checking the deploy log.") still fold. Without the variable nothing changes.Verification
final_answerentries from the fold.final_answeronly when the setting is on. All 470 tests inClaudeAdapterV2.test.tspass; server typecheck, lint, fmt and knip are clean.local/nightly-patched, and on the Mac desktop app through the bundle patch int3code-local-patches.Written with Claude Code (Claude Opus 5.5).
🤖 Generated with Claude Code