By Warp Level · Warp 1
Warp 1 — Connected
Just get the agent talking to your tools.
The trivial first rung. A single agent, a human approving everything — the “hand-fly” default. There's nothing to earn here except a working connection.
Configuration checklist
Connect your MCP servers (GitHub, Linear, filesystem, etc.).
Confirm the agent can read the repo and call its MCPs in-session.
What “done” looks like
You can open a session, point the agent at the repo, and it can list files, read a ticket from your tracker, and check a PR — all without you copy-pasting context. That's the whole bar. Everything still routes through your approval.
If you haven't connected CloudClawer's MCP server yet, the MCP Connection guide covers both paths — the Claude.ai custom connector and the terminal CLI.
When to climb
Move to Warp 2 once the agent is reliably connected and you've watched it work a few small tasks end-to-end. Warp 2 is where you start making reversible work autonomous — which means first building the hygiene and the safety spine that make autonomy safe.
Configure this feature directly
The Forward-Deployed Agent →
The embedded-engineer model and the npm client commands