a ridge on the cerebral cortex
Claude Code. Codex. Cowork. Antigravity.
None of them remember the others.
You make decisions in one tool, build in another, brainstorm in a third.
Gyrus reads all of them and builds one knowledge base. Plain markdown, editable, local-first.
curl -fsSL https://gyrus.sh/install | bash
One command. Bring your own API key. macOS, Linux & Windows.
Run the install. Gyrus scans your sessions, extracts insights, and merges them into project wikis — automatically.
Found: 51 cowork, 33 claude-code, 53 codex, 132 antigravity Cost estimate: ~$4.11 | Time estimate: ~14 minutes [1/269] claude-code kidworthy — 5 thoughts [2/269] cowork recallalert — 8 thoughts [3/269] codex chartlite — 4 thoughts [4/269] antigravity instantfashion — 11 thoughts Merging 115 thoughts into 'recallalert'... ✓ Updated 'recallalert' v1 Merging 271 thoughts into 'instantfashion'... ✓ Updated 'instantfashion' v1 Done. 269 sessions, 1226 thoughts, 31 project pages. Cost: ~$4.88 | LLM calls: 266 extract, 32 merge_
What a project page looks like
Consumer app aggregating product recalls from CPSC, FDA, and USDA into a personalized feed. iOS (SwiftUI) and Android (Expo/React Native) sharing the same Supabase backend. Privacy-first: all user data on-device, only anonymous push tokens stored remotely.
Built from 115 thoughts across claude-code, cowork, codex, and antigravity sessions spanning Dec 2025 – Apr 2026
Reads Claude Code, Cowork, Codex, and Antigravity sessions from the same machine. Groups by workspace so a Cowork architecture session and a Claude Code build session end up on the same project page.
An LLM you choose picks out decisions, status changes, and project context. Not code diffs or terminal output.
New insights merge into existing wiki pages. You can edit pages by hand anytime — your edits are preserved.
Supported tools
A cron job checks for new sessions on your schedule. No new sessions = no API calls = zero cost. Review your pages periodically — they're drafts, not gospel.
The installer sets up a cron job (or Windows Scheduled Task) at whatever frequency you choose — every 30 minutes, hourly, every 4 hours, or daily. Each run checks for new sessions since the last one. If nothing changed, it exits immediately. No LLM calls, no cost.
Gyrus installs a /gyrus slash command into Claude Code and instruction files for Codex. Your AI tools can query the knowledge base mid-session — context flows both ways.
When there are new sessions: ~$0.01–0.04 per run • Frequency is configurable during install • Self-updates with python3 ingest.py --update
Monday you architect in Cowork. Tuesday you build in Claude Code. Wednesday you debug in Codex. Thursday you refactor in Antigravity. By Friday, none of them know what happened in the others.
What Gyrus captures
What it skips
Each run adds new context. Pages get more useful as you work, but they're LLM-maintained — review them like you'd review a junior's draft.
Week 1
"Beacon is a SaaS analytics dashboard"
Week 2
"Beacon targets early-stage startups, using ClickHouse for real-time queries"
Week 3
"Beacon's moat is sub-second latency + Stripe-native cohort analysis"
Week 4
"Beacon needs YC demo by April 1. Ship churn predictor or cut scope."
Pages work best for: project status, key decisions, timeline, next steps. They're weaker for precise architecture docs or exact dependency versions — review and edit as needed.
Gyrus runs on your machine. You pay your LLM provider directly. No accounts, no cloud, no middleman.
Thought extraction
~$0.01/session
Haiku, GPT-5.4-nano, Gemini Flash
Knowledge merging
~$0.05/page update
Sonnet, GPT-5.4, Gemini Pro
Typical monthly cost
$5-15
Cloud accounts needed
Zero
Run --compare-models to benchmark models on your own sessions and pick one. Supports Anthropic, OpenAI, and Google models. Swap anytime.
Working patterns and cross-cutting decisions go into ~/.gyrus/me.md. Ideas and brainstorms go into ideas.md. You can review project statuses in status.md and edit them by hand.
Gyrus stores everything as plain markdown in ~/.gyrus/. Sync however you want:
iCloud / Dropbox / Google Drive
Point ~/.gyrus/ to a synced folder
Git
cd ~/.gyrus && git init
Obsidian
Set your vault path to ~/.gyrus/
Notion
Optional adapter via --storage=notion
Run the installer on each machine. Same knowledge base, everywhere.
Good fit
Less useful for
Different approach. Mem0 and OpenMemory store facts as vector embeddings in a database. They're designed as memory APIs for AI apps.
Gyrus produces editable markdown wiki pages organized by project. You can read them, edit them, sync them with any tool. The output is structured documents, not database rows.
Those are static files you write and maintain by hand, scoped to a single repo. Gyrus extracts knowledge from your actual sessions across all your projects and tools automatically. They're complementary — AGENTS.md tells the AI how to behave, Gyrus captures what you've decided and built.
Gyrus currently supports Claude Code, Claude Cowork, OpenAI Codex, and Google Antigravity. More tools added on request — each one just needs a session reader (~30 lines of Python). Contributions welcome.
Gyrus runs entirely on your machine by default. Sessions are sent to your chosen LLM API for extraction (same as using any AI tool), but your knowledge base stays local as plain markdown files. Nothing is stored in any cloud unless you opt in — you can choose to sync via iCloud, Dropbox, Notion, or Git if you want cross-machine access.
Yes, and you should. Pages are LLM-maintained drafts — they can be subtly wrong or overgeneralized. Edit them in any text editor. Gyrus preserves your manual edits during the next merge. You can also set project statuses in status.md.
Three commands: remove the cron job (crontab -l | grep -v ingest.py | crontab -), remove the Claude Code skill (rm ~/.claude/commands/gyrus.md), and delete the directory (rm -rf ~/.gyrus). Back up your knowledge base first if you want to keep it.
Takes 2 minutes. You'll see what it finds.
curl -fsSL https://gyrus.sh/install | bash