القائمة
Deploy a Trinity instance on any server and scaffold a complete ops agent to manage it — handles fresh installs and existing instances
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Abilityai/abilities --skill deploy-new-instanceيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Generate an agent-specific `/update-dashboard` skill that keeps `dashboard.yaml` current for Trinity. Analyzes the agent's purpose and data sources, proposes metrics, gets user approval, then scaffolds a schedulable skill.
Modify an existing playbook based on conversation context or explicit instructions. Use when user wants to update, fix, extend, or refine a playbook they already have.
Create a new skill or playbook. Guides through requirements gathering and generates the appropriate template based on complexity.
عرض SKILL.md
| name | deploy-new-instance |
| description | Deploy a Trinity instance on any server and scaffold a complete ops agent to manage it — handles fresh installs and existing instances |
| argument-hint | [instance-name] |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion |
| metadata | {"version":"1.4","created":"2026-04-30T00:00:00.000Z","author":"Ability.ai","changelog":["1.4: Removed the Step 2b healthcheck patch — trinity#443 fixed the /mcp probe upstream, and the old blanket `sed s|/mcp|/health|g` over every Dockerfile now CORRUPTS a fresh install by renaming the base image's /home/developer/mcp-servers to /home/developer/health-servers. Replaced with a read-only diagnostic","1.3: First-run setup now also seeds the instance GitHub token (Settings → GitHub token — fine-grained PAT, Contents: Read) alongside the MCP API key, in both the SSH and local-Docker paths — it is what the default deploy path (create_agent from github:owner/repo) clones with, so a private-repo fleet is unblocked before the first agent is deployed","1.2: Align with Trinity v0.7.0+ first-run flow — mandatory web setup with admin email replaces the removed setup token (#49), OWASP password complexity enforced (generator now keeps a special char), note that start.sh auto-generates AGENT_AUTH_SECRET/REDIS_* and probes DOCKER_GID","1.1: Scaffold the ops agent by cloning trinity-ops-public instead of generating files inline — agents now ship with the full, maintained skill set","1.0.1: Add a /bug-report skill to generated ops agents, and fix six production deploy gaps — port checks, Dockerfile, and macOS sed compatibility","1.0: Initial version — provision a Trinity instance on cloud, remote, or local Docker and scaffold a complete ops agent to manage it"]} |
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.deploy-new-instance vX.Y — recent: <summary>. Then proceed.
Set up a Trinity instance and create a complete operations agent to manage it.
What you'll get:
/status, /restart, /update, /logs, /agents, /cleanup, /diagnose, /rebuild-agent, /rollback, /telemetry, /provisionUse AskUserQuestion:
Cloud is fully managed — no server to configure.
Display this message and stop:
## Cloud Deployment
For ability.ai cloud hosting, use the standard connect flow:
1. Sign up at https://ability.ai
2. Go to Settings → API Keys and copy your MCP connection URL
3. Run: /trinity:connect
4. Run: /trinity:onboard (to deploy your current agent)
Ability.ai manages infrastructure — no ops agent needed.
Do not continue to agent generation.
Use AskUserQuestion:
Collect the following as three separate AskUserQuestion calls:
SSH Host:
34.123.45.67 or my-server.example.comSSH_HOSTSSH User:
ubuntu for AWS/GCP, root for DigitalOcean)"SSH_USERSSH Key:
~/.ssh/id_rsa, ~/.ssh/my-server.pem (AWS), ~/.ssh/hetzner_key~ to $HOME using echo $HOMESSH_KEYFix key permissions (required — SSH refuses keys with open permissions):
chmod 400 {SSH_KEY}
Test connectivity:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no -o ConnectTimeout=10 {SSH_USER}@{SSH_HOST} "echo connected"
If connection fails, show the error. Common causes by provider:
.pem downloaded at instance creation), or user should be ec2-user for Amazon Linuxgcloud compute os-login or the GCP consoleroot; key must be added during droplet/server creationDo not proceed until SSH works.
SECRET_KEY=$(openssl rand -hex 32)
INTERNAL_API_SECRET=$(openssl rand -hex 32)
echo "Secrets generated"
Store both values — you'll write them to Trinity's .env on the server.
Use AskUserQuestion (tool requires ≥2 options):
openssl rand -base64 18 | tr '+/' '@#' and show the result; store as ADMIN_PASSWORD (keeps =/@/# — the first-run setup form rejects passwords with no special character)Check all four required ports before starting (ss/netstat are universally available; lsof is not installed on many minimal images):
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"for p in 80 8000 8001 8080; do ss -tlnp 2>/dev/null | grep -q \":$p \" && echo \"IN_USE $p\" || echo \"FREE $p\"; done"
For each port reported IN_USE, use AskUserQuestion (tool requires ≥2 options — structure as choice 1: suggested alternate, choice 2: enter custom) to ask for an alternate:
| Port in use | Question | Suggestion | Store as |
|---|---|---|---|
| 80 | "Port 80 is taken. What port for the frontend?" | 8090 | FRONTEND_PORT |
| 8080 | "Port 8080 is taken. What port for the MCP server?" | 8085 | MCP_PORT |
| 8000 | "Port 8000 is taken. What port for the backend API?" | 8100 | BACKEND_PORT |
| 8001 | "Port 8001 is taken. What port for the scheduler?" | 8101 | SCHEDULER_PORT |
Defaults if port is free: FRONTEND_PORT=80, MCP_PORT=8080, BACKEND_PORT=8000, SCHEDULER_PORT=8001.
Display this warning and ask the user to confirm before proceeding:
## Open Required Ports
Before Trinity can be reached from outside the server, you need to open
these ports in your cloud firewall / security group:
Port {FRONTEND_PORT} — Web UI
Port {MCP_PORT} — MCP Server (for Claude Code connection)
How to open ports:
AWS → EC2 → Security Groups → Inbound Rules → Add Custom TCP for {FRONTEND_PORT} and {MCP_PORT}
GCP → VPC → Firewall → Create rule: tcp:{FRONTEND_PORT},{MCP_PORT} targeting your instance tag
Hetzner → Cloud Console → Firewall → Add Inbound rule for TCP {FRONTEND_PORT} and {MCP_PORT}
DigitalOcean → Networking → Firewalls → Add Inbound rule for TCP {FRONTEND_PORT} and {MCP_PORT}
VPS / bare metal → ufw allow {FRONTEND_PORT}/tcp && ufw allow {MCP_PORT}/tcp
If you're on a private network or Tailscale, ports only need to be
reachable by your machine — no public firewall rule needed.
Use AskUserQuestion:
If they say "Skip", note that the web UI and MCP server will not be reachable until ports are opened.
Inform the user: "Deploying Trinity — first run takes 10-15 minutes to build the base Docker image."
Step 1: Verify / install Docker
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"docker --version 2>/dev/null || (curl -fsSL https://get.docker.com | sh && sudo usermod -aG docker \$USER)"
Step 2: Clone Trinity
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"[ -d ~/trinity ] && echo 'already cloned' || git clone https://github.com/abilityai/trinity ~/trinity"
Step 2b: Patch MCP server Dockerfile
No healthcheck patch is needed — and do not apply the old one. The MCP server's HEALTHCHECK has probed /health since trinity#443; the "/mcp returns 400, container reports (unhealthy)" bug this step used to work around is fixed upstream.
The retired workaround was a blanket find . -name Dockerfile | xargs grep -l '/mcp' | sed -i 's|/mcp|/health|g', and running it today corrupts the install: the only remaining /mcp substrings in the tree are a comment and the agent base image's /home/developer/mcp-servers directory, which the substitution renames to /home/developer/health-servers.
If a container really does report (unhealthy), read the actual probe before changing anything:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"cd ~/trinity && grep -n 'HEALTHCHECK' -A2 src/mcp-server/Dockerfile"
If MCP_PORT is not 8080, also update the hardcoded port in all three Dockerfile locations (EXPOSE, ENV, HEALTHCHECK):
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"cd ~/trinity && find . -name 'Dockerfile' | xargs grep -l '8080' 2>/dev/null | while read f; do
sed -i 's/EXPOSE 8080/EXPOSE {MCP_PORT}/g' \"\$f\"
sed -i 's/ENV MCP_PORT=8080/ENV MCP_PORT={MCP_PORT}/g' \"\$f\"
sed -i 's/:8080\/health/:{MCP_PORT}\/health/g' \"\$f\"
echo \"port patched: \$f\"
done"
Update docker-compose.yml port mappings for any non-default ports:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} "
cd ~/trinity
[ '{FRONTEND_PORT}' != '80' ] && sed -i 's/\"80:80\"/\"{FRONTEND_PORT}:{FRONTEND_PORT}\"/g' docker-compose.yml || true
[ '{MCP_PORT}' != '8080' ] && sed -i 's/\"8080:8080\"/\"{MCP_PORT}:{MCP_PORT}\"/g' docker-compose.yml || true
[ '{BACKEND_PORT}' != '8000' ] && sed -i 's/\"8000:8000\"/\"{BACKEND_PORT}:{BACKEND_PORT}\"/g' docker-compose.yml || true
[ '{SCHEDULER_PORT}' != '8001' ] && sed -i 's/\"8001:8001\"/\"{SCHEDULER_PORT}:{SCHEDULER_PORT}\"/g' docker-compose.yml || true
echo 'docker-compose ports configured'
"
Step 3: Configure .env
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"cd ~/trinity && [ -f .env ] || cp .env.example .env"
Set the three critical variables (start.sh auto-generates the other required secrets — AGENT_AUTH_SECRET, REDIS_PASSWORD, REDIS_BACKEND_PASSWORD — and auto-probes DOCKER_GID on fresh installs; note /update never regenerates them, so don't remove them from .env later):
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} "
cd ~/trinity
sed -i 's|^SECRET_KEY=.*|SECRET_KEY={SECRET_KEY}|' .env
sed -i 's|^INTERNAL_API_SECRET=.*|INTERNAL_API_SECRET={INTERNAL_API_SECRET}|' .env
sed -i 's|^ADMIN_PASSWORD=.*|ADMIN_PASSWORD={ADMIN_PASSWORD}|' .env
echo 'configured'
"
For any non-default ports, update .env:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} "
cd ~/trinity
[ '{FRONTEND_PORT}' != '80' ] && (grep -q FRONTEND_PORT .env && sed -i 's|^FRONTEND_PORT=.*|FRONTEND_PORT={FRONTEND_PORT}|' .env || echo 'FRONTEND_PORT={FRONTEND_PORT}' >> .env) || true
[ '{MCP_PORT}' != '8080' ] && (grep -q MCP_PORT .env && sed -i 's|^MCP_PORT=.*|MCP_PORT={MCP_PORT}|' .env || echo 'MCP_PORT={MCP_PORT}' >> .env) || true
[ '{BACKEND_PORT}' != '8000' ] && (grep -q BACKEND_PORT .env && sed -i 's|^BACKEND_PORT=.*|BACKEND_PORT={BACKEND_PORT}|' .env || echo 'BACKEND_PORT={BACKEND_PORT}' >> .env) || true
[ '{SCHEDULER_PORT}' != '8001' ] && (grep -q SCHEDULER_PORT .env && sed -i 's|^SCHEDULER_PORT=.*|SCHEDULER_PORT={SCHEDULER_PORT}|' .env || echo 'SCHEDULER_PORT={SCHEDULER_PORT}' >> .env) || true
echo 'ports configured'
"
Step 4: Start Trinity
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"cd ~/trinity && sudo ./scripts/deploy/start.sh"
This takes several minutes. Wait for it to complete.
Step 5: Verify health
Wait 30 seconds, then check:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"curl -sf http://localhost:8000/health && echo backend-healthy"
Retry up to 3 times with 15-second delays. If still failing after retries:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"sudo docker logs trinity-backend --tail 30"
Show the logs and ask the user how to proceed.
Display:
## First-Run Setup + MCP API Key
Trinity is running. Complete the first-run setup, then create an API key for the ops agent.
1. Open: http://{SSH_HOST}:{FRONTEND_PORT}
(If unreachable, check your firewall / security group — port {FRONTEND_PORT} must be open.
On a private network? Run ./scripts/tunnel.sh first and use http://localhost:12080)
2. The first visit shows the first-run setup screen (the old setup token is removed, trinity#49):
enter an ADMIN EMAIL (required — it becomes your sign-in identity) and set the admin
password to {ADMIN_PASSWORD}. What you set here is authoritative — it overwrites the
.env-seeded value. Login attempts before setup completes return 403 setup_required.
⚠️ Do this immediately: the pre-setup window is unauthenticated. On an internet-reachable
host, complete setup via the tunnel (./scripts/tunnel.sh) BEFORE opening the firewall.
3. Log in with that admin email (or username admin) + password
4. Go to: Settings → Platform API Keys
5. Click "Create New Key" — copy the value
6. While you're in Settings, add your GitHub token (Settings → GitHub token):
a fine-grained PAT with Contents: Read on the repos your agents live in.
Agents are deployed by cloning their GitHub repo, so this is what makes the
normal deploy path work — required for private repos, recommended for public
ones (it lifts GitHub's anonymous rate limits).
Use AskUserQuestion (tool requires ≥2 options):
MCP_API_KEYMCP_API_KEY="" and note that .env must be updated before using the ops agentSet ports: BACKEND_PORT=8000, FRONTEND_PORT={FRONTEND_PORT}, MCP_PORT={MCP_PORT}, SCHEDULER_PORT=8001
Verify connectivity:
ssh -i {SSH_KEY} -o StrictHostKeyChecking=no {SSH_USER}@{SSH_HOST} \
"curl -sf http://localhost:8000/health && echo healthy"
If port differs from 8000, ask: "What port is the Trinity backend on?" Store as BACKEND_PORT.
Collect:
ADMIN_PASSWORDMCP_API_KEYSet defaults: BACKEND_PORT=8000, FRONTEND_PORT=80, MCP_PORT=8080, SCHEDULER_PORT=8001
Same two options as PATH B.
docker --version
If Docker is missing, display:
Install Docker Desktop: https://www.docker.com/products/docker-desktop
Stop until Docker is available.
Generate secrets:
SECRET_KEY=$(openssl rand -hex 32)
INTERNAL_API_SECRET=$(openssl rand -hex 32)
Ask for ADMIN_PASSWORD (same as PATH B).
Check all required ports before starting:
for p in 80 8000 8001 8080; do
lsof -i ":$p" >/dev/null 2>&1 && echo "IN_USE $p" || echo "FREE $p"
done
For each IN_USE port, use AskUserQuestion (≥2 options) to ask for an alternate — same table as PATH B. Set defaults FRONTEND_PORT=80, MCP_PORT=8080, BACKEND_PORT=8000, SCHEDULER_PORT=8001.
Deploy:
git clone https://github.com/abilityai/trinity ~/trinity
cd ~/trinity && cp .env.example .env
Patch the MCP server Dockerfile healthcheck (upstream bug — /mcp returns 400; /health returns 200):
find ~/trinity -name 'Dockerfile' | xargs grep -l '/mcp' 2>/dev/null | while read f; do
perl -i -pe 's|/mcp|/health|g' "$f" && echo "healthcheck patched: $f"
done
If MCP_PORT is not 8080, also patch the hardcoded port and update docker-compose:
find ~/trinity -name 'Dockerfile' | xargs grep -l '8080' 2>/dev/null | while read f; do
perl -i -pe "s/EXPOSE 8080/EXPOSE {MCP_PORT}/g; s/ENV MCP_PORT=8080/ENV MCP_PORT={MCP_PORT}/g; s|:8080/health|:{MCP_PORT}/health|g" "$f"
done
# Update docker-compose.yml port mappings for all non-default ports
cd ~/trinity
[ '{FRONTEND_PORT}' != '80' ] && perl -i -pe 's/"80:80"/"{FRONTEND_PORT}:{FRONTEND_PORT}"/g' docker-compose.yml || true
[ '{MCP_PORT}' != '8080' ] && perl -i -pe 's/"8080:8080"/"{MCP_PORT}:{MCP_PORT}"/g' docker-compose.yml || true
[ '{BACKEND_PORT}' != '8000' ] && perl -i -pe 's/"8000:8000"/"{BACKEND_PORT}:{BACKEND_PORT}"/g' docker-compose.yml || true
[ '{SCHEDULER_PORT}' != '8001' ] && perl -i -pe 's/"8001:8001"/"{SCHEDULER_PORT}:{SCHEDULER_PORT}"/g' docker-compose.yml || true
Configure .env — use perl -i -pe for cross-platform compatibility (sed -i requires a backup suffix on macOS):
cd ~/trinity
perl -i -pe 's|^SECRET_KEY=.*|SECRET_KEY={SECRET_KEY}|' .env
perl -i -pe 's|^INTERNAL_API_SECRET=.*|INTERNAL_API_SECRET={INTERNAL_API_SECRET}|' .env
perl -i -pe 's|^ADMIN_PASSWORD=.*|ADMIN_PASSWORD={ADMIN_PASSWORD}|' .env
[ '{FRONTEND_PORT}' != '80' ] && (grep -q FRONTEND_PORT .env && perl -i -pe 's|^FRONTEND_PORT=.*|FRONTEND_PORT={FRONTEND_PORT}|' .env || echo 'FRONTEND_PORT={FRONTEND_PORT}' >> .env) || true
[ '{MCP_PORT}' != '8080' ] && (grep -q MCP_PORT .env && perl -i -pe 's|^MCP_PORT=.*|MCP_PORT={MCP_PORT}|' .env || echo 'MCP_PORT={MCP_PORT}' >> .env) || true
[ '{BACKEND_PORT}' != '8000' ] && (grep -q BACKEND_PORT .env && perl -i -pe 's|^BACKEND_PORT=.*|BACKEND_PORT={BACKEND_PORT}|' .env || echo 'BACKEND_PORT={BACKEND_PORT}' >> .env) || true
[ '{SCHEDULER_PORT}' != '8001' ] && (grep -q SCHEDULER_PORT .env && perl -i -pe 's|^SCHEDULER_PORT=.*|SCHEDULER_PORT={SCHEDULER_PORT}|' .env || echo 'SCHEDULER_PORT={SCHEDULER_PORT}' >> .env) || true
Start:
cd ~/trinity && ./scripts/deploy/start.sh
Verify:
curl -sf http://localhost:8000/health && echo healthy
Open http://localhost:{FRONTEND_PORT}/ — the first visit shows the first-run setup screen: enter an admin email + the admin password (same rules and same authority as PATH B; the setup token is gone). Then Settings → Platform API Keys → create and copy the MCP key. Add your GitHub token too (Settings → GitHub token — fine-grained PAT, Contents: Read): agents deploy by cloning their GitHub repo, so private-repo agents need it.
Set SSH_HOST="" (empty — local, no SSH).
curl -sf http://localhost:8000/health
Ask for ADMIN_PASSWORD and MCP_API_KEY. Set SSH_HOST="".
Use AskUserQuestion to collect:
Instance Name:
production, my-company, dev)"{INSTANCE_NAME}-opsINSTANCE_NAMEDestination:
~/{INSTANCE_NAME}-ops (recommended)~ to $HOMEDESTAnthropic API Key (optional but recommended):
ANTHROPIC_API_KEYANTHROPIC_API_KEY=""ANTHROPIC_API_KEYContact email (optional):
CONTACT_EMAIL (may be blank)Compute today's date:
date +%Y-%m-%d
Store as TODAY.
Clone the trinity-ops-public repository into {DEST}:
git clone https://github.com/abilityai/trinity-ops-public {DEST}
If git is not installed locally, display: Install git: https://git-scm.com/downloads and stop.
If the destination already exists, warn and offer to pick a different path.
Copy .env.example to .env:
cp {DEST}/.env.example {DEST}/.env
Configure credentials — use perl -i -pe for cross-platform compatibility:
For remote SSH:
perl -i -pe 's|^SSH_HOST=.*|SSH_HOST={SSH_HOST}|' {DEST}/.env
perl -i -pe 's|^SSH_USER=.*|SSH_USER={SSH_USER}|' {DEST}/.env
perl -i -pe 's|^SSH_KEY=.*|SSH_KEY={SSH_KEY}|' {DEST}/.env
For all paths:
perl -i -pe 's|^ADMIN_PASSWORD=.*|ADMIN_PASSWORD={ADMIN_PASSWORD}|' {DEST}/.env
perl -i -pe 's|^MCP_API_KEY=.*|MCP_API_KEY={MCP_API_KEY}|' {DEST}/.env
[ -n "{ANTHROPIC_API_KEY}" ] && perl -i -pe 's|^ANTHROPIC_API_KEY=.*|ANTHROPIC_API_KEY={ANTHROPIC_API_KEY}|' {DEST}/.env || true
For any non-default ports:
[ '{FRONTEND_PORT}' != '80' ] && perl -i -pe 's|^FRONTEND_PORT=.*|FRONTEND_PORT={FRONTEND_PORT}|' {DEST}/.env || true
[ '{MCP_PORT}' != '8080' ] && perl -i -pe 's|^MCP_PORT=.*|MCP_PORT={MCP_PORT}|' {DEST}/.env || true
[ '{BACKEND_PORT}' != '8000' ] && perl -i -pe 's|^BACKEND_PORT=.*|BACKEND_PORT={BACKEND_PORT}|' {DEST}/.env || true
[ '{SCHEDULER_PORT}' != '8001' ] && perl -i -pe 's|^SCHEDULER_PORT=.*|SCHEDULER_PORT={SCHEDULER_PORT}|' {DEST}/.env || true
For local Docker (no SSH): leave SSH_HOST empty (the .env.example default).
Write {DEST}/instance.yaml:
instance:
name: {INSTANCE_NAME}
contact: {CONTACT_EMAIL}
status: active
host:
address: {SSH_HOST}
user: {SSH_USER}
key: {SSH_KEY}
trinity:
version: latest
branch: main
path: ~/trinity
ports:
frontend: {FRONTEND_PORT}
backend: {BACKEND_PORT}
mcp: {MCP_PORT}
scheduler: {SCHEDULER_PORT}
created_at: {TODAY}
notes: []
For local Docker: set host.address: localhost and omit user and key.
Make scripts executable:
chmod +x {DEST}/scripts/*.sh
Run a quick status check to verify the connection works from the new agent:
source {DEST}/.env && {DEST}/scripts/status.sh
Display:
## Trinity Ops Agent Ready
Instance: {INSTANCE_NAME}
Agent: {DEST}
### Open the agent
cd {DEST}
claude
### Skills available
/status — health check all services
/restart — restart Trinity services
/update — pull latest Trinity + rebuild
/logs — view service logs
/agents — list and manage agent containers
/cleanup — prune unused Docker images and resources
/diagnose — run a deep diagnostic sweep
/rebuild-agent — rebuild a specific agent container
/rollback — roll back Trinity to a previous version
/telemetry — view aggregated logs and metrics
/provision — provisioning guides for cloud providers
### Access Trinity
Web UI: http://{SSH_HOST}:{FRONTEND_PORT}
Backend: http://{SSH_HOST}:{BACKEND_PORT}
MCP Server: http://{SSH_HOST}:{MCP_PORT}
Credentials are in {DEST}/.env — keep this file secret.
| Situation | Action |
|---|---|
| SSH connection fails | Show error, ask to verify host/user/key |
| Docker not found on server | Show install command for their OS |
| Port 80 taken | Ask for alternate port (suggest 8090) |
| Deployment times out | Show sudo docker logs trinity-backend --tail 30 |
| Health check fails after deploy | Show backend logs, offer to retry |
| Destination already exists | Warn, offer to pick a different path |
git clone fails | Check network connectivity and git installation |
| Trinity already running at wrong port | Ask for actual backend port before collecting credentials |