By name: gyrus description: Query the Gyrus knowledge base. Trigger with "check gyrus", "what did I decide about", "has this been explored", "what do we know about", or when you need context from previous AI sessions.
Gyrus — Knowledge Base
Gyrus is a knowledge base built automatically from all your AI tool sessions (Claude Code, Claude Cowork, Codex, Cursor, Copilot, and more). It lives as local markdown files in ~/.gyrus/.
How to read
The knowledge base is plain markdown files. Read them directly:
~/.gyrus/projects/— one wiki page per project~/.gyrus/status.md— overview of all projects~/.gyrus/me.md— personal memory (working patterns, preferences)~/.gyrus/cross-cutting.md— insights that span multiple projects
Each project page contains: status, overview, key decisions, open questions, connections to other projects, and recent activity.
Export to connected services
When the user says "push to [service]", "export to [service]", or "sync to [service]", check which connectors/MCP tools are available and use them to export Gyrus project pages.
- Read the project page(s):
~/.gyrus/projects/*.md - Detect which relevant connector tools are available to you
- Create/update content in the target service — e.g. one Notion page or Google Doc per project, project decisions as Linear/Jira issues, digests as Slack messages, wiki pages via GitHub
If the target service isn't connected, suggest connecting it first (Settings → Connectors). For "export everything", iterate over all files in ~/.gyrus/projects/ and report what was exported.
When to use
- Before starting strategic work: read the project page for context
- When the user asks "what did I decide about X?" or "has this been explored?"
- When you notice cross-project connections worth surfacing
- When the user says "gyrus" or "check gyrus" or "what do we know about"
- When the user says "push to [service]" or "export to [service]" → export via connectors
Guidelines
- Present results as concise summaries, not raw file contents
- Highlight key decisions, open questions, and recent activity
- Note when information might be stale (check dates)
- Don't modify the files — Gyrus manages them automatically
- For exports: confirm the target and scope before pushing (one project vs all)