Every Agent, One Graph
Claude Code, Codex, OpenCode, Cursor, and the agents you build share one durable knowledge graph. Tell one tool your context; every tool keeps it.
One self-hostable knowledge graph, shared across Claude Code, Codex, OpenCode, Cursor, and the agents you build. If it runs a shell command, it speaks Sibyl.
Every app wants to remember you now. Your assistant imports your history from the last one, builds a profile, and turns the context you generate into someone else's asset. And none of it travels: what you taught Claude Code, Cursor never sees, so you re-explain the same project to every tool you use. The question stopped being whether your tools remember and became who the memory works for.
Sibyl is cross-agent memory where the answer is you. A knowledge graph, memory loop, and task workflow shared across every coding agent you use, self-hosted on your own hardware so the memory works for you and stays yours:
context → act → remember → reflect, built into every surfaceflowchart TD
W["Your Actual Workflow<br/>Claude Code · Editors · Scripts · Teammates"]
S["Skills<br/>Teach the workflow"]
H["Hooks<br/>Inject context"]
C["CLI<br/>Express power"]
SRV{{"Sibyl Server<br/>SurrealDB graph · Semantic search · Memory loop · Tasks"}}
UI["Web UI<br/>Human collaboration · Memory workspace · Graph explorer"]
W --> S & H & C
S & H & C --> SRV
SRV --> UISkills teach your tools and teammates structured workflows:
# Load context before implementing
sibyl context "authentication work" --intent build
# Track work with full lifecycle
sibyl task start task_xyz
# Capture learnings when done
sibyl task complete task_xyz --learnings "OAuth tokens need refresh..."Hooks automatically inject relevant knowledge into every prompt so useful context shows up before you have to go looking for it.
Web UI for collaboration and oversight:
CLI for power users and scripting:
# Start a local daemon
sibyl init --local
sibyl serve
# Capture a learning
sibyl remember "Redis insight" "Pool size must be >= concurrent requests" --kind rule
# Load it as working context
sibyl context "redis connection pool"
# Manage tasks
sibyl task list --status doing
sibyl task complete <task_id> --learnings "OAuth tokens expire after 1 hour"Sibyl is built around a durable cycle that both humans and agents follow:
flowchart LR
R(["CONTEXT<br/>Pull working context before you act"])
A(["ACT<br/>Do the work with context in hand"])
M(["REMEMBER + REFLECT<br/>Capture learnings, distill session notes"])
R --> A --> M
M -.->|the graph gets smarter| REvery completed task makes your knowledge graph smarter. Every pattern discovered helps future sessions move faster. The system learns as you work.
| Without Sibyl | With Sibyl |
|---|---|
| Agent rediscovers same solutions | Agent recalls existing patterns instantly |
| Memory trapped in one tool | Portable memory you own |
| Manual prompting required | Hooks inject context automatically |
| No task tracking | Full lifecycle with learnings capture |
| Scattered documentation | Searchable, connected knowledge graph |
Built for projects that deserve to remember.