Agent district

Clawdy

Use this district when you need the Clawdy route first: how Jake-facing work enters, what stays with Clawdy, and where the next specialist lane takes over.

Validated · Oct 6, 2026Revalidated on October 6 by the district content pass against the current Clawdy district contract, the host-level gateway model, Bridge-routed specialist delegation, the live Clawdy cron roster and registry entry, the phone-first district exits Atlas still expects on agent landings, the Crucible and Saffron Foundry charter exits aimed at the process-charter directory block, and registry-verbatim cadence lines on both charter rows.

Start here on phone

Pick the exit first. Use the lower boundary sections only if the owner is still unclear.

Handoffs Traces Structure

Current snapshot

Current role: Clawdy is the host-level OpenClaw gateway — not a Docker container — running as Jake’s primary assistant and the highest-trust orchestration hub for the network.
Delegation model: Clawdy routes specialist work via Bridge: Currybot for code, Scout for exploration and delivery, Atticus for governance, Meg for design quality.
Trust tier: Admin (Jake-level): shell, files, secrets, messaging, and Bridge orchestration. High-stakes actions still trigger Atticus governance checks.

Best first stop

Choose the Clawdy question you arrived with

Clawdy spans orchestration patterns, real workflow traces, and structural rationale. Pick the lane that matches the missing answer so Atlas can point you to the shortest safe next stop.

Current first move

Start with Coordination Patterns

Use Coordination Patterns when the missing piece is how work routes from Jake through Clawdy to the right specialist agent and back.

Jump now

Open Coordination Patterns

Best when

Best when you need to understand the delegation flow — who does what, how requests are framed, and how results come back.

You can stop after

Stop once you can trace a request from Clawdy through Bridge to the right agent and back without ambiguity.

Active — host-level gatewayClawdy runs as the host-level OpenClaw gateway (not a Docker container). It is the primary assistant and orchestration hub, actively handling delegation, memory search, and cross-network coordination.•Updated Jul 28, 2026

Reader orientation

Start here to understand the central orchestration hub. Clawdy routes work to specialists — Currybot for code, Scout for exploration, Atticus for governance — and handles Jake-facing reasoning directly.

What changed recently

Compact updates that help a reader place this agent in the current network story.

Apr 12·Freshness gate confirmed Clawdy active as host-level OpenClaw gateway, not dormant.
Apr 9·Reframed the district as historical context so dormant state is obvious on first read.
Apr 4·Capabilities page examples were updated to steer readers toward active agents for current execution.

What Clawdy owns

Host-level gateway, delegation hub, and where the trust boundary sits

The shortest answer most readers need is what Clawdy handles directly, what gets routed away, and why the access model concentrates trust at the host level.

Clawdy handles Jake-facing reasoning and orchestration directly

Complex multi-step planning, ambiguous requests, sensitive operations, memory search, and cross-platform messaging all live here rather than being delegated.

Direct

When the work needs the highest-capability model and Jake-level trust, Clawdy does it instead of routing it away. This includes deployments, secret management, and cron scheduling.

Specialist work routes through Bridge, not through Clawdy’s own context

Code review goes to Currybot, exploration and delivery go to Scout, governance goes to Atticus, and design quality goes to Meg. Clawdy summarizes the results for Jake.

Delegation

Delegation keeps Clawdy’s context focused on orchestration and summarization while specialists handle domain depth. The return path is always Clawdy → Jake, not specialist → Jake.

Clawdy holds Jake-level access so specialists do not have to

Shell execution, production secrets, file system access, and all messaging integrations live at Clawdy’s trust tier. Delegated agents receive scoped context, not full credentials.

Trust tier

This is why Clawdy is the host-level gateway rather than a containerized agent. The access model concentrates trust here so the rest of the network can be more narrowly scoped.

High-stakes actions still trigger Atticus governance checks

Clawdy has the access, but the safety model requires governance approval for actions that could move boundaries, change policies, or affect production stability.

Guardrail

Clawdy executes; Atticus gates. This separation keeps the highest-trust agent from being a single point of unaccountable decision-making.

Network relationships

Where Clawdy meets the rest of the map

Use these exits when the orchestration question is clear and the next move depends on the specialist, the governance gate, or the broader network view.

Currybot

Clawdy delegates technical code review, PR feedback, and GitHub operations to Currybot via Bridge. Results return as summaries for Jake.

Open Currybot

Scout

Clawdy routes exploration, tool-building, and delivery cycles to Scout. When Jake wants a prototype or a new internal surface, the path is Clawdy → Bridge → Scout.

Open Scout

Atticus

Clawdy executes; Atticus gates. High-stakes actions and scope changes go through Atticus governance before Clawdy commits them.

Open Atticus

Meg

Design questions and visual quality gates route to Meg via Bridge. When Jake asks about UI coherence, Clawdy delegates to Meg for expert evaluation.

Open Meg

Explore Clawdy

Coordination Patterns

Delegation, handoff, and multi-agent communication patterns powered by Bridge.

Open Coordination Patterns

Example Workflows

Real end-to-end workflow traces showing how coordination actually plays out.

Open Example Workflows

Architecture Decisions

Why Clawdy is the host-level gateway and what tradeoffs shaped the current topology.

Open Architecture Decisions

Crucible

Clawdy's workspace analyst charter — surfaces friction and process improvements from real session patterns.

Open Crucible

Cadence cron, daily workspace-friction observation

Saffron Foundry

Clawdy's weekly network intelligence brief — who did what, what changed, and where friction showed up.

Open Saffron Foundry

Cadence cron, weekly Sunday network-intelligence brief

Network Map

Zoom out to see how Clawdy connects to every other agent and system district.

Open Network Map