AI Agents
CommanderQ answers you and hands each job to the specialist built for it.
Maturity: Beta overall. Each agent below carries its own maturity, from the agents status record. Read from the QuoxCORE code (1b8bf54d).
| At a glance | |
|---|---|
| What it is | Quox runs specialist AI agents. CommanderQ answers you first and hands each job to the agent built for it. |
| Where it runs | Inside your QuoxCORE server. Some agents arrive with a paid add-on from the store. |
| When to reach for it | You want to know which agent does what, or which add-on brings the agent you need. |
| How to start | Ask in chat, or run quox chat "check the certificates on web-01". CommanderQ picks the agent. |
How the team works
CommanderQ is the front door. It answers simple questions itself and hands the rest to a specialist with a delegation tool. The team is flat: CommanderQ, then the specialists. There is no chain of managers with extra permissions.
What an agent may do comes from the tools it is granted, not its place in the team. These rules are enforced on every hand-off:
- an agent cannot delegate to itself;
- a chain of hand-offs is at most two deep;
- an agent can only pass on work that fits the scope it was given.
You can also address an agent directly by name.
The core agents
These ship with every QuoxCORE install.
| Agent | Job | Maturity |
|---|---|---|
| CommanderQ | The front door: answers you, or hands the job to the right specialist | Stable |
| WARDEN | Security checks: logins, certificates, permissions | Stable |
| CIPHER | Network diagnosis: ping, DNS, routes, ports | Stable |
| DAEDALUS | DevOps: containers, deployments, automation | Stable |
| HYPERION | Proxmox virtual machines: list, start, stop, snapshot | Experimental |
| METRICS | Prometheus queries and alerts | Stable |
| INSIGHT | Grafana dashboards | Stable |
| VIGIL | Uptime checks and notifications | Stable |
| KEEPER | Backups and updates | Experimental |
| PRISM | Analysis, planning and classification | Stable |
| SCHOLAR | Research, and looking things up in memory | Stable |
| GEMINI | A second opinion: review and synthesis | Stable |
| PERPLEXITY | Web research and fact checking (needs a Perplexity key) | Stable |
| ImagesQ | Image generation | Stable |
| WEAVER | Builds workflows | Stable |
| TESTER | Quality checks | Stable |
Agents that come with an add-on
These arrive when you install the add-on from the store, where its price is shown.
| Agent | Job | Add-on | Maturity |
|---|---|---|---|
| VULCAN | Code and GitHub work | GitQ | Stable, needs a GitHub connection |
| NETWATCH | MikroTik routers | RouterOS Manager | Stable |
| JANUS | The gate for SSH to your other machines | QuoxBastion | Stable |
| ARCHIVIST | Files and document intelligence | Advanced Memory | Experimental |
| ARGUS | Wazuh security events | Wazuh SIEM | Roadmap: connector not built yet |
An example hand-off
This shows the shape of a hand-off. It is an illustration, not a recorded run.
You: "Is the certificate on web-01 about to expire?"
CommanderQ: hands the job to WARDEN (security)
WARDEN: checks the certificate with its granted tools
-> "Expires in 12 days. Want me to open a renewal task?"
Any risky step pauses for your approval first. See Safety.
Limits
- Delegation lists are advisory today. Each agent has a list of agents it may hand work to. A hand-off outside that list is logged, not blocked. The rules above (no self-delegation, two-deep chains, scope) are enforced.
- HYPERION cannot clone VMs yet. Cloning is planned.
- Some agents need outside keys or connections, such as Perplexity and GitHub.
- ARGUS is on the roadmap. Its Wazuh connector is not built yet.
Related
- Introduction: agents, tools, approvals, safety levels and evidence.
- Architecture: how a request reaches an agent and becomes an action.
- Safety: approvals and safety levels.
- Store: add-ons that bring more agents.
Last verified 2026-10-29 against QuoxCORE 1b8bf54d (agent registry) and the agents status record.