First 10 minutes

Turn one local note into agent memory.

Start with the demo, add one real source, save one explicit memory, then ask an agent to query Link through MCP, skills, or the CLI.

1. Run The Demo

The demo is the fastest proof of value. It already has raw sources, wiki pages, memories, backlinks, and graph data.

macOS with Homebrew:

brew install gowtham0992/link/link
lnk try
lnk serve link-demo

The Homebrew formula is maintained in the public gowtham0992/homebrew-link tap.

Or from source:

git clone https://github.com/gowtham0992/link.git
cd link
python3 link.py demo
python3 link.py next link-demo
python3 link.py serve link-demo

On Windows from source, use the Python launcher:

git clone https://github.com/gowtham0992/link.git
cd link
py link.py demo
py link.py next link-demo
py link.py serve link-demo

Use lnk try for the shortest Homebrew proof loop. It creates the demo, checks readiness, runs a compact query and brief, and prints the viewer command plus the first agent prompts. From source, use python3 link.py try or py link.py try.

Judge the generated demo The repo's root wiki/ is only a scaffold for local development and personal testing. Generated content in wiki/, raw/, and link-demo/ is ignored by git so private memory is not published by accident.
Viewer is optional lnk serve is only for browsing Link in a local web UI. CLI commands, official skills, and MCP-enabled agents work without it because they read the same local wiki/ files directly.

The demo includes one pending memory intentionally, so the review inbox and explain-memory workflow are visible. Run lnk review-memory prefer-local-personal-memory link-demo if you want memory audit to be fully clear.

Open http://127.0.0.1:3000, then inspect /brief, /memory, /ingest, /graph, and /health. Open more for prompts, proposal review, audit, captures, profile, log, and all pages. Link accepts localhost too, but the numeric loopback address avoids slow IPv6 fallback in some Safari setups.

lnk query "why does Link help agents?" link-demo --budget small
lnk brief "working on agent memory" link-demo
lnk benchmark "agent memory" link-demo
lnk health link-demo

2. Install Link For Your Agent

From the cloned checkout, run the installer for the agent you use. Re-running the same installer updates code and instructions without replacing existing wiki data.

bash integrations/codex/install.sh
bash integrations/kiro/install.sh
bash integrations/claude-code/install.sh
bash integrations/cursor/install.sh
bash integrations/copilot/install.sh
bash integrations/vscode/install.sh
bash integrations/antigravity/install.sh

Use --project for a repo-local Link install. Project-scoped memory then stays separate from other project memory while still allowing broad user memory to be recalled.

On Windows PowerShell, use the matching install.ps1 script:

.\integrations\codex\install.ps1
.\integrations\kiro\install.ps1
.\integrations\claude-code\install.ps1
.\integrations\cursor\install.ps1
.\integrations\copilot\install.ps1
.\integrations\vscode\install.ps1
.\integrations\antigravity\install.ps1

3. Add One Source

Open the local viewer and use ingest -> Add Raw Source, or write a first note directly:

mkdir -p ~/link/raw
cat > ~/link/raw/first-memory.md <<'EOF'
---
title: "First Link memory"
source_type: note
date_captured: 2026-05-04
---

# First Link memory

I am testing Link as local personal memory for agents.
Raw notes stay local. The agent turns them into source-cited wiki pages.
EOF

Check pending work:

lnk ingest-status
Safety gate Link blocks normal ingest guidance when raw files contain secret-looking values or cannot be read safely. Redact or fix those local files first.
Existing Link data If you already have files in ~/link/raw/, lnk ingest-status may point to a different pending file first. If first-memory.md was already ingested and you overwrite it, Link marks that raw file as stale and asks the agent to refresh the existing source page.

4. Save One Direct Memory

Use natural language with an agent:

remember that I am testing Link as local personal memory for agents
brief me from Link before we continue
what does Link remember about local personal memory?

Or use the CLI:

lnk remember "I am testing Link as local personal memory for agents." --type preference --scope user --tags onboarding
lnk brief "local personal memory"
lnk recall "local personal memory"
lnk profile
lnk memory-audit

5. Ask The Agent To Ingest

In your agent chat, ask:

ingest raw/first-memory.md into Link

The agent reads ~/link/LINK.md, creates a source page, updates concepts/entities when useful, updates the index and log, rebuilds backlinks, and validates generated pages.

Return to /ingest after the agent finishes. Link shows which raw files are represented and gives follow-up prompts for proposals or retrieval checks.

6. Verify The Loop

lnk doctor --fix
lnk health
lnk ingest-status
lnk validate
lnk memory-audit
lnk operations
lnk verify-mcp

lnk verify-mcp should report Result: ready when you use MCP. Then ask your agent:

query Link for first Link memory

If the answer comes from Link, local agent memory is working.