Repository navigation
Chat coding adapter: retry dropped streams, keep context small, nudge toward writing - #75
Merged
Merged
Conversation
… toward writing
Second live refiner build on Argo (2026-10-08, build df9ee3a5): the Code
Implementer ran 98 steps (96 shell commands, no source edit). The
conversation had grown to ~130k tokens, per-step latency rose from ~6 s to
180 s, and Argo then dropped the stream ("peer closed connection without
sending complete message body (incomplete chunked read)"). The adapter
treated that provider error as fatal, so the owning Run stopped.
- Transient transport failures (dropped stream, connection errors, 5xx, as
classified by auxiliary_client._is_transient_transport_error) are retried
on the same route up to 3 times with 5/20/60 s backoff. Retries are
reported as activity, not api_error (which makes the Implementer interrupt).
- Conversation budget lowered from 600k to 240k characters and per-tool
output from 40k to 20k; elided old tool output keeps its first 300 chars.
- After 40 steps (and every further 40) without write_file/edit_file the
model is told to write the assigned source or record the specific blocker.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 8, 2026
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.
Follow-up to #67/#71, from the second live refiner build on Argo (2026-10-08,
build_request_df9ee3a5…, Runrun_7645d122…).What happened
run_command, 3read_file, 1list_files, and no source edit.api_error→CodingTurn.error→ModelCallFailed), so the build endedinterruptedwith no edits.Change (
agent/transports/refinement_chat.py)auxiliary_client._is_transient_transport_error, which covers dropped streams, connection errors, 5xx and 408. Retries are reported asactivityevents, notapi_error, because the Implementer interrupts the turn onapi_error. Non-transient errors, and transient ones still failing after the retries, surface as before.write_file/edit_file(and every further 40), the model is told to write the assigned source or record the specific blocker in.openchia-implementation.json.Tests: 14 pass, 4 new:
Context
Most of the exploration reads library sources and earlier packages outside the workspace. #74 (container shell plus read-only
/ctx/openchia) and #73 stage 3 (curated context) should shorten it further.🤖 Generated with Claude Code