Teams & Projects

Each project in Operum gets its own AI team — a dedicated set of agents with their own knowledge base, workflow, and configuration.

What is a Team?

A team is a project workspace. When you create a team, you get:

• AI Agents — PM, Architect, Engineer, Tester, Marketing, and Community
• Knowledge Base — Project goals, decisions, and context that agents share
• Workflow — A Kanban board tracking every task through the workflow
• Repository Connection — Optional link to your GitHub repo for code operations
• Templates — Customizable agent behavior definitions

Creating a Team

Click "Create Team" in the sidebar and choose your setup:

• Quick Start — We create a repository for you. Best for new projects.
• Connect Your Repo — Link an existing GitHub repository. Best for existing projects.

Then configure your project:

1. Enter a project name (e.g., "My SaaS App")
2. Pick a color to identify it in the sidebar
3. Optionally choose a template for a head start (web app, mobile app, API, etc.)
4. Click "Create"

Templates

Templates define how each agent behaves. Operum uses a layered template system:

• System Templates — Auto-synced from Operum's cloud. Handle workflow, IPC, branching, and coordination. You don't need to touch these.
• Custom Instructions — Your per-agent customizations. Add project-specific context, coding standards, or special instructions for any agent.

Templates are composed at runtime — system templates provide the foundation, and your custom instructions are layered on top. This means you get the latest workflow improvements automatically while keeping your customizations intact.

Team Limits

Managing Teams

Switching Teams

Use the team switcher in the sidebar to switch between projects. Each team maintains its own state.

Deleting a Team

Open team settings, scroll to the bottom, and click "Delete Team". Note: Deleting a team removes it from Operum but does not delete files from your working directory. If you didn't create your own repo, Operum-provided repo will be deleted permanently in 30 days after deleting a team. Agent files and context remain on disk.

Best Practices

• One team per project — Keep teams focused on a single product or codebase
• Use descriptive names — Make it easy to identify projects at a glance
• Customize your PM first — Add project context to the PM's custom instructions so it understands your product

What's Next?

• Track progress with the visual workflow board
• Set up your knowledge base for smarter agents
• Connect your favorite tools and services