Link - First 10 Minutes

1. Run The Demo

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

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

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.

The demo includes one pending memory intentionally, so the review inbox and explain-memory workflow are visible. Run link 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, /audit, /captures, /propose, and /graph. Link accepts localhost too, but the numeric loopback address avoids slow IPv6 fallback in some Safari setups.

python3 link.py query "why does Link help agents?" link-demo --budget small
python3 link.py brief "working on agent memory" link-demo
python3 link.py benchmark "agent memory" link-demo
python3 link.py status --validate 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.

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:

link 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/, link 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:

link remember "I am testing Link as local personal memory for agents." --type preference --scope user --tags onboarding
link brief "local personal memory"
link recall "local personal memory"
link profile
link 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

link doctor --fix
link status --validate
link ingest-status
link validate
link memory-audit
link verify-mcp

link verify-mcp should report Result: ready. Then ask your MCP-enabled agent:

query Link for first Link memory

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