메뉴
Caddy-based web server providing web console hosting, file sharing, and health check endpoints. Use when configuring HTTP access, setting up file sharing, or troubleshooting web connectivity.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Guardian service that monitors the active runtime agent's state and automatically restarts it if stopped. Use when checking agent liveness state or understanding the auto-restart mechanism.
Built-in web interface for communicating with Claude without external services. Use when setting up or configuring the web console channel, or troubleshooting browser-based access.
Core memory system. Maintains persistent memory across sessions via tiered markdown files following the Inside Out model. Handles Memory Sync (processing conversations into structured memory), session rotation, consolidation, and context-aware state saving. Must be launched via a runtime-appropriate background subagent mechanism — do not invoke with the Skill tool.
C4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.
Guidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.
Start a new session when context is high. Claude uses /clear, Codex uses /exit. Use when context is high or when a fresh session is needed.
| name | http |
| description | Caddy-based web server providing web console hosting, file sharing, and health check endpoints. Use when configuring HTTP access, setting up file sharing, or troubleshooting web connectivity. |
User-space Caddy web server providing:
~/zylos/http/public/zylos add)| Component | Path |
|---|---|
| Binary | ~/zylos/bin/caddy |
| Caddyfile | ~/zylos/http/Caddyfile |
| Public files | ~/zylos/http/public/ |
| Access log | ~/zylos/http/caddy-access.log |
| Domain config | ~/zylos/.zylos/config.json |
Caddy runs as a PM2 service (user-space, no sudo needed for daily operations).
Caddy is set up automatically during zylos init:
~/zylos/bin/caddyconfig.jsonsetcap, one-time sudo)To re-run setup: zylos init
| Path | Description |
|---|---|
/ | File listing or index.html |
/*.md | Markdown documents (served as plain text) |
Place files in ~/zylos/http/public/ to share:
cp document.md ~/zylos/http/public/
# Access at: https://your.domain.com/document.md
Components declare http_routes in SKILL.md frontmatter. Routes are auto-managed via marker blocks in the Caddyfile by zylos add/upgrade/remove.
# Check Caddy status
pm2 logs caddy
# Validate Caddyfile
~/zylos/bin/caddy validate --config ~/zylos/http/Caddyfile --adapter caddyfile
# Reload after manual Caddyfile edits
pm2 reload caddy
# Access logs
tail -f ~/zylos/http/caddy-access.log
On Linux, Caddy needs CAP_NET_BIND_SERVICE to bind ports 80/443:
sudo setcap cap_net_bind_service=+ep ~/zylos/bin/caddy
This is set automatically during zylos init. If the binary is replaced (e.g., after an update), re-run the command above.