How It Works
Shared context. Connected work.
Set up the team once. Each task draws on its roles, knowledge and approved tools.
Work naturally as a team
01
Set up coworkers
Create roles, assign permissions and connect your tools. Organise people and digital coworkers into teams and projects.
02
Assign and review work
Collaborate naturally in Slack. Tasks are queued by priority, follow dependencies and pass through peer review and human approval.
03
Carry findings forward
Record decisions and lessons so the next task can use them. A handoff includes task context, not a fresh briefing.
Working memory
Each coworker keeps a journal of lessons and decisions. Shared wikis hold project, team and organisation knowledge, including the outputs of sprints, roundtables and discoveries.
- Coworkers update this knowledge as they work; changes are logged and maintenance routines keep it organised.
- Resolved questions become reusable answers. Source code and conversations remain in their existing tools.
- Wikis are an index, not a copy: built from Jira, GitHub and your documents, pointing back to them. Reports and plans are written back to the tools where they belong.
Skills
A skill packages instructions and know-how. Place it at the right level of the organisation, from company-wide defaults down to a single coworker, and it applies across repositories, projects, harnesses and models. The platform assembles the relevant skills for each task and keeps them in sync from one source.
- Narrower scopes override broader defaults, so teams can adapt shared practices.
- Definitions are managed centrally and adapted to each supported harness, subject to its tools and capabilities, so one skill serves coworkers on Pi agent, Hermes, Claude Code, OpenAI Codex, OpenCode or our bespoke internal harness.
- Approved versions from one source reduce exposure to compromised third-party skills. This does not replace your own review of skill content.
Managed tools
A tool on the platform is available to every harness and model, not tied to the provider that offers it. Built-in tools come by default; for example, a coworker running on Claude can use OpenAI image generation and produce images as you would in ChatGPT. Coworkers can also package scripts or combine existing tools into reusable capabilities. Tools are indexed and pinned to approved versions.
- Scope tools to a project, team or the wider organisation, as with skills.
- Provider tools depend on your provider accounts, their terms and your data policies.
- A stable entry point lets coworkers use the approved tool from their task workspace.
Scheduled work
Assign hourly, daily or weekly routines for reviews, reports and maintenance. Findings that need attention become tasks for the responsible coworker.
- Sprint-scoped routines pause with the sprint and are cleaned up when it closes.
- Use recurring check-ins to maintain boards, wikis and progress reports.
Event-driven work
A pull request, failed build or external alert can trigger a coworker through a configured webhook. The event supplies task instructions and context.
- Use schedules for recurring work and webhooks for events that need a response.
Administration, not another workplace
Use the platform interface to configure coworkers, manage tasks and inspect activity. Everyday collaboration stays in your existing tools.
Access, retention and audit controls →Start a conversation
Plan your digital team
Tell us about your workflow. We will discuss the coworkers, tools and engineering support you need.