63 agents. One orchestrator. No overclaiming.

Proxmox specialist - VM lifecycle, snapshots, golden-template clones, the disposable VM pool, cluster health

Network operations specialist - connectivity, traffic, performance

Core introspection specialist - monitors Quox internals, cognitive implants, system topology, and provides health diagnostics

Container fleet overlord, multi-host Docker management, fleet discovery, health audits, space reclaim, and AI diagnostics

Bastion gateway specialist, god of gateways and transitions. Narrates fleet state, guides host management, explains SSH access flow, reviews audit trail, and protects against destructive blind-fires. Read-only in V1; gains direct command execution in V2 when server tools land.

System continuity specialist, backup, restore, migrate, update, and rollback. Ensures QuoxCORE survives across versions and incidents.

Tailscale mesh networking specialist. Monitors device connectivity, manages subnet routes and exit nodes, handles key lifecycle, explains ACL policy, alerts on status changes.

MikroTik RouterOS specialist for network monitoring, troubleshooting, and management. Speaks in plain English for noobs while providing professional-grade capabilities.

DevOps and operations automation specialist, deployments, CI/CD, container management, automation scripts, fleet operations. Does NOT design visual QuoxFlow workflows on the builder canvas (that's WEAVER's job).

Uptime specialist - owns the organisation's Uptime Kuma: status, down services, and the monitor list (changes need human approval); SLA tracking, availability reporting

The All-Seeing Eye, anomaly detection, guided tours, spatial queries, evidence witnessing in Cognitive Core 3D.

Grafana specialist - dashboards, annotations, trend analysis

Prometheus specialist - PromQL queries, alert management, metric analysis

Analysis, planning and classification specialist - objective decomposition review, workflow design, task routing, risk assessment

Wazuh SIEM specialist, Argus Panoptes, the all-seeing watcher. Triages security alerts by severity and rule pattern, prioritises CVEs by exploit availability, narrates FIM diffs, explains SCA/compliance failures, and oversees the fleet of Wazuh agents. Read-only and advisory in V1; destructive actions (agent deploy/remove, active response) gate through HITL approval via the inbox in V2.

Adversarially reviews candidate findings from recon_specialist/web_specialist before anything is reported as confirmed. security_verify_finding persists the verdict, confirmed or refuted, always with a reason.

Reconnaissance specialist for host/service/domain discovery within an authorized security engagement. QUOX-SECURITY Phase 1: sectest_discover_hosts (subfinder), sectest_probe_http (httpx), and sectest_resolve_dns (dig) are real, policy-gated tools; no bastion-managed scan host is configured yet.

Security Engagement Lead. Owns the engagement/scope object for a security testing job, delegates recon/web/verification work to specialists. QUOX-SECURITY Phase 1: engagement/scope tools only, no scanning capability has shipped yet.

Security operations specialist - threat detection, compliance, auditing

Web application testing specialist (auth flows, injection classes, TLS/header posture) within an authorized security engagement. QUOX-SECURITY Phase 1: sectest_probe_http (httpx), sectest_vuln_scan (nuclei), and sectest_inspect_tls (openssl s_client) are real, policy-gated tools; no bastion-managed scan host is configured yet.

Creates and configures agents, assistants, tools, and teams through conversation. The meta-agent that builds other agents. Also plans plugins and capabilities against the real build path, sizing work into QuoxPlan after a sibling check.

The owner of the Quox Dev Suite: builds, dev servers, skill packs and dev sessions. Reads dev server, skill-pack and session state (citing when each host was last seen), reads build status/history from the durable build_receipts store, diagnoses outcomes from the receipt's own message field, runs a narrow blast-radius preflight (direct importers + registry membership), and verifies a deploy actually came up (container alive + HTTP probe) before calling it green. Can file a gripe or fan out a Telegram alert on failure. Proposes, never resolves. Pull-only - no scheduled trigger.

Web automation specialist, navigates, interacts with, and extracts data from any website

Git operations specialist. Manages issues, PRs, releases, and CI across all connected repositories.

GitQ onboarding concierge. Maps a connected Git provider's orgs and repos, guides the user through connecting a provider token to the org vault (guides and verifies, never writes the token itself), and hands repositories to RepoBrain for indexing. Chat-native, no setup screen.

Quick-fire GitHub issue filer, part of the GitQ plugin. Chat-native port of the terminal-only gripe skill - turns a one-liner complaint into a filed, labelled GitHub issue with minimal back-and-forth. Reachable from the dashboard, Discord, and Telegram via the existing chat pipeline.

The codebase cartographer. Answers "where is X", "how does Y work", "what depends on Z" across the Quox repos by querying RepoBrain, returning cited file:line snippets instead of whole files. The conversational front door to an engine that previously had only a CLI and a raw tool.

Terminal-based code execution and system operations specialist. Handles interactive shell commands, script writing, and real-time infrastructure tasks.

Quality assurance specialist - runs tests, validates system components, analyzes test coverage, and provides intelligent test selection

Quox Tool Builder, chat-driven Python tool authoring agent at /tools/add?type=script-forge. Produces governed, sandboxed, signed Quox Tool Definitions ready for the existing install pipeline. Does NOT execute host code or bypass the seven-step pipeline.

Workflow design specialist, builds and edits QuoxFlow workflows on the visual canvas at /workflow-builder. Collaborative, methodical, asks discovery questions before building. Does NOT do ops automation, deployments, or scripting (those are DAEDALUS).

Personal and organisational task management, tracks todos, priorities, deadlines, and completion

Calendar-Q reads a layered agenda across a connected provider calendar, internal events, team schedules, and workflow cron triggers, with an honest per-layer coverage statement, and surfaces human double-booking clashes bounded by the window it actually checked. It can propose and, with human approval, create a single non-recurring event; it has no tool to reschedule, cancel, or create a recurring event in this phase.

InboxQ inbox chief of staff. Reads zone counts, messages, the daily report, and pending proposals, and proposes filing, re-zoning, blocking, and folder-creation changes - every mutation is a proposal a human approves, the agent never executes, resolves, or claims an outcome itself, and it has no tool to send, reply, delete, or mark mail read.

NotesQ notes assistant. Captures, finds, tidies and links the org's notes: searches, reads, creates, appends, tags, restores and (after confirmation) deletes notes, always citing titles and /notes?note=<id> links. Every write is a revision and can be undone.

Inbox triage and human-in-the-loop specialist, categorises, prioritises, summarises, and recommends actions on inbox items

File operations specialist - document analysis, summarization, comparison, and data extraction

The recall agent across memory, wisdom and Qortex: answers from your knowledge with the sources it cites, and also captures notes, corrects them and handles deletion requests. A librarian of your own notes and history, not a general assistant.

Independent review and synthesis specialist, code review, large-context analysis, content generation, and second-perspective sanity checks, on the organisation's default model.

Web research and verification specialist, searches the web with citations, verifies facts against current sources, and performs deep multi-source research using the web search and page-read tools.

Research specialist - documentation, CVE lookup, troubleshooting guides

Facebook Pages specialist for organic publishing, insights, and Lead Ads retrieval.

AI image generation specialist, part of the MediaQ family, creates, edits, and analyzes images using Google Gemini models with a choice of model. Handles text-to-image, image editing, and vision analysis. LLM-backed image tool serving as an agent until MediaQ goes beyond it.

Instagram specialist for publishing, insights, and comment management on the shared Meta credential.

LinkedIn specialist for publishing content, tracking engagement, and managing organisation page presence.

QuoxSignal's triage analyst: explains and challenges an item's triage verdict, lens findings, and drafted proposals, grounded in the evidence in context. It explains and argues; it does not decide (approve/reject/handoff are human acts in the UI).

QuoxSEO analyst, reads the witnessed URL warehouse: crawl summaries, per-URL status and GSC performance, the signed change log, and WARD chain verification. Read-only and advisory; never performs a site change.

TikTok specialist for governed video publishing and draft uploads on a dedicated TikTok credential.

The Herald social suite voice, covering X (Twitter) as its first channel. Verifies connected credentials and drafts posts, threads and deletes; every posting action files an owner approval card and never posts directly. Drafting help in chat is in scope, content-engine features are not.

YouTube specialist for uploading videos, managing metadata, organising playlists, and monitoring channel performance.

The caller-facing outbound voice of QuoxVoice: places the calls Quox makes out (morning wake-ups, briefings, estate alerts, report-ready calls, campaigns). Does not decide when to call (LUCID and triggers), does not own the policy (VoiceQ), and does not place session callouts (Sesha). It speaks; others decide and govern.

The inbound front door of QuoxVoice: answers the phone, authenticates the caller, and routes them to the right agent by delegation. Handles outside callers and SMS, and is the clonable customer template. Inbound only; never places calls.

Liaison to the owner's live Quox Claude and terminal sessions: knows which are running and what each is doing, relays messages to them, and reports what is waiting on the owner. Reached through Reception. Her only outbound action is a call on behalf of a running session; she feeds LUCID's sessions view.

Team leader for QuoxVoice: a pure admin and builder, never caller-facing. Provisions numbers and wires Twilio, creates and customises the voice agents, manages per-org voice settings and attach-to-session tooling, performs the guarded bridge deploy, and owns the outbound policy (DND, thresholds, consent, allowlist) and the voice evidence trail.

Compliance intelligence specialist, direct visibility into AEE, AOCL, VOLT, WARD. Generates reports, verifies chains, grades evidence against the VOLT tiers, explains controls.

Front-of-house operator for the Quox Discord Pro plugin. Lists channel bindings, explains what every mode means, and diagnoses why a bot has gone silent in a channel (usually a Discord permission the bot cannot grant itself). Can bind and unbind channels, but every mutation is held for human approval before it executes.

The running-loop conductor. Reads a QLoop session's WITNESSED turn record (the server-side evidence trail, not a reconstruction), says what a loop has actually been doing, spots a loop going in circles, and proposes a governed halt when one warrants stopping. Read-first and escalation-only: it never reaches onto the host itself.

Catalog navigator and tool-discovery assistant. Surfaces the best tool from a library of ~3200 entries for any given mission, MCP servers, repos, APIs, security tools, OSINT utilities, dev tooling, and more.

Workflow engine specialist: the runtime identity behind QuoxFlow's own executed workflows (fleet, Docker, Proxmox, SSH, and vault-backed credential actions triggered from a running workflow). The ENGINE, not the designer: WEAVER builds workflows on the canvas, QUOXFLOW is the identity a workflow executes as, reached through its own execution rather than chat delegation.

Resident governed agent that ships with every Quox server. The simulated power user the platform runs against itself: drives real CLI, MCP and browser surfaces under a server-side mode (OFF/OBSERVE/PARTIAL/FULL) and a signed capability scope, runs canaries, and files what breaks with evidence.

Settings & configuration warden. Cross-agent concierge for the Settings surface. Explains settings, narrates current state, surfaces dependencies, and (with HITL on destructive changes) modifies configuration. Every change becomes an AEE envelope with VOLT receipt, tamper-evident config history. Orchestrates JANUS/WARDEN/HYPERION/DAEDALUS on settings questions that touch their domains.

Strategic roadmap navigator, reads, queries, and manages the strategic roadmap. Knows every stream, phase, priority, dependency, and plan document.