Docs

Context & Sessions

How FlyDocs manages project context, session continuity, and a knowledge base that carries decisions forward between conversations.

FlyDocs gives your AI tools persistent, structured context that carries forward between sessions.

Project context

flydocs/context/project.md is the foundation: your project's scope, stack, conventions, and current priorities. Generated during install, refined during setup, and loaded before every prompt via the context injection hook.

Context graph

The context graph tracks relationships between skills, decisions, sessions, issues, and project knowledge. It's not a flat file; it understands how things connect. When you start a new session, the AI doesn't just know what happened yesterday. It knows how yesterday's decisions relate to today's work.

Relationship Graph

SESSION
Yesterday's work
RELATES_TO →
DECISION
ADR-001
↓ INFORMS
SKILL
TypeScript patterns
← GUIDES
ISSUE
Today's work

Session continuity

Every session starts where the last one ended:

  • /start-session loads active issues, recent progress, and project context
  • /wrap-session captures what happened, decisions made, and next steps
  • The context graph stores it all so nothing gets lost between conversations

Knowledge base

flydocs/knowledge/ is a growing repository of decisions, notes, and project documentation (ADRs, technical discoveries, feature docs). Anything worth remembering goes here. The AI consults it when making decisions, so institutional knowledge compounds over time instead of resetting every session.

Coming soon: cross-session intelligence

Today, context carries forward within a single project. We're building cross-session intelligence so context compounds across your whole team. Decisions made in one session inform the next, across projects and contributors. Coming with the cloud tier.

Join the Discord for upcoming features, support, and early access to what's next.

Next