Own your context.
1Context is a local memory layer for people who work with AI agents. It turns desktop files and work activity into a private personal wiki, then gives agents like Claude Code and Codex a stable place to read what matters about you, your projects, and how you like to work.
AI assistants are powerful, but they forget the shape of your work. You repeat preferences, project history, decisions, caveats, and "please do it this way" instructions over and over.
1Context is meant to become the long-term memory that sits beside those agents. Instead of hiding memory in one chat product, it keeps memory in a wiki you can open, inspect, edit, and share later when you choose.
The product direction is simple:
- Your computer keeps a private record of useful context.
- A small group of Open Claw-style agents work together like careful Wikipedia editors.
- They propose and organize memories before changing the readable pages.
- Claude, Codex, and future agents can read the same wiki instead of each keeping their own scattered memory.
This public preview is early, but the app shell is real and polished:
- a signed macOS menu bar app
- a private local wiki served in your browser
- polished default pages, even before you have much content
- user-owned local content under
~/1Context/as it is created - no product telemetry and no upload of project data in this preview
Memory collection and memory writing are still manual in this release. The automatic screen activity pipeline, passive remembering, and multi-agent wiki editing system are in active development. Today, 1Context is best understood as the polished public shell plus the first local wiki path.
1Context uses the wiki as the meeting place between you and your agents.
The readable article pages are calm and current. Talk pages keep the reasoning: questions, proposed updates, evidence, curator notes, and agent instructions. That gives the system a place to think before it rewrites what future agents will read.
Under the hood, the public app keeps the sturdy macOS parts small and explicit. The menu bar owns the user experience, the local web server, updates, setup, and diagnostics; future memory publication can plug into that app-owned boundary without shipping a source checkout inside the app.
Requires Apple Silicon and macOS 13 Ventura or newer.
Download the latest 1Context.dmg from
GitHub Releases,
open it, and either drag 1Context.app to /Applications or launch it and
choose Install and Open.
First launch opens 1Context Setup. Grant Local Wiki Access once, then use the menu bar item to open or refresh your wiki.
Homebrew users can install the same signed app with:
brew install --cask hapticasensorics/tap/1contextThe cask installs 1Context.app in /Applications, links the 1context
support command, and leaves app updates to the signed in-app updater.
Support commands are available through the bundled CLI:
/Applications/1Context.app/Contents/MacOS/1context-cli status
/Applications/1Context.app/Contents/MacOS/1context-cli diagnose
/Applications/1Context.app/Contents/MacOS/1context-cli setup local-web status
/Applications/1Context.app/Contents/MacOS/1context-cli wiki local-urlUninstall the app:
From the menu bar, choose Settings > Uninstall 1Context..., or use the support
CLI:
/Applications/1Context.app/Contents/MacOS/1context-cli uninstall
/Applications/1Context.app/Contents/MacOS/1context-cli uninstall --delete-dataMoving the app to the Trash removes the app bundle. The app-owned uninstall path
also removes 1Context background items and local HTTPS trust while preserving
~/1Context unless you choose --delete-data.
1Context keeps user-owned content and app machinery separate:
~/1Context/
user-created wiki files and user-owned content
~/Library/Application Support/1Context/
app/runtime state, config, indexes, shipped wiki shell, and local web state
~/Library/Logs/1Context/
logs and debug/support information
~/Library/Caches/1Context/
disposable cache, safe to delete
The public preview makes no product telemetry calls and does not upload project data. App update checks are app-owned and use the signed Sparkle release feed.
See PERMISSIONS.md for the ownership, consent, and privacy contract.
This is a founder preview, not a finished memory product:
- Memory collection and page creation are currently manual.
- Local chat/librarian execution is not shipped in the app yet.
- Cloud wiki sharing is not enabled yet.
- The local wiki is private.
The design intentionally keeps the browser contract cloud-compatible: local
today, cloud later, same wiki pages and /api/wiki/* shape.
Maintainer and contract details live in:
Thanks to Karpathy for llm-wiki.
Apache-2.0. Copyright Aurem, Inc.



