by zylos-ai
Give your AI a life — open-source infrastructure for persistent, self-maintaining AI companions. Powered by Claude Code.
# Add to your Claude Code skills
git clone https://github.com/zylos-ai/zylos-corePowered by Claude Code
Claude Code is a genius — but it wakes up with amnesia every session. No memory of yesterday, no way to reach you, no ability to act on its own.
Zylos gives it a life. Memory that survives restarts. A scheduler that works while you sleep. Communication through Telegram, Lark, or a web console. Self-maintenance that keeps everything running. And because Claude Code can program, it can evolve — building new skills, integrating new services, growing alongside you.
Prerequisites: Git, Node.js >= 20 (via nvm recommended), a Linux server (or Mac), and a Claude subscription.
Why nvm? Installing Node.js via nvm avoids permission issues with
npm install -g. System-level Node.js (from apt/yum) requiressudofor global installs, which can cause problems.
# Install (--install-links required for GitHub install; will be published to npm soon)
npm install -g --install-links https://github.com/zylos-ai/zylos-core
# Initialize — sets up tmux, PM2, memory, scheduler, and more
zylos init
zylos init is interactive and idempotent. It will:
~/zylos/ directory with memory, skills, and servicesTalk to your agent:
# Attach to the Claude session
tmux attach -t claude-main
# Or add a messaging channel
zylos add telegram
zylos add lark
Most agent frameworks isolate sessions per channel — your AI on Telegram doesn't know what you said on Slack. Zylos is agent-centric: your AI is one person across every channel. The C4 communication bridge routes all messages through a single gateway — one conversation, one memory, one personality. Every message persisted to SQLite and fully queryable.
Other frameworks lose your AI's memory during context compaction — silently, without warning. Zylos prevents this with a two-step safeguard: when context reaches 75%, the system automatically saves all memory before compaction runs. Five-layer Inside Out memory (identity → state → references → sessions → archive) ensures the AI always knows what to keep and what to compress. Your AI never wakes up with amnesia.
No third-party monitoring tools needed. Zylos includes native crash recovery, heartbeat liveness probes, health monitoring, context window management, and automatic upgrades — all built in. Your AI detects its own problems and fixes them. It stays alive while you sleep.
Other frameworks charge per API token. Community reports show monthly bills of $500–$3,600 for always-on agents. Zylos runs on your Claude subscription — flat rate, no per-token billing. Same AI capabilities, a fraction of the cost.
Zylos builds on Claude Code — Anthropic's official AI agent runtime. When Anthropic ships new capabilities like agent teams, your AI gets them automatically. And because Claude Code can program, your AI writes new skills, integrates services, and evolves with your needs.
graph TB
subgraph Channels["📡 Communication Channels"]
TG["Telegram"]
LK["Lark"]
WC["Web Console"]
end
subgraph Zylos["🧬 Zylos — The Life System"]
C4["C4 Comm Bridge<br/>(unified gateway · SQLite audit)"]
MEM["Memory<br/>(Inside Out architecture)"]
SCH["Scheduler<br/>(autonomous task dispatch)"]
AM["Activity Monitor<br/>(guardian · heartbeat · auto-recovery)"]
HTTP["HTTP Layer<br/>(Caddy · file sharing · HTTPS)"]
end
subgraph Brain["🧠 Claude Code — The Brain"]
CC["Claude Code<br/>(in tmux session)"]
end
TG & LK & WC --> C4
C4 <--> CC
MEM <--> CC
SCH --> CC
AM --> CC
HTTP <--> CC
| Component | Role | Key Tech | |-----------|------|----------| | C4 Comm Bridge | Unified message gateway with audit trail | SQLite, priority queue | | Memory | Persistent identity and context across restarts | Inside Out tiered architecture | | Scheduler | Autonomous task dispatch while you are away | Cron, NL input, idle-gating | | Activity Monitor | Crash recovery, heartbeat, health checks | PM2, multi-layer protection | | HTTP Layer | Web access, file sharing, component routes | Caddy, auto-HTTPS |
zylos init.Install with one command:
zylos add telegram
zylos add lark
All channels connect through the C4 communication bridge. To add a new channel (Slack, Discord, WhatsApp, etc.), implement the C4 protocol — a simple HTTP interface that pushes messages into the unified gateway. Your custom channel gets the same unified session, audit trail, and memory as every other channel.
zylos init # Set up Zylos environment
zylos status # Check running services
zylos logs [service] # View service logs
zylos add <component> # Install a channel or capability
zylos upgrade <component> # Upgrade a component
zylos list # List installed components
zylos search [keyword] # Search component registry
Zylos is the open-source core of Coco — the AI employee platform.
We built Zylos because we needed it ourselves: a reliable infrastructure to keep AI running 24/7 for real work. Everything in Zylos is battle-tested in production at Coco, serving teams that depend on AI employees every day.
Want a managed experience? Coco gives you a ready-to-work AI employee — with persistent memory, multi-channel communication, and skill packages — deployed in 5 minutes.
No comments yet. Be the first to share your thoughts!