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 time you start a new coding session, critical context slips away. That OAuth gotcha you debugged for two hours? Gone. The pattern that finally made your tests pass? Vanished. The configuration quirk that took forever to figure out? Lost to the void.
Sibyl is cross-agent memory. A knowledge graph, memory loop, and task workflow shared across every coding agent you use:
recall → 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:
# Recall context before implementing
sibyl recall "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 pattern
# Recall it as working context
sibyl recall "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(["RECALL<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 |
| Context lost between sessions | Knowledge persists in a graph |
| 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.