Plan — overview
Plan turns Open Free Max into an autonomous bulk orchestrator — one repetitive job, a pool of agents, carried to the end across crashes, reboots and token-limit windows.
Plan is OFM’s killer feature: an autonomous engine that runs a repetitive job to completion on its own. You stop being the for-loop.
The idea
You hand Plan one repetitive task — a list of units plus what to do with each — and it runs a pool of interactive agent sessions in parallel until the whole batch is done. For hours or days, without you in front of the screen. Then you come back to the finished work.
A campaign is one such job: a source of units, a prompt applied to each, an output convention that defines “done”, and a concurrency budget.
A local daemon that bridges three gaps
Because OFM’s Rust core survives any individual session, it acts as a local daemon — the thing a bulk run needs. It carries the batch across the three things that interrupt long jobs:
| Gap | What happens |
|---|---|
| Crash | A dead session is detected (lease/watchdog) and relaunched. |
| Reboot | The spool is on disk; on restart the batch resumes where it left off. |
| Token limit | Hitting your plan’s cap is normal in bulk — the session parks and auto-resumes when the quota window reopens. See Concurrency & quota. |
Still on your subscription
Every unit is a real interactive session, not a headless call — so a thousand-item batch runs on your plan, never the API meter. That’s the whole reason quota auto-resume exists instead of spilling onto metered credits. See Subscription vs API.
Truth = output files
Plan doesn’t track thousands of rows in memory. The source is re-enumerated on demand and a unit is “done” when its output exists on disk (a file, or a non-empty folder). That makes a run idempotent and resumable: rerun it and finished units are skipped. See Output & done-detection.
Cockpit
The Plan tab shows your campaigns as cards — progress, ETA, live sessions, a readable “quota exhausted · auto-resume ~14:30” line, and failures. Drill in to see each worker and the quarantine. An engine strip shows the global pool and a pause switch.
On a fresh install the tab opens with a guided onboarding — what a campaign is, the three steps to launch one, and a Start with the Assistant button — so the first run explains itself.
Get started
- Create a campaign (Assistant or Advanced)
- Brief format reference
- Recipes — concrete examples