Stop rediscovering the same solutions every session. Sibyl gives your projects persistent memory, semantic search, and durable task context.
Every time you start a new coding session, critical context slips away. That OAuth gotcha you debugged for 2 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 a knowledge graph and task workflow that gives your team:
┌──────────────────────────────────────────────────────────────────┐
│ Your Actual Workflow │
│ Claude Code • Editors • Scripts • Teammates │
└────────────────────────────┬─────────────────────────────────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
▼ ▼ ▼
┌─────────┐ ┌───────────┐ ┌──────────┐
│ Skills │ │ Hooks │ │ CLI │
│ Teach │ │ Inject │ │ Express │
│ workflow│ │ context │ │ power │
└─────────┘ └───────────┘ └──────────┘
│ │ │
└────────────────────┼────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────┐
│ Sibyl Server │
│ Knowledge Graph (FalkorDB) • Semantic Search • Task Management │
└──────────────────────────────────────────────────────────────────┘
│
▼
┌──────────────────────────────────────────────────────────────────┐
│ Web UI │
│ Human collaboration • Project management • Graph explorer │
└──────────────────────────────────────────────────────────────────┘Skills teach your tools and teammates structured workflows:
# Search before implementing
sibyl search "authentication patterns"
# 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 the infrastructure
sibyld up
# Search your knowledge
sibyl search "authentication patterns"
# Add a learning
sibyl add "Redis insight" "Connection pool must be >= concurrent requests"
# Manage tasks
sibyl task list --status doing
sibyl task complete <task_id> --learnings "OAuth tokens expire after 1 hour"Sibyl enforces a simple cycle:
┌─────────────────────────────────────────────────────┐
│ 1. RESEARCH │
│ Search for existing patterns before coding │
│ sibyl search "what you're implementing" │
└─────────────────────────┬───────────────────────────┘
▼
┌─────────────────────────────────────────────────────┐
│ 2. DO │
│ Work on your task with context from search │
│ sibyl task start <task_id> │
└─────────────────────────┬───────────────────────────┘
▼
┌─────────────────────────────────────────────────────┐
│ 3. REFLECT │
│ Capture learnings for future sessions │
│ sibyl task complete <task_id> --learnings "..." │
└─────────────────────────────────────────────────────┘Every 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 finds existing patterns instantly |
| Context lost between sessions | Knowledge persists forever |
| 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.