01 · Responsibility
A role with a clear goal
Define what an agent is responsible for, how it should approach the work, and which tasks belong to that role.
Agent teams
Specialized agents. One coordinated workflow.
Agent teams work best when every role has a defined responsibility and every handoff has a purpose. Cohuno gives you a visual place to design those boundaries, choose each agent's capabilities, and see how the team operates together.
- Defined roles
- Visible handoffs
- Human review
Agent team workspaceEvery role stays inspectable
Team configuredTeam anatomy
Coordination starts with clear boundaries.
An agent team is not a collection of interchangeable prompts. It is an operating structure: roles own distinct work, tasks establish the sequence, context moves through explicit connections, and operators retain the decisions that require judgment.
02 · Capability
Scoped tools and knowledge
Attach approved tools and relevant knowledge to specific agents instead of giving every role the same access.
03 · Coordination
Explicit task handoffs
Connect agents to assigned tasks and pass earlier task output forward where later work depends on that context.
04 · Oversight
Human decisions in context
Insert approval gates in the workflow so an operator can review consequential work before execution continues.
05 · Operation
A shared run record
Observe events, outputs, handoffs, usage, and approval activity from the same workspace that defines the team.
06 · Reuse
Saved roles and workflows
Return to saved workflows, duplicate agents when building related roles, and adapt the configuration to a new process.
Design the collaboration
Give every handoff a reason.
Use the canvas to separate responsibilities and make dependencies clear. One agent can own a focused task, another can transform its output, and a manager role can coordinate a hierarchical workflow when that operating pattern fits the work.
- Describe the goal and operating instructions for every specialized agent.
- Connect task output only to later work that depends on that context.
- Choose sequential or hierarchical processing to match the workflow structure.
Operating principles
A team you can inspect, adapt, and reuse.
Cohuno keeps the configuration concrete. The team's roles, tools, knowledge, task graph, performance profiles, and run behavior remain available for review rather than being hidden behind a single request.
Least capability by role
Give agents the specific integrations and knowledge they need, then review those choices as the role changes.
Readable coordination
Use named agents, task assignments, and visible dependencies so another operator can understand the workflow.
Appropriate human control
Pause at an approval gate when the next action or output requires human authority or judgment.
Evidence from the run
Review events and outputs after execution, then use that record to refine roles, instructions, and handoffs.
Build the team around the work