A clear finish line.
Set an outcome, workspace, permissions, and budget so the engine knows what success means and where it can act.
In development
Give it a goal.
Give it a goal.
It keeps going.
An autonomous goal engine designed for work that takes more than one session. A small Rust core, two Codex workers, and Jev between them.
The execution core has completed a bounded live trial. Persistent goals and the unattended 24/7 supervisor are not implemented or active yet.
THE EXECUTION CORE
01 / The workOne bounded task.
Codex ACandidate
JevDecision
Codex BCandidate
02 / The evidenceVerify before accepting.
OpenRouter connects the workers and Jev. The Rust controller checks results and can stop when the evidence is insufficient.
A goal that outlasts
the conversation.
The direction is a new kind of /goal: an event-driven process that keeps making useful progress without a recurring schedule.
Progress across restarts.
Planned durable checkpoints let the engine resume a goal, recover from bounded failures, and preserve what it has learned.
Results you can inspect.
The target is a plan, act, verify, continue loop with visible receipts and explicit pause, resume, and cancel controls.
These persistent-goal capabilities are the next milestone. The current lab executes bounded trials.
Small core. Concrete evidence.
Built in Rust.
Tested with real workers.
The initial lab runs two actual Codex processes with Jev mediation through OpenRouter. Its published proof separates the controller footprint from the workers it starts.
Read the project evidence ↗- Verified execution core
55 tests and a bounded live OpenRouter trial. Both workers passed 20 checks; the controller stopped acceptance when Jev's preference did not meet the fixed threshold.
- Low controller footprint
The measured Rust binary is about 657 KiB and the live controller used about 6 MiB. Codex workers use additional memory.
- Next: unattended goals
General goals, durable supervision, restart recovery, and a 24-hour soak remain to be implemented and validated.