Positioning

Link is not a notes app. It is local memory for agents.

The wiki is the inspectable storage layer. The product is shared, source-backed memory that local agents can query without starting every session from zero.

Best Fit

Use Link when you want one local memory layer that multiple agents can share. It is strongest for developer and power-user workflows where privacy, provenance, and inspectable files matter.

Personal agent memory

Preferences, decisions, project conventions, and active context that should survive between Codex, Kiro, Claude, Cursor, Antigravity, and other local agents.

Source-backed knowledge

Raw notes, transcripts, release notes, articles, and project files that should become cited Markdown pages instead of hidden context.

Inspectable retrieval

Smart query packets with reasons, sources, graph links, budgets, and follow-up actions instead of full-folder dumps.

Local ownership

Plain Markdown and JSON indexes on your machine. No hosted backend, telemetry, or required cloud account.

The Loop Link Changes

Link is useful when it changes the start and end of real agent sessions.

MomentWithout LinkWith Link
Starting workYou retype project state and preferences.The agent asks for a brief or calls memory_brief/query_link for compact local context.
Switching agentsEach tool has its own memory gap.Codex, Claude, Cursor, Kiro, VS Code, and Antigravity can point at the same wiki.
Saving a decisionThe note disappears into chat history.An explicit remember becomes a reviewable Markdown memory.
Trusting memoryYou cannot see why the agent knows something.You can inspect sources, graph links, review state, and lifecycle history.

How To Choose

If you need...Use Link when...Use another category when...
Human-first notesYou want agents to query and maintain the notes as memory.You mainly want a polished human writing app, mobile sync, plugins, and manual note-taking.
Hosted app memoryYou want local files, no cloud account, and MCP access from many desktop agents.You are building a hosted product and need managed APIs, user accounts, dashboards, and cloud-scale operations.
Stateful agent runtimeYou already use agents and need shared memory outside any one runtime.You want an entire agent platform with its own execution loop, hosted state, and deployment model.
Temporal business graphYou need personal/project memory with explicit review and source-backed Markdown.You need automatic entity extraction, temporal fact invalidation, multi-user business data, and enterprise integrations.
Plain file searchYou want search plus memory lifecycle, graph context, MCP tools, validation, and provenance.You only need grep, ripgrep, or a folder of notes with no agent-memory workflow.

Trust Model

Link deliberately avoids hidden memory. A durable memory is a Markdown page with scope, status, review state, source/provenance, graph links, and a local audit trail. Agents can recall it, but humans can inspect, edit, archive, restore, or forget it.

raw/file.md -> wiki/sources/file.md -> linked concepts
remember "preference" -> wiki/memories/preference.md
query_link -> compact context + why_selected + follow_up actions

Boundaries

  • Link is local-first personal software, not a hosted SaaS backend.
  • The local web viewer has no authentication and must stay on loopback unless you add your own auth layer.
  • Ingest quality depends on the agent that reads and writes pages; Link provides schema, validation, safety gates, and review workflows.
  • Generated memory is not automatically trusted. Use proposal, review, explain, archive, and forget workflows.