Guides
Choose the task that matches your project and current state.
Open beta · 0.7.0-beta.1
Start with your current project and the workflow you want to organize. Map its steps into roles and handoffs, then choose the operation that matches the project's state. Each guide names its prerequisites, proposed effect, exact approval, and next review. Definitions stay in files that follow you, while private credentials and local authority stay separate.
Setup and changes
| Task | Guide |
|---|---|
| Map a manual or one-to-one agent workflow | Map your existing workflow |
| Add a specification to an existing project | Existing project |
| Use an optional separate workspace | Prepare a separate workspace |
| Pin, sync, and apply skills from npm or GitHub | Add third-party skills |
| Create a team, a skill, or a prompt | Create teams, skills, and prompts |
| Change an installed goal or profile | Revise an installed setup |
| Resolve an interrupted revision | Recover a revision |
| Request a registered-work stop | Stop registered work |
For your current project, follow Integrate your first team. Review files and private records before sharing definitions.
Capability boundaries
| Topic | Current guide |
|---|---|
| Agent applications | Codex and Claude Code |
| Tool servers | MCP connections |
| Separate local services | Local backend |
| Shared organization work | Personal and company use |
| Supported comparisons | Workbench |
These pages describe supported tasks and their limits. Setup does not run a team or connect a tool server.
Current support describes supported tasks and limits. Troubleshooting helps identify an actual refusal. Bug reports and feedback explains where to get help.