statusLABSCO SUMMARY
Memory you can open in a text editor.
The architectural bet is that no model belongs in the write path: ingestion and recall are deterministic, agents propose and you approve, and every memory is a Markdown file you can grep or delete by hand. That also means the useful failure mode is legible — a weak or semantic-only match comes back labelled as such, so the agent asks instead of asserting.
What it is
A memory layer that several agents share. Raw notes, transcripts and docs become an inspectable Markdown wiki; explicit "remember this" requests become reviewable memories; agents retrieve compact, source-backed packets through the CLI, MCP, skills or a local viewer rather than dumping the wiki into a chat window.
What you get
- Readiness, schema state, validation and safe next actions before anything is written —
status - The single read path — startup briefs, answer-ready packets, wiki search, graph context and follow-up actions, each memory carrying a confidence label of
strong,moderateorweakand a match type oflexical,semanticorhybrid—recall - Durable memory written only after explicit approval, with duplicate and conflict checks, provenance, visibility, and optional
review_afterandexpires_at—remember - Raw sources turned into wiki pages, with stale-ingest detection when a file changed after it was indexed —
ingest - The memory inbox, audit, archive, restore and forget workflows, plus a read-only consolidation plan applied per action with approval —
review - Backup, migration, graph export, rebuilds and advanced maintenance —
admin - Point-in-time answers: asking what was true in March reconstructs from dated files and their supersede lineage, matched by a regex and a calendar rather than a model
Requirements
No account, no key and no hosted backend — everything is local files, and the installed CLI, MCP server and viewer carry no telemetry. Install with Homebrew, then lnk setup, which detects Claude Code, Codex, Cursor, Windsurf, Zed, Kiro and Gemini CLI and wires them in one pass. For an MCP-only install, pip install link-mcp and launch python3 -m link_mcp --wiki ~/link/wiki --surface slim; the server.json publishes link-mcp at 2.3.0 over stdio. --surface slim is the recommended six-tool surface, --surface full keeps the compatibility set. Paraphrase matching needs the optional link-mcp[semantic] extra and a one-time model fetch you approve; recall itself never touches the network. On Homebrew Python, externally-managed-environment means install into a dedicated venv.
Setup effort
Follow the published steps — brew install gowtham0992/link/link
USE CASES
01
Starting a session without re-explaining yourself
Have the agent make one empty-query recall on its first substantive turn and pick up the preferences, decisions and project constraints already approved.
02
Sharing one memory across every agent you use
Wire Claude Code, Codex, Cursor and the rest to the same workspace, so what one agent learned the next one reads.
03
Keeping junk out of long-term memory
Work the inbox — read what was proposed, archive or forget what should not stick, and approve only what you want remembered.
04
Turning a folder of notes into something queryable
Drop transcripts, articles and project files into the raw layer, then ingest them into source-backed pages the agent can cite.
6 tools
Listed in project docs. Your client may show a different list.
recallrememberingestreviewadminBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
python3 on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
brew install gowtham0992/link/link
lnk setuplnk setup finds Claude Code, Codex, Cursor, Windsurf, Zed, Kiro and Gemini CLI on your machine and wires each one — workspace, MCP server and session hooks. Run it again after brew upgrade.
MCP Clients
Claude Code
CLAUDE CODE · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent claude-code --write --hooksThis creates ~/link, sets up the MCP server and wires Claude Code. Leave out --write to preview the configuration first.
Codex
CODEX · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent codex --write --hooksThis creates ~/link, sets up the MCP server and wires Codex. Leave out --write to preview the configuration first.
Cursor
CURSOR · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent cursor --write --hooksThis creates ~/link, sets up the MCP server and wires Cursor. Leave out --write to preview the configuration first.
Kiro
KIRO · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent kiro --writeThis creates ~/link, sets up the MCP server and wires Kiro. Leave out --write to preview the configuration first.
GitHub Copilot
GITHUB COPILOT · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent copilot --writeThis creates ~/link, sets up the MCP server and wires GitHub Copilot. Leave out --write to preview the configuration first.
VS Code
VS CODE · TERMINAL
git clone https://github.com/gowtham0992/link.git
cd link
bash integrations/vscode/install.shOn Windows run .\integrations\vscode\install.ps1 instead. The installer creates or updates ~/link, installs link-mcp and writes the agent instructions.
Antigravity
ANTIGRAVITY · TERMINAL
brew install gowtham0992/link/link
lnk onboard --agent antigravity --writeThis creates ~/link, sets up the MCP server and wires Antigravity. Leave out --write to preview the configuration first.
Any MCP client — Manual
ANY MCP CLIENT — MANUAL · TERMINAL
python3 -m pip install --upgrade link-mcpAdd this to your client's MCP configuration:
ANY MCP CLIENT — MANUAL · JSON
{
"mcpServers": {
"link": {
"command": "python3",
"args": [
"-m",
"link_mcp",
"--wiki",
"~/link/wiki",
"--surface",
"slim"
]
}
}
}--surface slim gives the recommended six tools; --surface full keeps the compatibility set. On macOS with Homebrew Python, if pip reports externally-managed-environment, install into a venv (python3 -m venv ~/.link-mcp-venv, then ~/.link-mcp-venv/bin/python -m pip install --upgrade pip link-mcp) and use that python as the command.
