Search sessions, commands, diffs, and debugging context locally
Locality gives Codex users a private project memory workspace for searchable sessions, commands, diffs, decisions, and debugging context.
Start for free
Built around local-first developer workflows
Keep every agent handoff searchable
Locality keeps the reason behind changes, the commands that worked, and the debugging history your next Codex session should not have to rediscover.
Bring coding history into Locality in minutes
Install the CLI, sign in once, and import the sessions that matter. Locality turns AI coding work into readable project memory without changing your editor.
Install and import your history
Connect this device, bring in recent sessions, and keep private project memory on infrastructure you control.
Search the decision, command, or diff
Recover why a file moved, which prompt worked, and what changed before you reopen the same debugging path.
Connect more tools without losing context.
Use one local memory across Codex, Claude Code, Cursor, Copilot, Obsidian, and local or cloud models.
Open chatAsk memory
Add tools around one memory layer
Keep imports, dashboards, vault notes, and AI chat connected to the same project memory instead of scattering context.
Carry context across every agent
Switch editors, models, and machines without starting from zero every time a new tool joins the workflow.
Keep memory local. Ask better questions.
Locality turns prior sessions into durable project memory, keeps it readable in your vault, and lets you search commands, diffs, and context from one dashboard.
Built for developers who use agents every day
From solo builders to small teams, Locality keeps architecture decisions, fixes, prompts, and debugging context available after the chat window is gone.
Readable notes, not locked context
Locality writes ordinary Markdown into memory you own, so the result stays portable across tools and understandable outside one UI.
One workflow across editors and models
Keep the same project memory available whether the work happened in Codex, Claude Code, Cursor, Copilot, or a local model.
Setup. Import. Remember.
Keep the context from every coding session without changing how you build.
Ask memory
Ask memory
Install and connect Locality
Sign in once, activate the CLI, and choose the vault or local setup that will hold your project memory.
Ask memory
Choose the history to import
Review detected coding-agent sessions and import only the projects you want to preserve for later search and chat.
Ask memory
Search or ask your local memory
Browse readable notes in your vault or ask the Locality dashboard what changed, which commands worked, and why.
Install and connect Locality
Sign in once, activate the CLI, and choose the vault or local setup that will hold your project memory.
Choose the history to import
Review detected coding-agent sessions and import only the projects you want to preserve for later search and chat.
Search or ask your local memory
Browse readable notes in your vault or ask the Locality dashboard what changed, which commands worked, and why.
What Locality is built to preserve
These are the kinds of context Locality keeps available after the chat window closes. They describe workflows, not customer endorsements.
Keep the reasoning behind a schema change, refactor, or rollback so the next agent session can start with context instead of guesses.
Decision history
Locality workflow
Recover the exact terminal commands and follow-up fixes that solved a problem last time instead of rebuilding the path from memory.
Command recall
Locality workflow
Keep imported sessions and vault-backed notes in a local workflow that stays readable outside a hosted chat product.
Private notes
Locality workflow
Move between local models and connected providers while keeping the same project memory attached to the work.
Model switching
Locality workflow
Keep the reasoning behind a schema change, refactor, or rollback so the next agent session can start with context instead of guesses.
Decision history
Locality workflow
Recover the exact terminal commands and follow-up fixes that solved a problem last time instead of rebuilding the path from memory.
Command recall
Locality workflow
Keep imported sessions and vault-backed notes in a local workflow that stays readable outside a hosted chat product.
Private notes
Locality workflow
Move between local models and connected providers while keeping the same project memory attached to the work.
Model switching
Locality workflow
Keep the reasoning behind a schema change, refactor, or rollback so the next agent session can start with context instead of guesses.
Decision history
Locality workflow
Recover the exact terminal commands and follow-up fixes that solved a problem last time instead of rebuilding the path from memory.
Command recall
Locality workflow
Keep imported sessions and vault-backed notes in a local workflow that stays readable outside a hosted chat product.
Private notes
Locality workflow
Move between local models and connected providers while keeping the same project memory attached to the work.
Model switching
Locality workflow
Keep the reasoning behind a schema change, refactor, or rollback so the next agent session can start with context instead of guesses.
Decision history
Locality workflow
Recover the exact terminal commands and follow-up fixes that solved a problem last time instead of rebuilding the path from memory.
Command recall
Locality workflow
Keep imported sessions and vault-backed notes in a local workflow that stays readable outside a hosted chat product.
Private notes
Locality workflow
Move between local models and connected providers while keeping the same project memory attached to the work.
Model switching
Locality workflow
Pull recent coding-agent sessions into one searchable place so new work can start from prior attempts and known outcomes.
Session imports
Locality workflow
Write durable project memory into an Obsidian vault so the archive remains yours, portable, and easy to inspect in plain Markdown.
Obsidian sync
Locality workflow
Authorize more than one machine and keep imported memory available wherever your day-to-day coding actually happens.
Multi-device setup
Locality workflow
Ask what changed, why a file moved, which command worked, or which earlier decision shaped the current implementation.
Ask memory
Locality workflow
Pull recent coding-agent sessions into one searchable place so new work can start from prior attempts and known outcomes.
Session imports
Locality workflow
Write durable project memory into an Obsidian vault so the archive remains yours, portable, and easy to inspect in plain Markdown.
Obsidian sync
Locality workflow
Authorize more than one machine and keep imported memory available wherever your day-to-day coding actually happens.
Multi-device setup
Locality workflow
Ask what changed, why a file moved, which command worked, or which earlier decision shaped the current implementation.
Ask memory
Locality workflow
Pull recent coding-agent sessions into one searchable place so new work can start from prior attempts and known outcomes.
Session imports
Locality workflow
Write durable project memory into an Obsidian vault so the archive remains yours, portable, and easy to inspect in plain Markdown.
Obsidian sync
Locality workflow
Authorize more than one machine and keep imported memory available wherever your day-to-day coding actually happens.
Multi-device setup
Locality workflow
Ask what changed, why a file moved, which command worked, or which earlier decision shaped the current implementation.
Ask memory
Locality workflow
Pull recent coding-agent sessions into one searchable place so new work can start from prior attempts and known outcomes.
Session imports
Locality workflow
Write durable project memory into an Obsidian vault so the archive remains yours, portable, and easy to inspect in plain Markdown.
Obsidian sync
Locality workflow
Authorize more than one machine and keep imported memory available wherever your day-to-day coding actually happens.
Multi-device setup
Locality workflow
Ask what changed, why a file moved, which command worked, or which earlier decision shaped the current implementation.
Ask memory
Locality workflow
Start free. Remember more. Scale clean.
The Codex importer is free. Upgrade when durable, multi-tool memory becomes part of your daily workflow.
GoPopular
For developers using agents every day.
Everything in Free +
- Unlimited history
- Codex, Claude Code, Cursor and Copilot
- Automatic imports
- Web and Obsidian Local AI chat
- Ollama, OpenAI and Claude
Plus
A connected memory layer across your whole setup.
Everything in Go +
- Everything in Go
- Multiple devices and vaults
- Advanced semantic indexing
- Team-ready export
- Priority releases
Get Started today:
- Latest 10 imported chats
- Up to 50 turns per chat
- Codex importer
- Manual imports
- Local Obsidian notes
Frequently Asked Questions
Answers to common questions about Locality, local-first project memory, imports, and private AI chat.
Keep your next agent session grounded with Locality
Your project already has a history. Turn it into private, durable memory before the next bug, refactor, or handoff starts cold.