Agents Templates, not copies.

Build an agent in four moves.

1. Start from a template

Every agent begins as a blueprint: PROFILE, SOUL, AGENTS, MEMORY and a policy.json that denies by default.

Browse templates
01

2. Give it a workspace and a channel

Its own files, its own memory, its own channel identity. No agent inherits another's history — ever.

See isolation
02

3. Harden it before it ships

No host execution, no platform secrets, no other agents' sessions. Then an adversarial gate: it must survive attempts to break its boundaries.

Read the gate
03
The method

Four moves. No black box.

🧬

Blueprint

Identity, tone and boundaries defined in files, not prompts.

🛡️

Deny by default

Only explicitly allowed tools are reachable.

🔁

Versioned

Every promotion carries a tag, a rollback path and real output.

📈

Measured

Time, cost and success rate per run — visible from day one.

Ready when you are.

Start with your own key, connect one channel, and watch your first agent take work off your desk.