Panopticon · Ideal Customer Profile Companion to the market brief 2026-07-08

The agentic engineer

The in-the-loop agentic engineer who hands real work to a fleet of agents — and refuses to stop knowing what they're doing. Not a role or a company size. A posture: high-delegation, high-oversight.

The paradox to design for: they want vibe-coding-scale leverage while emphatically rejecting the loss of control. Panopticon's state machine — which governs exactly when an agent may act alone and when it must stop and ask — operationalizes "in the loop" instead of merely asserting it. That is the whole pitch.

01 — Who they are

A named identity, defined against vibe coding

The community coined a label and then settled it: Simon Willison proposed "vibe engineering" (Oct 2025), and by his own Feb 2026 update "agentic engineering" had won out — using AI tools aggressively while staying "proudly and confidently accountable for the software they produce." The persona is validated, vocal, and now has a settled name.

✕ They are NOT

Vibe coders who ship unread output · single-agent users · fire-and-forget autonomists · delegation skeptics.

✓ They ARE

Running 3–8 parallel agents, reviewing what merges, treating themselves as the orchestrator/architect — the typing is the agent's, the decisions are theirs.

The tell: they were power-users of their tools before agents — vim/emacs, tmux, dotfiles, config-as-code — and will climb a learning curve for long-term leverage and control. That disposition is why a keyboard-driven, self-hosted TUI lands with them where a GUI-first or "just prompt it" product repels them. (A persona heuristic, not a survey stat — but it predicts adoption better than most.)

"If an LLM wrote the code for you, and you then reviewed it, tested it thoroughly and made sure you could explain how it works to someone else — that's not vibe coding, it's software development."Simon Willison · vibe engineering

The fault line worth exploiting

The persona is splitting into a "review every line" wing and a faster-growing "gate by blast radius" wing (Steinberger's "loop engineering": "not a diff to babysit, but a PR to review"). Both stay hands-on and anti-vibe. Panopticon's per-state "when must the agent stop and ask you" machine is the literal mechanism the second wing is improvising by hand — meet them there.

02 — Their two pains

Both are documented, felt, and already coined into vocabulary

The model stopped being the constraint. Human attention is now the rate-limiter — and these are the two ways it breaks. Echo their own words back to them.

babysitting agentsyou're the bottleneck

1 · The idle fleet

Every agent flips between working and waiting on you; a fleet stalls when you can't tell who's blocked. Practitioners peg the ceiling at 3–5 sessions before context-switching tanks productivity.

"One stops to ask whether it can run a migration. Another quietly waits on a permission prompt… I wasn't coding at that point. I was babysitting."Amit Raz · DEV, Jun 2026
context thrashingsession sprawl

2 · Losing the plot

Many concurrent agents outrun what you can hold in your head — which branch, which task, which one beeped. Coordination overhead is why people "hesitate to spin up just one more."

"Six terminal tabs open, you can't remember which one is waiting for approval, and you've lost track of which branch belongs to which agent."Brizz · "Context Thrashing," Mar 2026

03 — Why Panopticon fits this ICP

Others display the problem. Panopticon governs it.

The crowded field of dashboards (Vibe Kanban, Claude Squad, Conductor, Anthropic's own Agent View) converges on the same primitives — isolation + a board + diff review. They show you which agent is blocked. None decides when an agent should stop and ask in the first place.

The fit thesis

Pain #1 and #2 map 1:1 onto Panopticon's two most distinctive primitives: the turn/blocked model (who's working vs. waiting, at a glance) answers the idle fleet, and the declared workflow state machine (bounded autonomy per state) answers the sprawl — by governing the autonomous-vs-ask turn rather than leaving the human to poll for it. This ICP already self-hosts and lives in the terminal, so adoption friction is near zero.

04 — Value props, re-tested for this ICP

Two legs, not four

Ranked by how differentiated each is for this buyer. The story rests on the first two; the rest supports or should stay off the headline.

Lead

Turn-dashboard — attention routing across a busy fleet

Which agents are heads-down, which are blocked on you. Directly answers "keep the fleet busy" + "track WIP." The turn/blocked model is rare — competitors show sessions, not the ball.

Lead

Gated autonomy — the workflow draws the line

A declared state machine defines what an agent does alone and when it must stop and ask. Unrepresented in the OSS field, and the exact resonance point for the anti-vibe, "gate-by-blast-radius" wing.

Support

Zero-friction spin-up

Container isolation is the differentiated slice; branch + per-repo secret/env management is expected table-stakes. Sells the setup, not the headline.

Deprioritize

Reflection (plan / summarize)

A nice-to-have that Claude Code's plan mode and the hosted planners already do as well or better. Leaning on it invites an unfavorable comparison — keep it as "rounds out the loop," never a lead.

05 — How big

Small slice, steepest curve, Claude-Code-concentrated

A low-single-digit share of all professional developers today — but the most intensive, daily-use, Claude-Code-heavy cohort, and every trend line is climbing. No survey measures "3+ concurrent" directly; these are the closest proxies.

~16%
run multiple / coordinated agents · SO "Agents on a Leash," 2026
9→18%
orgs orchestrating multiple agents, YoY (doubled)
70%
of multi-agent power users are on Claude Code
63%
still rarely/never let agents run on full autopilot — i.e. stay in the loop

Roles cut across seniority by posture: senior/staff ICs, tech-lead "orchestrators," and experienced solo devs who review what merges — the "engineer → orchestrator" shift (Osmani, Zakas). Not a demographic — heavy-AI indie hackers who ship without review are the foil, not the ICP. Anecdotal ceiling: 4–8 concurrent worktrees per dev before review becomes the bottleneck.

06 — Messaging

They define themselves against "vibe" — so word choice is load-bearing

Resonates — lead with control & ownership

stay in controlreview every changeyou're the orchestratorcopilots, not autopilotskeep your agents busymission control for your fleetbounded autonomyhuman in the loop

Alienates — reads as vibe-adjacent

vibe codingfire and forgetautopilotlet AI do everythingship without reading the codeno-codeagentmaxxinghands-off

The load-bearing frame, verbatim from the persona's own manifesto: reviewing and testing AI-written code "is not vibe coding, it's software development." Never imply code ships unread.

07 — Where to reach them

Habitat & vocabulary

Highest-signal venues

  • r/ClaudeCode~344k members, grown from near-zero in ~12 months (+10,000%+) — the core hub; multi-instance / tmux power-user threads dominate.
  • Show HNLiterally this persona's habitat; comparable orchestrator/dashboard launches get real traction. Highest-signal launch venue.
  • awesome-claude-code"Orchestrators" category — durable passive discovery. Low-cost must-do.
  • NewslettersPragmatic Engineer, Latent Space, Simon Willison, Addy Osmani.
  • VoicesBoris Cherny, Peter Steinberger (loop engineering), Steve Yegge.

Keywords they search & self-describe with

parallel agentsmulti-agent orchestrationbabysittingcontext switchinggit worktreesworktree per agenttmux panesagent fleetvibe coding (as foil)

Reddit-verified caveat: "agentic engineering" and "mission control" are thought-leadership framing — not native to Reddit search. For community/SEO reach, use what they actually type: parallel agents · babysitting · context switching · orchestration. Keep "mission control" for the pitch narrative, not the keywords.