Frameworks
Claude is the default framework on EarnOrg. Hermes and OpenClaw are also available for some templates.
In the new-agent wizard, framework is the runtime family you choose in Step 1. It defines how the agent runs day to day: schedules, skills, LLM wiring, and how EarnOrg hosts the machine.
A runtime is the hosted environment for one deployed agent. EarnOrg connects it to the selected template and runtime pack, then to supported Thirdfy integrations. See Templates and Integrations at runtime.
Not every template ships on every framework. The wizard only shows launchable combinations for your org.
Claude (default)
New agents run on Claude unless a template says otherwise. EarnOrg templates and creator templates are built for it.
What it is
How it decides
Upstream docs
- Claude Managed Agents overview
- MCP connector
- Thirdfy MCP (execution and delegation)
Also available: Hermes and OpenClaw
Some templates still run on Hermes or OpenClaw. The wizard shows them only where the template supports them. Pick them when a template asks for one; otherwise keep Claude.
Hermes
What Hermes is
Best for
Upstream docs
OpenClaw
What OpenClaw is
Best for
Upstream docs
- OpenClaw documentation
- OpenClaw installation
- Thirdfy OpenClaw skills (optional skill packs for Thirdfy actions)
Quick comparison
| Framework | Hosted by | Typical lanes | Operator surface |
|---|---|---|---|
| Claude (default) | Anthropic, set up by EarnOrg | EarnOrg and creator templates: trading, yield, prediction, LP | EarnOrg agent page: check-ins, positions, memory |
| Hermes | EarnOrg | Trading, yield, prediction packs | Agent page, cron diagnostics, run history |
| OpenClaw | EarnOrg | Soul-driven finance agents, skills | Gateway artifacts, dashboard access, run history |
Runtime lifecycle (all frameworks)
- Provision — org, agent wallet, runtime id, pack version
- Preflight — delegation scopes, template rules, plan allowance, venue readiness
- Run — cron, signal, or manual trigger
- Receipt — execution status and skip reasons in run history
Health and upgrades
- Runtime diagnostics surface adapter errors, funding gaps (for example perps margin), and pack version drift
- You can pin pack versions or roll out upgrades on a schedule that fits your org

