Apply for beta

GitHub-first design-partner beta

Keep the “why” attached to the Markdown file.

Limn adds text-anchored review threads to files already in GitHub, so teammates and MCP-compatible agents can recover the rationale later.

See the live demo Apply for beta access

Start with a public GitHub Markdown file. Open the demo, select text, then sign in to leave a comment.

docs/authentication.md Open interactive demo ↗

Architecture decision

Session lifetime

Sessions are short-lived and must be renewed after eight hours.

Renewal happens through the identity provider; the application never stores a reusable password.2

Failed renewal returns the user to the sign-in screen.

At a glance Existing GitHub file Text-fingerprint anchor Stored by Limn Callable through MCP

One narrow workflow

Discuss the file where the work already lives.

Limn adds a review layer to public Markdown in GitHub. It does not require moving the document into a separate workspace.

  1. 01

    Open a public GitHub Markdown file

    Use the hosted viewer to render the current file and its Limn threads side by side.

  2. 02

    Select text and discuss

    Signed-in reviewers create, reply to, and resolve threads anchored to the selected passage.

  3. 03

    Retrieve the rationale later

    A teammate can revisit the viewer, or an MCP-compatible client can call Limn’s tools to request the file’s threads.

What persists

Anchored to text, associated with GitHub, stored by Limn.

Limn stores thread and comment data in its service database and associates it with the GitHub repository URL, file path, commit reference, and a text fingerprint. Threads are not committed to the Git repository.

Original selection Temporal.PlainDate represents a calendar date
After nearby edits Text fingerprint matched
If the text is removed Thread marked detached

Matching uses the selected text plus surrounding context. When Limn cannot place an anchor confidently, it exposes the thread as detached instead of attaching it to unrelated text.

Agent-neutral context

Callable tools, not invisible injection.

Limn exposes MCP tools that a compatible client or agent can call. Limn does not intercept every file read and does not automatically add threads to an agent’s context. The client, operator, or prompt must request the tool call.

Illustrative MCP tool call 
get_file_comments({
  repoUrl: "https://github.com/tc39/proposal-temporal",
  filePath: "README.md"
})
Illustrative tool result 
3 open threads
• PlainDate — request for a type decision table
• Temporal — prior-art cross-reference
• proposal — ready for the next review round

Connect an MCP-compatible client with npx -y @limn-sh/mcp. Create a revocable key in Settings → API, then copy the generated client configuration.

Current boundary

Start with one public GitHub workflow.

In scope now

  • Public GitHub Markdown files
  • Browser-based anchored threads
  • Explicit MCP tool calls with assisted setup
  • Hands-on design-partner feedback

Not offered today

  • Private repository access
  • Paid team or enterprise plans yet
  • Self-hosting or compliance certification
  • Guaranteed uptime or support response times

See the design-partner offer or review the current security boundary.

Ready to try it?

Bring one real Markdown workflow.

See Limn on a public file, then tell us where review rationale gets lost today.

Apply for beta access See the live demo