my-coder v0.1: durability, transcripts, entry point (learned from run #1) - #3
Merged
Conversation
…run) Improvements driven by the first real run (my-raytracer#2) + a high-effort code review: - Durability: a session that committed real work but then errored/timed out (e.g. hit the turn cap → is_error) no longer discards that work. Its commits are pushed and the run reports `needs_review` (branch pushed, no PR) instead of `failure`, mirroring fleet_dispatch's resume ethos. Only a clean session opens the draft PR. - Diagnosability: persist the redacted session transcript per run and record the session's final_message + transcript path on every terminal outcome, so a failure is traceable after the worktree is gone. - Default `--max-turns` 40 → 60: a cap too low is indistinguishable from a real failure (the first live run hit 30 and exited is_error); a small issue already needs ~30 turns. `--max-budget-usd` stays the real backstop. - Add the `mycoder` console-script entry point (was `python -m mycoder` only). - Review fixes: transcripts co-locate with the ledger (not the invoking CWD, which is often the target checkout); reconcile the documented head branch name with the code (`mycoder/<repo>-<issue>`). 24 tests, 97% coverage. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
First iteration of the continuous self-improvement loop: my-coder gets better every time it's used. Driven by its first real run (my-raytracer#10, Vec3+Ray) plus a high-effort
/code-review.What run #1 taught us
--max-turns 30— the session hit the cap and exitedis_error, indistinguishable from a real failure. With headroom it completed in ~26 turns.mycoderconsole script (onlypython -m mycoder).Changes
needs_review(branch pushed, no PR) instead offailure— mirroringfleet_dispatch's resume ethos. Only a clean session opens the draft PR. New outcome matrix:no_changes(clean, no commit) ·failure(errored, no commit) ·needs_review(committed but session errored / push failed) ·success(clean + draft PR).final_message+ transcript path on every terminal outcome.--max-budget-usdis the real backstop).mycoderconsole-script entry point.Code-review fixes (high effort, 2 findings, both fixed)
.mythings/mycoder-transcripts), not the invoking CWD (often the target checkout).mycoder/<repo>-<issue>).Tests
24 tests, 97% coverage, green under
GITHUB_ACTIONS=true. New coverage: durable-commit→needs_review, transcript persistence + ledger recording, the higher turn default, and the co-located transcripts dir.Readiness
🤖 Generated with Claude Code