Core Concepts
This page explains the key concepts that make up Minion Workspace.
Minions
Section titled “Minions”A minion is an AI agent (Claude Code) that works on a machine of its own: a cloud VPS Minion Workspace sets up, a PC or server of yours, or a Docker container. The machine runs Minion, which consists of:
| Component | Description |
|---|---|
| Minion Agent | A service that keeps a connection out to Minion Workspace and carries its requests: chat, runs, terminal, screen sharing, files. No port is opened on the machine |
The minion user | The OS user the AI works as, separate from the agent. Its tools and permissions are set from Minion Workspace |
| Claude Code | The AI’s runtime, installed from the minion’s Brain tab |
| Screen | The machine’s screen (Windows, macOS) or a virtual display (Linux, Docker, cloud VPS), shared to Minion Workspace |
| Updater | Installs new versions of Minion by itself (not in Docker) |
See Adding and Managing Minions for how to add one.
Projects
Section titled “Projects”A project is a unit that groups workflows and contexts together.
- Add people and minions as members, each with a permission (Admin / Editor / Member) that decides what they can change. See Project members and permissions
- Define shared context in Markdown
- Anyone in the workspace can view a project; only members can change it
Boards
Section titled “Boards”A board is where a project’s to-dos are written down, one ticket each, and lined up. Tickets move left to right through five columns — Backlog → Todo → Doing → Review → Done — so a ticket’s column tells you who is doing what and where things are stuck.
- A ticket can be assigned to a minion as well as a person. Write down what “done” looks like (the acceptance criteria), and the minion does the work and moves the ticket to Review
- Once there are a lot of tickets, filters, custom fields, sprints and the roadmap are there to help
- Opt-in per project (enable it in the project’s Settings tab)
The difference from a workflow is the shape of the work. A workflow runs a fixed procedure again and again; a board is for writing down work as it comes up and moving it along one ticket at a time. Use workflows for repeatable procedures and the board for work that comes up as you go.
See Board for details.
Skills
Section titled “Skills”Skills are reusable prompts for Claude Code. They are defined as SKILL.md files and version-controlled.
---name: my-skilldisplay_name: My Skilldescription: A description of the skill---
Write your prompt body here.Skills can also include accompanying files (templates, configs, etc.).
Workflows
Section titled “Workflows”Workflows are project-scoped graphs that coordinate skills and multiple minions with organizational governance. They are built in the HQ visual editor from typed nodes connected by edges (a DAG — directed acyclic graph), rather than a single straight line of steps.
flowchart LR S(("Start")) --> A["Skill: fetch"] A --> C{{"Conditional"}} C -->|ok| F[["Fan-out"]] C -->|error| E(("End")) F --> J(("Join")) J --> R{"Review"} R -->|approved| E- Parallel execution, fan-out/join, and conditional branching — express real dependencies, not just a linear sequence
- Can be scheduled via cron expressions, triggered on-demand from HQ, or started from outside over a webhook URL
- Each node can be assigned an execution role (PM / Engineer)
- Review nodes insert human (or minion) approval gates with revision loops
- Full version control — each change creates an immutable snapshot
- Complete audit trail tracked in HQ database
See DAG Nodes for the available node types.
Routines
Section titled “Routines”Routines are minion-scoped pipelines for autonomous, self-contained scheduled tasks.
flowchart LR A["skill-1"] --> B["skill-2"]- Owned by an individual minion, not a project
- Run autonomously on the minion’s cron scheduler without HQ involvement
- No role assignment or review gates — the owning minion executes all steps
- Always use latest skill versions (no version pinning)
- Execution history stored locally on the minion
Think of routines as a personal crontab for a minion.
How to choose
Section titled “How to choose”The key differentiator is governance level and orchestration complexity, not whether multiple skills are involved:
- “Who runs this?” is one minion → Routine
- “Who runs this?” depends on roles → Workflow
- Need review gates or audit trails? → Workflow
- Need parallel branches, fan-out, or conditional routing? → Workflow
- Autonomous personal habit? → Routine
The same skills can be used in both. See Routine Design for detailed comparison and examples.