Why cliq
Ready-made teams, not a toolkit. Other multi-agent frameworks require you to write Python to wire agents together. Install teams from CliqHub — TDD pipelines, feature development with git automation, human-in-the-loop review, and more — then assemble and run. Describe it, generate it, run it. Need a custom team? Describe what you want in plain English andcliq builder generates a complete team — roles, workflow, gates, and metadata — validated and ready to refine. Iterate on roles, analyse for gaps, and regenerate without hand-writing the whole DAG.
Configure, don’t code. Under the hood, roles are markdown files, workflows are YAML DAGs, and gates are checks the process must pass. Everything is inspectable and editable. No SDK required to start. No classes. No framework abstractions in your way.
Built to share. Teams are portable packages — roles, workflow, and gates bundled together. Build a team once. Use it on your laptop, share it with your org, publish it for others. CliqHub is the registry where teams are discovered and installed.
Any domain. Official engineering teams ship on CliqHub, but the model is domain-agnostic: phases, dependencies, and gates. The same primitives power content pipelines, research workflows, compliance reviews, or any process where specialist agents collaborate.
What a run feels like
- You attach a team to your project
- You start a run with your requirement or inputs
- Specialists do their part, in dependency order
- Quality checks decide whether the work continues, goes back for revision, or needs a person
- You inspect what happened — status, logs, and the result of each phase
Start here
Get started
Install Cliq and finish your first run in a few minutes.
Concepts
Phases, agents, roles, gates — how a team is built.
Running teams
Assemble, pass inputs, run, inspect, and resume.
Agents
Built-in agents, settings, and phase inputs.
Auth
Sign-in, user tokens, and machine enroll tokens.
CLI
Commands and flags when you already know what you want.