Introducing Hapimatic
Run your AI agents as a distributed fleet
Harnesses supported at launch: Claude Code, Codex, Gemini CLI, and OpenCode.The status of each is on the Install page.
Close the laptop, reboot the PC, lose the network, hit a rate limit or an API error, come back a month later on a different subscription account, and pick up right where you left off.
See it working
One interface for every session, on your desktop, your tablet, and your phone
What's in the open-source core
-
A fleet, not a box
Every Hapimatic session is a peer of every other: see it, message it, spawn it, on any machine you own, any VM we host, or any VM you run. Cluster as many machines as you want and run coordinated sessions in parallel across all of them.
-
Sessions that never die
Server restarts, harness upgrades, crashes, reboots, API outages, and rate limits do not end a session. Park your work for weeks, then come back on a different account, and continue from where you left off.
Gemini CLI and OpenCode sessions do not persist through a restart of the Hapimatic background service.
-
Parallel work without collisions
Each session gets its own worktree, so several agents can work on the same repo, on the same machine, at the same time.
-
Scheduling that runs while you sleep
Run recurring prompts inside a session, and schedule events that start sessions on their own, with the controls a real scheduler needs: overlap rules, operating hours, exclusions, jitter, and backoff.
-
Every session transcript, searchable forever
The complete record of every session stays saved on your node, searchable and recoverable to restart at any time, by you or any agent.
The core is free and open source (AGPL). Paid add-ons (Issue Workflow, Project Manager, Hardware Bench) and hosted VMs are planned; nothing paid is required to run it.