// Sub-agent routing table — which agent handles diagnostics, machine health, infrastructure, GitHub, billing, and notifications. Load when the current task is not a direct deployment.
| name | deploy-delegation |
| description | Sub-agent routing table — which agent handles diagnostics, machine health, infrastructure, GitHub, billing, and notifications. Load when the current task is not a direct deployment. |
| metadata | {"version":"1.1"} |
Use the delegate tool to route non-deploy tasks to specialized agents. Pass the agent name and a task description with all relevant context.
| Agent | Handles | Example tasks |
|---|---|---|
diagnostics | Build errors, crashes, runtime issues | "Investigate why deployment X failed" |
machine | Server health, CPU/RAM, Docker daemon, DNS, backups | "Check server memory usage" |
infrastructure | Domain listing/creation/deletion, containers, healthchecks, server management | "List all domains and their status" |
github | Branches, PRs, file operations | "Create a fix branch and PR for the Dockerfile" |
preDeploy | First-time validation, monorepo assessment | "Run pre-deploy checks on this repository" |
notification | Deploy alerts, channel config | "Send a deploy success notification to Slack" |
billing | Credits, plans, invoices | "Check credit balance" |
delegate({ agent: "diagnostics", task: "Investigate deployment failure for applicationId=abc-123. Check logs and container state." })
Always include relevant identifiers in the task: applicationId, owner, repo, branch. The delegate tool automatically injects context formatting for agents that need it.
Delegation is synchronous — process the result in the same response. If delegation returns an error, try using direct tools instead.
Reference for all Nixopus API operations callable via nixopus_api(method, path, body)
Generate Caddyfile configurations for static sites and reverse proxies — SPA fallback routing, cache headers, compression, redirects, and error pages. Use when deploying a static site that needs custom Caddy configuration, or when the user needs SPA routing, caching, or redirect rules.
Generate docker-compose.yml for multi-service setups including databases, caches, and service dependencies. Use when the app needs a database, cache, message broker, or has multiple independently deployable services.
Size container memory and CPU limits, diagnose OOM kills and CPU throttling, and recommend resource adjustments by ecosystem. Use when containers are being OOM-killed, running slowly, or when setting initial resource limits for a deployment.
Build and deploy C/C++ applications — CMake, Meson, Ninja, and Dockerfile patterns. Use when deploying a C or C++ project, or when CMakeLists.txt or meson.build is detected.
Run database migrations safely during deployment — framework-specific commands, pre-deploy vs post-deploy timing, health gates, and rollback strategies. Use when the app has a database migration system and needs migrations run during deployment.