Repository navigation
Conversation
… launched Godspeed A Claude Code session exports its session id, messaging socket and token, effort and IDE port to its children. When Godspeed's engine was started from one (a terminal inside Claude Code, or an agent running the CLI), every claude it spawned inherited them and acted as part of that session, with its effort overriding the chat's. The Claude CLI harness passed all of them on; the ACP, Pi and OpenCode adapters dropped only three. Both paths now drop the full marker list. Inspired by: pingdotgg/t3code@47f2c8d29e
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.
What T3 added
pingdotgg/t3code@47f2c8d29e: a Claude Code session exports markers to its children (
CLAUDECODE,CLAUDE_CODE_SESSION_ID,CLAUDE_CODE_MESSAGING_SOCKET/_TOKEN,CLAUDE_EFFORT,CLAUDE_PID, …). Aclaudespawned with them acts as part of that session. T3 now strips them before starting Claude.How Godspeed does it
If the engine is started from inside Claude Code (a terminal in Claude Code, or an agent running the
godspeedCLI), every Claude chat inherited those markers.CLAUDE_EFFORTalso overrode the chat's chosen effort. The direct Claude CLI harness passed all of them on. The ACP, Pi and OpenCode adapters (process::owned::configure) dropped only three.crates/harness/src/process/owned.rs: the full 13-variable list plusremove_claude_session_markers.configureuses it.crates/harness/src/claude/mod.rs: the run command, the initialize probe and the--thinking-displayprobe all call it. The CLI's entrypoint is left alone.47f2c8d29e, plus new T3-GAPS rows (model/effort switch divider, withdrawn Claude approvals, managed policy).Screenshots: not available (no UI change).
Tests
cargo test -p zeron-harness --no-fail-fast: all pass (lib 435). The two env tests now assert that the session markers are removed.cargo build -p godspeed: okcargo check --workspace --tests: okCheck by eye
Start the engine from a Claude Code terminal, then open a Claude chat with effort set to low. The run should start as a new session, and its effort should not follow the launching session's
CLAUDE_EFFORT.🤖 Generated with Claude Code