The operating layer for humans + agents
One view for your whole team, human and AI. Approvals, budget caps, and full visibility into who's doing what.
Early access for builders. No spam.
Every handoff is a context switch. Every context switch is where things fall through. None of your tools were built for a team that's both.
Tasks with context and acceptance criteria
To a human or an agent, with constraints
Your whole team on one board
Approve, revise, or redirect outputs
Budget caps · Approval loop · Execution history
3-5 humans, a growing set of agents, and nobody knows what anyone else is doing. One view. Nothing falls through.
Agents across multiple projects, humans for the rest. One place where all of it is visible and managed.
| handler/one | Linear / Notion | Paperclip | |
|---|---|---|---|
| Unified view of humans + agents | ✓ | ✕ | ✕ |
| Budget caps per agent | ✓ | ✕ | ✓ |
| Human approval loop | ✓ | ✕ | ~ |
| Claude Code + Codex | ✓ | ✕ | ~ |
| No self-hosting | ✓ | ✓ | ✕ |
You bring your team. You bring your agents.
handler/one coordinates both.
“I built handler/one because I needed it. Running a tutoring company, an EdTech platform, and multiple projects, with humans and agents handling the work. Nothing else gave me visibility across both.
In 24 months, most computer work will be done by agents.
handler/one takes your team from mostly-human to mostly-agent.
Task by task. On your timeline.
Onboarding founders and operators running humans and agents together.
Early access for builders. No spam.