Work Desks and Specialty Agents: The Architecture Between Sessions and Teams
Sessions, jobs, work desks, and specialty agents are four names for the same primitive — and knowing which one you mean changes how you design, debug, and gover
Principles for the human / agent / robot triad — written at the level of concepts so they outlive any platform, project, or year. Concepts, workflows, and lessons drawn from the practice of running long-lived agents in OpenClaw.
Sessions, jobs, work desks, and specialty agents are four names for the same primitive — and knowing which one you mean changes how you design, debug, and gover
Three guided routes through the manual: start here, memory & goals, and patterns & lessons.
The three pieces to read in the first 30 minutes. Agent loop, the loop-vs-graph distinction, and how the runtime surfaces you use every day fit together.
An agent loop is the repeating cycle an AI agent uses to make progress on a goal.
Once you have built one agent loop, the temptation is to make it bigger.
OpenClaw gives you two useful ways to work with the same system: the macOS app and the browser-based Control UI.
The durable layers. How agents remember, why long-running agents forget, and how an explicit goal turns an agent into something an operator can follow.
The three-layer memory model — short-term, long-term, semantic — is the floor.
The thing that breaks first in a long-running AI workflow is almost never the model.
OpenClaw's Pursuing goal feature is small on the surface and important underneath.
Three patterns that survive contact with real work. What worked, what broke, and what to keep in your back pocket.
Most workspaces need a daily "what changed?" check.
Across long-running agents, the failures that cost the most are not reasoning failures.
Two ways to think about agent memory. The first: the agent writes notes, the user reads them when something goes wrong.
The vocabulary every Triadive article assumes you know. A separate reference layer — read these once, then refer back as needed.
Adding more desks does not make a multi-agent system faster if every desk still reports to the same overloaded coordinator. The CEO-agent bottleneck is the pattern that breaks most desk-based architectures, and it is almost entirely self-inflicted.
Triadive is a working field manual for the human / agent / robot triad. The examples lean on OpenClaw because that's where the practice is most visible right now — but every principle here is meant to outlive the platform it came from.