How Eres worksThe model is a CPU
The harness is the intelligence.
Models can change. Eres keeps the memory, rules, permissions, and work record.
Each mission has a plan. Eres assigns the work, checks the result, and records what happened.
What Eres providesBuilt for continuity and control
- Switch live between Claude, Codex, and DeepSeek as the main model. Cursor and OpenRouter run as dispatched agents.
- Multiple missions run concurrently. Eres schedules and manages them.
- Tiered memory across sessions. Long-term context, working memory, and episodic records stay available.
- Approval cards for protected changes. A command you approve repeatedly in a project stops asking.
- Isolated work branches. Each task runs in its own worktree. Eres checks before merge.
- Start Eres on a second machine and it can take over as conductor once the first one's lease is released or expires.
- Independent review. A separate reviewer agent verifies results and records its verdict.
- Use it from the desktop app (with menu-bar tray) or the web (including a phone-width interface).
Your authorityAgents do the work. You keep the authority.
EXAMPLE APPROVALWhen Eres needs your authority
- What happened
- A task reached a decision that needs your authority.
- What Eres did
- Eres completed the safe work and prepared the available options.
- What Eres needs from you
- Choose an option or give a different instruction.
Approve onceAlways in this projectTell Eres what to do instead…
- Eres can merge small verified changes.
- Eres asks before security-critical work.
- Each agent receives only the access that its task needs.
- Eres preserves the source error in the task record.
Eres is private
Kelvin uses Eres each day while the system remains in active development. Public access, documentation, and source code are not available yet.
Read the build log →