Skip to content

Scaffold my-coder: formalize the fleet's worker role - #1

Merged
lorenzoliuzzo merged 3 commits into
mainfrom
feat/genesis-scaffold
Jul 10, 2026
Merged

Scaffold my-coder: formalize the fleet's worker role#1
lorenzoliuzzo merged 3 commits into
mainfrom
feat/genesis-scaffold

Conversation

@lorenzoliuzzo

Copy link
Copy Markdown
Contributor

Copies the canonical My[X] scaffold from my-template and fills the four seams
in CLAUDE.md.

my-coder formalizes fleet-dispatch's inline worker role — the open-ended,
tools-enabled headless coding session that closes a picked issue as a draft
PR — as its own repo, instead of living inline in fleet_dispatch.py
(_prompt_for/_dispatch_one/_finalize_pr).

It's documented as the fleet's one deliberate exception to the
single-narrow-Engine-call pattern every other My[X] tool follows: every other
tool makes exactly one tools-disabled ClaudeCLIEngine call ("judgment
only, never a side effect"); my-coder's core action can't be reduced to that
shape, since closing an arbitrary issue requires reading/editing arbitrary
files, running the target repo's suite and linter, and deciding when it's
done.

  • pytest passes
  • ruff clean
  • change scoped to this repo only

Follow-up (not in this PR): porting fleet_dispatch.py's worker-invocation
logic into my-coder's own CLI so fleet-dispatch calls mycoder build <issue-ref> instead of inlining the session itself.

Lorenzo Liuzzo and others added 2 commits July 9, 2026 11:15
Copies the canonical My[X] scaffold and fills the four seams: my-coder
formalizes fleet-dispatch's inline worker role (an open-ended,
tools-enabled headless coding session that closes a picked issue as a
draft PR) as its own tool. Documented in CLAUDE.md as the fleet's one
deliberate exception to the single-narrow-Engine-call pattern every
other My[X] tool follows, since closing an arbitrary issue can't be
reduced to one bounded judgment call.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@lorenzoliuzzo
lorenzoliuzzo marked this pull request as ready for review July 9, 2026 11:46
CI failed to install the sibling core package because it referenced the
non-existent `mythings-core` (no hyphens) instead of `my-things-core`.

- pyproject.toml: dependency `mythings-core` -> `my-things-core`
- ci.yml: install URL/name -> my-things-core (repo owner's my-things-core@main)
- re-vendor HARNESS.md from canonical mythings._harness (drift test now green)
- CLAUDE.md: stale `mythings-core/docs/...` path -> `my-things-core/docs/...`

Verified locally: pip install against sibling checkout, ruff, and pytest
(incl. harness-drift) all pass.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@lorenzoliuzzo
lorenzoliuzzo merged commit 2ea61c6 into main Jul 10, 2026
1 check passed
@lorenzoliuzzo
lorenzoliuzzo deleted the feat/genesis-scaffold branch July 10, 2026 12:08
lorenzoliuzzo added a commit that referenced this pull request Jul 18, 2026
my-coder v0.1: durability, transcripts, entry point (learned from run #1)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant