Live progress output — streaming per-worker status
cyberine run and npm run cli now emit live per-worker status lines to stderr as adapters
work, rather than surfacing a single blob at the end. The per-worker lines appear as they arrive;
the final judged winner is still printed to stdout after the judge resolves, matching the
existing --print contract.
cyberine run "add a readme section for the new feature"
# stderr (live, as work happens):
# [loop-deepseek-build] tool: write_file(src/foo.ts)
# [loop-kimi-build] generating implementation...
# [verdict:consensus] winner=loop-deepseek-build
# stdout (once, after judge):
# runId: <uuid>
# state: done
# watch: cyberine agents
cyberine run -p "What is 2+2?"
# stderr: per-worker progress lines as above
# stdout: 4 (clean, pipeable)
cyberine run -p "..." | jq -r . # stdout stays a clean single value; progress on stderrForeground run wall-clock timeout — cyberine run --timeout <sec>
--timeout <sec> adds an inline wall-clock auto-kill to foreground cyberine run invocations. If the run (workers + judge) has not finished within the given number of seconds, an abort signal is sent to
Auto-routed implementer fleet on the foreground run
A bare cyberine run "<edit task>" (no --fleet, no --cheap, no CYBERINEBUILDFLEET) used to run only the read-only compare pool and exit 0 with state: done and no diff. The foreground path now...