SUZENT / Blog

What Is Regent? Suzent's Orchestration Layer

Suzent

Why your AI setup shouldn't turn you into a full-time dispatcher: how Regent acts as a single point of attention across autonomous project sessions, and how it differs from sub-agents.

The first time an AI agent finishes a real task for you, you give it a second one. Then a third. Within a week you have one session benchmarking a parser, another drafting a release post, a third triaging literature, and a fourth watching a deployment.

You are no longer doing the work. You are doing something just as exhausting: you have become the router.

Regent is Suzent's answer to that ceiling. Instead of facing a sidebar full of parallel sessions and polling each one yourself, you talk to a single orchestrator that dispatches work across your projects and only comes back when a decision belongs to you.

Why "Regent"?

Historically, a regent governs a realm in the monarch's stead — handling the day-to-day administration of state, coordinating ministers, and bringing only matters of sovereign consequence to the crown.

In early builds of Suzent, this singleton chat was simply called SUZENT (and in the codebase it still lives in suzent.core.focal_agent, with the fixed chat ID focal-suzent). As multi-project workflows matured, the generic name hid what made the role distinct: it is not "the main chatbot." You are the sovereign; Regent is the executive layer that governs your autonomous sessions while you focus elsewhere.

The Sovereign and the Regent: you hold the crown and set direction, delegating day-to-day governance of project ministers to Regent, who returns only for royal assent.

What Regent actually is

Instead of forcing you to act as a human router across a dozen tabs, Regent sits at the top of the desktop sidebar as a pinned card above your projects.

Before and after Regent: moving from human-as-router across many chat tabs to a single point of attention.

Three strict rules define how it operates:

  1. A single point of attention. You do not juggle tabs for Research, Coding, Writing, and Ops. You talk to Regent in one continuous conversation, and Regent routes work to the right project behind the scenes.

  2. A dispatcher, never a doer. Regent does not write code, edit documents, or run shell commands. Those tools are stripped from its runtime policy. When you ask for project work, Regent uses agent_dispatch to wake or spawn a primary session inside that project — or hand the job to a configured coding agent over the Agent Client Protocol (ACP).

  3. A filter, not a relay. When a project session finishes or hits a blocker, it reports to Regent's inbox. Regent never dumps a 4,000-character execution log into your chat. It distills the outcome to a single sentence — or, if nothing needs your input, records the completion silently without notifying you at all.

Regent architecture blueprint showing the full hierarchy: You at the top, Regent orchestrating across projects, autonomous Project Primary Sessions, and task-scoped Sub-agents at the bottom.

How is this different from sub-agents?

If you have used sub-agents in coding tools (including Suzent's own explore, plan, write, verify, and web sub-agents), it is natural to ask: isn't Regent just a parent agent spawning sub-agents?

No. They solve opposite problems at different layers of the stack:

DimensionSub-agents (agent tool)Project Primary SessionsRegent (focal-suzent)
Core purposeProtect a session's context window & run parallel stepsExecute durable work inside one projectProtect your attention across all projects
ScopeSingle task inside one parent sessionOne project (context.md, workspace, tasks)Every active project in Suzent
LifespanEphemeral (one bounded job, folded under parent in sidebar)Long-lived conversation across days or weeksPermanent singleton pinned at the top of the sidebar
Who talks to itIts parent project sessionRegent (via agent_dispatch) or you directlyYou (and project sessions reporting back)
Execution toolsScoped preset (explore, write, verify, web)Full project toolset (files, bash, MCP, sub-agents)None — orchestration & read-only lookup only
Blocking behaviorCan run synchronously or wake its parent sessionPauses on ask_question, tool approvals, or blocked tasksNever waits on a turn; filters inbox events for you

Put simply: a project session uses sub-agents to divide labor; you use Regent so you don't have to manage the project sessions.

Filter, not relay

Most multi-agent setups fail at the last mile: five agents do five things in parallel and then reward you with five walls of text to read.

Regent's system prompt gives it a harder job: "You are a filter, not a relay." Every event that reaches Regent's inbox — a reply to a dispatched task, a session closing its last open task, or a task marked blocked on user input — passes through two branches:

Filter, not relay: a 4,000-character session transcript is distilled by Regent into a single decision line or suppressed via HEARTBEAT_OK.

Enforced boundaries, not polite prompts

If you give an orchestrator agent a bash tool and a file editor, it will eventually stop orchestrating and start doing the work inline — polluting your main conversation with half-finished diffs and command output.

Regent's boundaries are enforced in code before every turn (apply_focal_tool_policy()):

Project isolation without context bleed

Because Regent never executes project work itself, each project keeps its own working directory, task list, and context.md cleanly separated. Your coding session's stack traces never leak into your research project's literature notes, and neither clogs your conversation with Regent.

When you do want to inspect the raw work, Regent's board groups every project session by where it stands for you — waiting, running, idle, or resolved — and opening any session from the board gives you a one-click tag in the header to jump straight back to Regent.

A COO, not another chat tab

The right mental model for Regent is a Chief Operating Officer. You do not walk from desk to desk checking who is stuck; you state the objective once, let the teams work in their own rooms (with their own sub-agents), and expect to be interrupted only when a call is genuinely yours to make.

Regent is a desktop feature today — the pinned sidebar card, the cross-project board, and the focal-suzent conversation live in the desktop app. The principle behind it is the core of how Suzent scales: sub-agents scale a session's execution; Regent scales your attention.


Quickstart · Focal Agent Architecture · Source (Apache-2.0)

regentmulti-agentorchestrationarchitecture