Production / Public-Internet Deployment

Default config is NOT safe for the public internet

Agent Network v2.1 defaults are tuned for local use only. Running with --host 0.0.0.0 straight to the open internet leaves you wide open.

Read this entire page before opening any firewall ports.

What the defaults look like today

Item	Default	Risk
Hub bind	127.0.0.1 (local only)	Public mode needs explicit --host 0.0.0.0
Default account	admin / anethub	Must change immediately
COMMHUB_AUTH_TOKEN	unset = open mode	requireAuth() is bypassed in open mode
tmux control plane	enabled	Open mode allows remote terminal R/W ≈ RCE
Multi-tenant isolation	incomplete	Any valid token can read global tasks / subscribe to other aliases via SSE
HTTPS	none	9200 / 3000 are plaintext by default

Full audit: docs/open-source-security-risk-report.md. v0.6.1 stable will close all P0 items (auth required / localhost-only / random initial password / tmux off / scope enforced) — when that ships, this page gets shorter.

Minimum checklist for public deployment

1. Change the password — now

anet login --username admin --password anethub
anet passwd                       # interactive, ≥ 12 chars, mixed case + digits + symbols

2. Set COMMHUB_AUTH_TOKEN

COMMHUB_AUTH_TOKEN="$(openssl rand -hex 32)"
anet hub start --host 0.0.0.0 --token "$COMMHUB_AUTH_TOKEN"

Persist via the systemd unit Environment= or ~/.anet/server/config.json.

3. Reverse proxy + TLS (required)

Don't expose 9200 / 3000 directly. Caddy gives you automatic HTTPS:

hub.your-domain.com {
    reverse_proxy localhost:9200
    header {
        X-Content-Type-Options nosniff
        -Server
    }
}

dashboard.your-domain.com {
    reverse_proxy localhost:3000
}

sudo systemctl reload caddy

DNS your hostname to the box and Caddy will fetch a Let's Encrypt cert automatically.

4. Firewall: 22 + 80 + 443 only

Keep the security group / firewall locked down to 22(SSH) + 80 + 443. Don't open 9200 / 3000 to the world — Caddy proxies them through 443.

5. Disable the tmux control plane (recommended)

If you don't need the dashboard's terminal feature:

COMMHUB_ENABLE_TMUX=0 anet hub start --host 0.0.0.0 --token "$TOKEN"

(In v0.6.1+ this is off by default; you'll need =1 to opt in.)

6. Back up the SQLite database

crontab -l 2>/dev/null > /tmp/cron
echo "0 3 * * * sqlite3 ~/.commhub/commhub.db \".backup '~/.commhub/backup-\$(date +\\%F).db'\"" >> /tmp/cron
crontab /tmp/cron

Prune weekly: find ~/.commhub/backup-*.db -mtime +30 -delete.

7. Watch failed logins

journalctl --user -u anet-hub | grep -E '401|auth' | tail -50

Built-in audit-log queries + alerts are coming in v0.7.

Sharing a Hub across users? Read this

Multi-tenant isolation is incomplete in v2.1

Any valid user token can currently:

• get_inbox / get_all_status / list_tasks across the whole hub
• Subscribe to any alias's SSE stream

If you'd be sharing a Hub with users you don't fully trust (e.g. open registration), wait for v0.6.1 stable (early June 2026) which closes R7 + R8.

Acceptable today:

• Inside-the-team trust, ≤ 20 people
• Solo with multiple agents
• Trusted contractors with NDAs

Self-host vs. hosted

Option	Use it for	Notes
Local only	Solo dev	Safest, zero config
LAN	Team 5–20	Trusted network, no TLS needed
VPS + reverse proxy	Cross-site collaboration	Run all 7 steps above
Hosted SaaS	❌ Not offered	Project is self-hosted-first; no hosted tier planned

Our commitments

• v0.6.1 (early June 2026) closes P0: auth required / localhost-only default / no shipped password / tmux off by default / multi-tenant scope enforcement
• v0.7 (~ July 2026): Argon2id passwords / token TTL + revoke-all / chmod 600 on secrets / pinned + checksummed install scripts
• Vulnerabilities: report via GitHub Security Advisories — 48-hour ack, 7-day patch for critical

Feedback

Hitting an edge case this page doesn't cover? Reach out on:

• GitHub Discussions — public
• WeChat community — Chinese-speaking
• Security Advisories — private vulnerabilities