docs: stop describing a two-backend program as a claude one - #7
Merged
Conversation
The README opened "A Bubble Tea TUI over the Claude Code stream-json protocol", the WRITEUP called itself a harness for Claude on a Max plan, and BUILD.md listed only the claude CLI as a requirement. All three were written when there was one backend and none of them had caught up. The feature list needed more than a find-and-replace. Several bullets describe things codex does not do — the approval bar, the command palette, AskUserQuestion — so a reader scanning it would conclude the codex backend does them too. It now says which backend it describes and points at the section that lists the differences, rather than qualifying every bullet. entClaude becomes entAgent. A codex reply was being stored under a constant named for the other backend, which is a small lie every reader of the codex adapter had to step over. -resume's help said "claude session id". It takes a claude session or a codex thread now, and the picker sets it from either.
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
1 participant
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.
A sweep for claude-specific copy across every user-visible surface, after the codex backend landed.
What was wrong
-resumeflag helpentClaudeconstantPlus the README's "why this is legitimate" argument, the run instructions, the env-scrub notes and the file table, all of which knew about one backend.
The feature list needed more than find-and-replace
Several bullets describe things codex does not do — the approval bar, the command palette,
AskUserQuestion. Renaming "Claude" to "the agent" in those would have made them more misleading, not less, because the behaviour is genuinely claude-only. The list now states which backend it describes and points at Backends for the differences, rather than qualifying every line.Deliberately unchanged
commandlist.gostill describes/syspromptas claude's response style. That is accurate — the feature is claude-only. What is wrong is that the command is still offered on codex, and that needs a capability set rather than new wording.question.go'sAskUserQuestionreferences. Claude-specific by definition.Verified
go vet, full suite. The rename is compiler-checked and no reference to the old name survives anywhere, including the docs.