onward.
Autonomous goal engine In development

Give it a goal.
It keeps going.

Less “continue.” More progress.
Two agents and a tiny Rust runtime, built toward work that moves itself forward, 24/7.

Meet the engine

The execution core is live-proven.
The continuous goal supervisor is next.

PROGRESS IS THE POINT01 — ∞
A continuous looping path points onward PLAN ACT VERIFY CONTINUE ↗ ONE GOAL. MANY STEPS.
DESIGNED TO KEEP MOVINGNO SCHEDULE REQUIRED
Rust at the coreTwo independent agentsEvidence before acceptanceOne continuous goal

01 / The idea

A goal is bigger
than an agent turn.

Set the outcome, boundaries, and budget once. Onward is being built to own the next step—and the one after that.

The intended loopInteractive illustration · no agents running

Start with the finish line.

An outcome.
Not another prompt.

Define what done means, where the agents may work, and what they may spend. The goal stays in charge as individual agent turns come and go.

Outcome + workspace + permissions + budget
ENGINE ARCHITECTURE
ACodexWorker one
JevMediation
BCodexWorker two
VIA OPENROUTER
A small Rust hostPermissions. Budget. Verification.

The agents propose.
The host checks what can proceed.

02 / Small by design

Ambitious goals.
Tiny engine.

Rust. Five direct dependencies. No async runtime. A focused controller with room to stay out of the way.

657KiB

Release binary

~6MiB

Live controller peak memory

Controller measurements only. Two Codex processes separately used ~147 MiB combined in a local fixture; the full process tree peaked at ~229 MiB including compiler processes. Sampled on one Mac.

03 / Current build

A real foundation.
An honest starting point.

The first live trial connected two actual Codex workers and Jev through OpenRouter on one small Rust task.

LIVE PIPELINE VERIFIEDFIRST LIVE TRIAL / OCT 2026
15.7s

End-to-end runtime

$0.005227

Total provider cost

20/20

Checks passed by each worker

Passing tests didn’t mean automatic acceptance. Jev preferred candidate B with a 43% probability. The host’s fixed 70% gate stopped acceptance. No winner was promoted; no retry followed.

POLICY HELD

One fixed task proves the connection works. It does not yet prove general goal completion, decision quality, or an advantage over other agent systems.

Built & verified

  • Two isolated Codex workers
  • Live OpenRouter + Jev mediation
  • Independent checks and conservative accounting
  • 55 local tests passing

Next milestone

  • Persistent, multi-step goals
  • Restart recovery with the same budget
  • Pause, resume, and cancellation
  • A resident supervisor and 24-hour soak

Research preview. Today’s CLI runs a bounded test job and exits. Continuous 24/7 operation, durable general goals, and restart recovery are in development. Onward is an independent project.

The direction is onward.

Work should continue
after the conversation.

A goal that survives the turn.
A runtime that earns the next step.

More from Matt Hoffner