An AgenticLevel archetype

🛰️

The Autopilot

The Autopilot delegates time, not just tasks — sets the destination, arms the autopilot, and leaves the cockpit.

Discover if you're a The Autopilot

The Autopilot is the form that lets go of the reins. Where most hover over every agent step with a finger on the stop button, this type sets the destination, stages the scene, and lets the fleet keep moving on its own for hours. Its signature isn't conducting more closely — it's decoupling progress from its own presence, treating the agent as a colleague on shift rather than a tool that needs babysitting.

How it conducts

This type starts with framing, not execution: it spends its energy nailing the destination because it knows it won't be in the room to correct course midway. Then it releases — long hands-off runs, or scheduled loops that wake on their own and monitor their own progress. It shapes work into blocks large enough to run unsupervised instead of slicing it into micro-steps approved one by one. When it returns, it reviews the result as a whole, in the rhythm of someone who plants at night and harvests in the morning.

Its superpower

Its unfair advantage is the time that runs with no one in the room. While one dev walks a single task to the finish line, this type has loops working through the night and agents crossing whole blocks while life happens away from the keyboard. Few have the stomach to delegate this much; the Autopilot does, because it designs a system that earns the trust.

Its frontier

Its next frontier is the exit gate. A long run that veers wrong at minute five burns the next three hours — and the type only finds out at the end. The growth isn't conducting more closely (that would kill the superpower), it's instrumenting better: checkpoints that abort early, mid-flight health signals, an agent that knows to call for help before it digs too deep. Mature autonomy isn't the absence of control, it's control placed exactly where it counts.

Sub-archetypes

Your work keeps office hours — just not yours.

You're the Scheduled Pilot: your signature is the loop that wakes on its own. You don't just delegate, you schedule the delegation — tasks that fire at set times, monitor their own progress, and report back. Time became a lever you pull: while you sleep or live, the cron works. You turned autonomy into infrastructure.

+ You don't babysit the terminal: your agents wake on schedule and watch themselves. While the rig runs on timed, monitored loops, you sleep, serve clients, or design the next product — the machine is already working for you.

The next move is closing the loop: have one run READ the previous result and retune its own schedule, turning timed tasks into a cadence that learns.

Your L signal for scheduled/monitored loops (schedule/wakeup + monitor) is the strongest in this form — that's what defines you: you don't fire off jobs, you conduct a clock of agents.

You don't sprint alongside the agent — you set it on the marathon and trust its stamina.

You're the Marathon Pilot: your signature is the long, hands-off run. You frame a big block, arm the agent, and let it run for hours without stepping in — because you've learned to prepare the ground so it can go the distance. Where others check at every kilometer, you trust the route you drew and review the whole finish at once.

+ You trust your fleet to run far without your hands on the wheel. Where most interrupt at every step, your agents cross whole marathons alone — and that only happens because you learned to prepare the ground so they don't get lost along the way.

The exciting frontier is resilience mid-marathon: checkpoints and self-recovery so an even longer run repairs itself in flight, never having to call you back.

Your afk_max_run (Rafk) — the longest human-free stretch — runs high and is exactly the signal that sets you apart: it's the distance your fleet covers before it needs you.

Wings & blends

It combines with other forms' wings as the blend leans toward them: a Verification wing becomes the safety net its long runs quietly ask for, and a Tooling wing tunes the autonomous loops so they derail less. Where the Autonomy axis meets Delivery, the type harvests volume at a distance; where it touches Orchestration, the delegated blocks start running side by side.

Computed from your real transcripts · auditable

The form emerges from Autonomy as the vector's dominant pillar: long runs with no human intervention (high afk_max_run) and scheduled, self-monitored loops across the transcripts. It's the structural signature of someone who delegates large blocks and lets them run — measured, not an impression about temperament.