Running teams

A run executes an assembled team’s phases on the daemon. The CLI starts the run and streams status; it does not orchestrate phases itself. Vocabulary: Concepts. Agent catalog: Agents. First install: Get started.

Lifecycle

cliq init
  → cliq assemble <team-ref>
  → cliq run [-i key=value ...]
  → cliq status / cliq logs

Optional: cliq team install … if the team is not already in the local catalog.

1. Workspace

mkdir my-project && cd my-project
cliq init
# or: cliq init --name my-project

init registers the current directory as a workspace with the daemon.

2. Assemble a team

cliq assemble @cliq/hello-world

Assemble binds a catalog team to this workspace. The daemon validates the manifest (phases, agents, DAG, nested teams).

cliq assemble @cliq/hello-world -w ~/other-project
cliq assemble @acme/release-review --workspace-id <id>

If several teams are assembled in one workspace, pick one at run time with --team.

3. Provide inputs

Teams declare what they need (task text, folder URLs, tickets, …). Pass values at run time:

cliq run -i task="Write a haiku about programming"
cliq run -i message="Hello" -i ticket=PROJ-123

-i / --input is repeatable (key=value). Missing required inputs surface as an error or INPUT_REQUIRED from the daemon — supply them and run again. Some demo teams need no inputs (@cliq/hello-world).

4. Run

cliq run
cliq run --name my-feature
cliq run -t @cliq/hello-world
cliq run -w ~/my-project
cliq run --no-stream          # return after dispatch; watch with status/logs

Flag	Purpose
`-n, --name`	Human-readable run name
`-t, --team`	Team ref when multiple are assembled
`-w, --workspace`	Target workspace by name or path
`-i, --input`	Run input (`key=value`, repeatable)
`--no-stream`	Do not attach to the event stream
`--docker`	Execute inside the team Docker image when configured

The daemon:

Resolves the assembled team and inputs
Walks depends_on and invokes each phase’s agent
Stores each phase output as a run artifact and passes predecessors as upstream
For gates: runs commands, then asks for PASS / ROUTE / ESCALATE

5. Inspect

cliq status                 # current workspace / latest run
cliq status --all           # all registered workspaces
cliq status -w my-project

cliq logs
cliq logs -f                # follow
cliq logs --last 5

Status shows phase progress. Logs show orchestrator and agent output for the run.

6. Resume / rerun a phase

Re-enter an existing run from a named phase (later phases re-execute; earlier outputs are reused when available):

cliq run <run_id> <phase_name>

Example:

cliq run bold-arch writer

Configure agents before AI teams

LLM and connector phases need settings on the daemon:

cliq setup
# or
cliq settings agents.cursor.api_key <key>
cliq settings agents.jira.base_url https://yoursite.atlassian.net

Check readiness:

cliq doctor
cliq agent list

Details per agent: Agents.

Multi-workspace and remote

Goal	Command / path
Run in another workspace	`cliq run -w <name-or-path>`
CI calling Hub	User token — Auth
Another machine	Realm enroll token → `CLIQ_DAEMON_TOKEN`
Hub-dispatched run	Hub API / BFF dispatch

Local cliq run talks to the local daemon by default.

Minimal examples

No API keys

mkdir ~/cliq-hello && cd ~/cliq-hello
cliq init
cliq assemble @cliq/hello-world
cliq run
cliq status
cliq logs

Cursor AI team

cliq settings agents.cursor.api_key <your-cursor-api-key>
mkdir ~/cliq-cursor && cd ~/cliq-cursor
cliq init
cliq assemble @cliq/hello-world-cursor-gate
cliq run -i task="Write a haiku about programming to haiku.txt"
cliq logs


Concepts	Phases, agents, gates, upstream
Agents	Built-ins and input params
CLI	Full command reference
Auth	Tokens and realms

Start

CLI

Running teams

Lifecycle

1. Workspace

2. Assemble a team

3. Provide inputs

4. Run

5. Inspect

6. Resume / rerun a phase

Configure agents before AI teams

Multi-workspace and remote

Minimal examples

Next

​Lifecycle

​1. Workspace

​2. Assemble a team

​3. Provide inputs

​4. Run

​5. Inspect

​6. Resume / rerun a phase

​Configure agents before AI teams

​Multi-workspace and remote

​Minimal examples

​Next

Lifecycle

1. Workspace

2. Assemble a team

3. Provide inputs

4. Run

5. Inspect

6. Resume / rerun a phase

Configure agents before AI teams

Multi-workspace and remote

Minimal examples

Next