82a80e4063
`./sylph-agent loose [task]` starts Claude Code detached with
--dangerously-skip-permissions, running /loop on loop-task.md: work the RE
backlog one item at a time, commit to auto/* branches, never push, record
withdrawn results rather than deleting them. `logs`/`attach`/`stop` to watch and
end it. Runs -d WITHOUT --rm so the transcript survives the container exiting —
for an unattended run that is the only record of what happened.
Two things had to be fixed for an agent to survive being left alone.
MEMORY CONTINUITY. The project is now bind-mounted twice: at /work, and at its
own host path. Claude Code derives its per-project state key from the working
directory, so running at /work handed the agent an empty project instead of the
accumulated one. Verified: a loose run now reports MEMORY=yes and reads back the
same branch and backlog as the host.
FOUR INTERACTIVE GATES, each a silent permanent hang with nobody at the keyboard
-- no error, no log line, just a container that looks healthy and does nothing:
theme picker hasCompletedOnboarding + lastOnboardingVersion. Re-fires
whenever the container's Claude Code is a different version
to the host's, which is the normal case.
folder trust projects.<path>.hasTrustDialogAccepted
bypass disclaimer answered in a pty by bin/claude-autonomous. It has no config
key by design -- it wants a person to accept once, and the
person did so by launching this.
fullscreen upsell fullscreenUpsellSeenCount. This one fires MID-SESSION, after
the pty wrapper has already handed over, so it cannot be
answered the same way.
Config key names were read out of the shipped binary's own strings, not guessed.
The pty wrapper matches SINGLE WORDS. Claude Code draws its UI with
absolute-column escapes between words, so the prompt arrives as
`Yes,\x1b[13GI\x1b[15Gaccept` and a multi-word pattern never matches -- failing
in a way indistinguishable from the wrapper not running at all. It stops
matching once the session is live so nothing later is answered by accident.
~/.claude.json is now mounted read-only at a staging path and copied in, so the
container cannot rewrite the host config. Credentials stay shared read-write in
~/.claude, which is what token refresh and memory continuity need.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
Work the Project Sylpheed reverse-engineering backlog, one item at a time.
Read Syplheed-Reborn/docker/agent/AGENT.md first — it has the container's
tooling and, more importantly, the method rules this corpus is built on.
Each iteration
- Pick one item. Take the next open entry from
Syplheed-Reborn/docs/re/BACKLOG.md, preferring the one whose "first step" is cheapest and most decisive. If you are mid-item from a previous iteration, continue it rather than starting another. - Do the smallest experiment that could settle it, and try to refute your hypothesis before you believe it.
- Write the result down in
docs/re/under the ✅/🟡/❔ convention, with the evidence. A withdrawn or refuted result is a real result — record it, with the reasoning, rather than deleting it. - Commit to a topic branch (below), one logical change per commit.
- Say plainly what you did not settle, and stop the iteration.
Hard rules
- Never commit to
main. Work onauto/<topic>in whichever repo you are touching, branched from the currentmain. Create it if it does not exist. - Never push. No push credentials are mounted, and that is deliberate — a human reviews before anything leaves the box.
- One emulator at a time.
run-canaryenforces this with a lockfile; do not work around it. - Do not edit
main's history, do not rebase shared branches, and do not delete branches. - Measure the oracle; never infer it. An iteration that reasons about the game without running it is a red flag unless it is a pure static-format task.
- Verify with an artifact, not with "it compiles":
build-reborn test(it wires upSYLPHEED_DISC— without it the disc tests silently self-skip and a green run means almost nothing),sylpheed-cli mesh render,screen render,save info, a screenshot.
When you are blocked
If an item needs something the container cannot do — hardware Vulkan for a
rendering question, a push, a decision only the user can make — do not
improvise around it. Write what you found, note the blocker in BACKLOG.md,
and move to the next item.
Pacing
Self-pace. A useful iteration is one experiment plus its write-up, not a marathon; stopping with a clean commit and an honest "here is what is still open" is the goal every time.