This is an old revision of the document!
Table of Contents
Service map
User manager
The following application units run in isnotreal’s user systemd manager. Observed active states are from 2026-10-25 around 16:20 UTC; they can change during rollout.
| Unit | State | Listener or role |
|---|---|---|
batbox-api.service | active, enabled | 127.0.0.1:8772, issue and communication API |
batbox-engine.service | active, enabled | autonomous engine; no separate listener observed |
batbox-memory.service | active, enabled | 127.0.0.1:8771, local memory and retrieval |
claude-searxng.service | active, enabled | 127.0.0.1:8888, local search |
Unit files are under /home/isnotreal/.config/systemd/user/. The engine unit declares Wants and After dependencies on the Batbox API and memory units.
System manager
| Unit | State | Listener or role |
|---|---|---|
caddy.service | active, enabled | public HTTP 80 and HTTPS 443; local admin endpoint 2019 |
qwen-vllm.service | active, enabled | 127.0.0.1:8001, local model API |
qwen-reasoning-router.service | active, enabled | 127.0.0.1:8003, local reasoning router |
cve-audit-kb.service | active, enabled | 127.0.0.1:8765, REST/MCP service |
ssh.service | active, disabled | port 22 was listening on IPv4 and IPv6 |
System unit files are in /etc/systemd/system/ or /usr/lib/systemd/system/. Port 8000 answered an unauthenticated local request with HTTP 401 and is configured as a credential-gated Caddy route. ss showed *:8000, while the Caddy site address names loopback; verify the actual bind and firewall exposure before treating it as loopback-only. Port 80/443 are Caddy ingress; the model ports 8001 and 8003 are local backends. Do not publish API credentials or copy environment-file contents into the wiki.
Recheck
Use systemctl –user show batbox-api batbox-engine batbox-memory claude-searxng -p Id -p ActiveState -p SubState -p FragmentPath, systemctl show caddy qwen-vllm qwen-reasoning-router cve-audit-kb ssh -p Id -p ActiveState -p SubState -p FragmentPath, and ss -lntup. Omit process IDs from maintained notes: model worker PIDs are transient during rollout. Health checks and source paths are at Local memory service and Startup and recovery checks.