You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting the factory today needs tribal knowledge, not a command:
the loop driver reads config from the environment only (SELFBUILD_*, internal/loopdriver/config.go:240); nothing reads devagent.json for it, so every knob is an export;
DevagentBin defaults to the bare name devagent (config.go:79), so a checkout that only ever builds ./devagent-go (make build) runs a stale or missing CLI for pane-run/task/preflight/sync-docs;
the start path is make loop-start in the repo (nohup + pgrep) or a hand-made hub job, and the selfbuild/state branch plus the selfbuild issue label are assumed to exist;
devagent create still bakes Node-era argv into its LaunchAgents (dist/src/cli.js at internal/pipeline/create.go:164, scripts/build-loop.sh at :193) — both paths are gone with the retired tree.
Requested change
One lifecycle command per direction:
devagent up — verify → seed → start, then report:
prerequisite gate (reuse commands.RunDoctor/RunInit checks: git origin + gh auth + worker CLI), aborting with the plain-language fix line;
config + state dirs (.selfbuild/{research,goals,logs}, .devagent/queue), selfbuild issue label ensured;
daemon start when down (:7788) and the loop driver detached (setsid + .selfbuild/logs/driver.log + pid file), or --foreground to run it in this terminal;
a final "what is running / where to look / next action" card.
devagent down — stop exactly the processes up started (pid files, never a blind pkill -f).
Fix devagent create's plist argv to the Go self-executable (createSelfExePath(), :216) and devagent loop, dropping the dist/src/cli.js and scripts/build-loop.sh entries.
Acceptance
devagent up on a clean checkout with only make build done starts a supervised-free driver and prints pid + log path + queue depth; a second up is idempotent (reports the live pid, starts nothing).
devagent down leaves no devagent-go loop/daemon process behind and reports what it stopped.
Problem
Starting the factory today needs tribal knowledge, not a command:
SELFBUILD_*,internal/loopdriver/config.go:240); nothing readsdevagent.jsonfor it, so every knob is anexport;DevagentBindefaults to the bare namedevagent(config.go:79), so a checkout that only ever builds./devagent-go(make build) runs a stale or missing CLI forpane-run/task/preflight/sync-docs;make loop-startin the repo (nohup + pgrep) or a hand-madehubjob, and theselfbuild/statebranch plus theselfbuildissue label are assumed to exist;devagent createstill bakes Node-era argv into its LaunchAgents (dist/src/cli.jsatinternal/pipeline/create.go:164,scripts/build-loop.shat :193) — both paths are gone with the retired tree.Requested change
One lifecycle command per direction:
devagent up— verify → seed → start, then report:commands.RunDoctor/RunInitchecks: git origin +ghauth + worker CLI), aborting with the plain-language fix line;.selfbuild/{research,goals,logs},.devagent/queue),selfbuildissue label ensured;:7788) and the loop driver detached (setsid +.selfbuild/logs/driver.log+ pid file), or--foregroundto run it in this terminal;devagent down— stop exactly the processesupstarted (pid files, never a blindpkill -f).devagent create's plist argv to the Go self-executable (createSelfExePath(), :216) anddevagent loop, dropping thedist/src/cli.jsandscripts/build-loop.shentries.Acceptance
devagent upon a clean checkout with onlymake builddone starts a supervised-free driver and prints pid + log path + queue depth; a secondupis idempotent (reports the live pid, starts nothing).devagent downleaves nodevagent-go loop/daemonprocess behind and reports what it stopped.devagent create --dry-runemits plists whoseProgramArgumentscontain no deleted paths.