How it works

From an empty account to an AI assistant reading your handbook, step by step. Setup takes one person about ten minutes; everyone else just signs in.

Part 1 · Set up a Markdown repository

Create an account

The free trial runs 7 days, no card required. Your account comes with one team; the team owns the Markdown repositories, deploy keys, members, and subscription. You start as Owner.

Generate a deploy key

Notedigit generates an ed25519 keypair in-app. The private key is encrypted at rest, never displayed, and never written to temp files — it's passed to git in-memory per operation. Keys belong to the team: reuse one across repositories or keep one per repo.

Connect the repo

Add the SSH URL and pick a branch. Any git host that accepts an SSH key works — you add the public key to the repo's access settings.

git@github.com:org/handbook.git · branch: main

"Check connection" verifies access with the key before the repository goes live. If it fails, you see the git error; that output is encrypted at rest, since git errors echo the remote URL.

Invite the team, assign the repository

Invite members by email; an invitation reserves a seat and expires after 7 days. Roles are Owner, Admin, and Member. Then assign users to the repository — joining the team grants nothing by itself.

Part 2 · Connect a client

Add the repository URL

Each Markdown repository has one MCP endpoint. Add it to your assistant as a custom connector — OAuth 2.1 authorization-server discovery and Dynamic Client Registration configure everything else. Any MCP client works the same way.

https://…/mcp/9f2c…e41a

Sign in and approve

The user signs in with their Notedigit account and approves access. Only users assigned to the repository get through. No shared bearer tokens anywhere in the flow.

Part 3 · Daily use

Ask your assistant something

"What's our incident escalation policy?" The assistant calls the repository's tools — search, read_file, list_files — and answers from your notes. On the first request, the repo is cloned on demand as a bare, shallow, single-branch mirror: no working tree of plaintext files.

Everything is logged

Each session and tool call records the client, the user, IP, tool name, arguments, status, and duration. Requests are rate-limited per token and per IP.

14:02:11 claude maria@team search {"query":"incident runbook"} ok 84ms

Idle clones are pruned

After about 15 idle minutes the clone is removed; the server holds no copy between sessions. The next request clones fresh, so changes on the git host appear within minutes.

Part 4 · Ongoing

Review the audit trail

Browse sessions and tool calls, filterable by repository, user, and date. When someone asks "is this safe?", this page is the answer.

Pause and come back

If the trial ends or you cancel, the account soft-locks: Markdown repositories and MCP access pause, settings and billing stay reachable, and your data is kept. Reactivating restores everything.

Ten minutes from repo to a working connector.

Start free — 7 days, no card