When do I get access?

We extend invites in small batches, regularly. You will get an email the moment you are in. An invite link from someone already inside works right away.

Do you see my prompts or my code?

No. Claude runs in your own session, exactly as it does without us; our backend only stores and serves the wiki’s pages. In chat, only the pages a question needs are sent to Claude’s cloud for that answer, never the whole wiki.

Do I still need my CLAUDE.md or my chat instructions?

Yes, and you keep what you have. In Claude Code, CommonGround adds a short pointer to your CLAUDE.md. In Claude Chat, the connector does the same job, and a line in your instructions can point at the wiki too. The wiki holds the rest: the decisions, the voice, and the history of how each one changed.

Does this spend my Claude usage?

Yes, it runs on the plan you already pay for. Seeding is one longer conversation, an ingest is a short one, and answering opens only the pages it needs. We spend nothing and meter nothing.

Where does my wiki live, and can I take it with me?

In a private git repo we host, with a plain-markdown clone on your disk that you can read, grep and back up. Leaving is a clone: the repo is yours.

How does my team get in?

Share an invite link from the web app. Members read and search, curators edit, admins manage the wiki and its surfaces.

What happens if my subscription ends?

Reading, search and everyone's local folders keep working, and nothing has been deleted.

Is this just a folder of markdown files?

Yes, and that is the point: plus a schema, a lint, a sync agent, and a history that shows how every line got there.

Every Claude session starts caught up.

A markdown database for context, created and maintained by Claude and curated by you. For your personal wiki or a shared team context. Used across Claude Code, chat and mobile.

rr@acme.corp · claude code

/commonground:ingest deploys will now pass through staging first always. Details on the Slack thread on #dev

Checking Slack thread

Got it. Today’s thread is the source I’ll use to document the decision.

> Created decisions/deploys-pass-staging.md

Recorded the decision and pushed the changes.

wiley.e@acme.corp · claude code

Can we push this to production?

> Checking CommonGround

The team decided yesterday that deploys must pass through staging first. Here’s the Slack thread of the conversation.

ana@acme.corp · claude code

/commonground:ingest the new marketing brief is at brand/brief-q3.pdf. Our website voice changes: confident, plain words, no jargon.

Reading the brief

> Updated brand/tone-of-voice.md

The new voice is recorded: confident, plain words, no jargon. Every project that reads this wiki writes that way now.

Draft the homepage headline.

Checking CommonGround

Your voice page changed this morning. Drafting in the new tone: confident, plain words, no jargon.

Want to look inside one first? See a real wiki

Why CommonGround

A single, shareable source for all your context.

Today, Claude’s context lives in your devices and your chat instructions. It’s messy, unshareable, and hard to update. CommonGround is a markdown wiki that is:

on every surface you use Claude on
shared across your whole team
tracking every source behind an answer

How this sits beside Claude’s own memory: persistent memory for Claude

Without CommonGround

Claude Code reads CLAUDE.md files. Claude Chat reads its own instructions, on the web, on desktop and on your phone. Nothing connects the two, so updating one never updates the other.

CLI

Desktop app

Web app

Mobile app

Claude Code

terminal and desktop app

Root CLAUDE.md

deploys pass staging first

Project CLAUDE.md

deploy directly to prod

Both load in every conversation, and they can disagree.

Claude Chat

mobile, web and desktop apps

Account-wide instructions

nothing about deploys

Project instructions

deploy directly to prod

Separate from Claude Code. Updating one never updates the other.

Four sets of instructions, kept by hand, and none of them knows about the others.

With CommonGround

Claude Code and Claude Chat point at the same wiki. Your terminal, your desktop, your browser and your phone all start from the same context.

Claude Code

CLAUDE.md + plugin → acme wiki

Claude Chat

instructions + connector → acme wiki

acme wiki

index.md

decisions/deploys-pass-staging.md

runbooks/deploy.md

… 140 pages

CLI

Desktop app

Web app

Mobile app

One wiki. Every device. The same answer, with the page named.

Without CommonGround

Ravi wrote the rule into his project’s file. Wiley’s Claude, in another repo, never saw it. Mia, in chat, has no file at all.

Ravi · api/ · claude code

Added to api/CLAUDE.md, line 212: deploys go through staging first.

Wiley · web/ · claude code

Can we push this to production?

Yes. Merging to main deploys straight to prod.

Mia · designer · Claude Chat

How do we ship changes to the site?

I don’t have that context. Can you paste the deploy doc?

With CommonGround

Ravi records it once. Wiley’s Claude and Mia’s Claude read the same page and cite it, each in their own surface.

Ravi · claude code

/commonground:ingest deploys pass through staging first, always.→ decisions/deploys-pass-staging.md

Wiley · web/ · claude code

Can we push this to production?

Through staging first. The team decided this on August 14.decisions/deploys-pass-staging.md

Mia · designer · Claude Chat

How do we ship changes to the site?

Through staging first, then production. Here is the runbook.decisions/deploys-pass-staging.md · runbooks/deploy.md

Without CommonGround

In Claude Code, one long instructions file loads whole every session. The decision is a line among many, and the reason lives in a thread nobody linked.

CLAUDE.md 412 lines · loaded every session

212- deploys go through staging first

Anthropic’s guidance: keep it under 200 lines. Longer files consume more context and reduce adherence.

With CommonGround

Claude starts at the index, opens the two pages the question needs, and cites them. A page can carry its sources too.

index.md

▸ decisions/deploys-pass-staging.md · sources: #dev thread

▸ runbooks/deploy.md

… 138 more pages, unopened

Wiley · claude code

How do we deploy?

Read index.mdRead decisions/deploys-pass-staging.mdRead runbooks/deploy.md

Through staging first, since August 14, because prod deploys broke twice that week. The runbook has the steps.opened 2 of 140 pages · decisions/deploys-pass-staging.md · runbooks/deploy.md

Every change stays on the record.

Each edit lands as a diff with the why beside it. Read what your team’s Claude believes, fix a wrong line, and every earlier version stays readable. Don’t like a change? Put the wiki back to an earlier state.

title: How we deploy · tags: [runbook] · updated: 2026-08-14

− Merging to main deploys straight to prod

+ Deploys pass through staging first (decided 2026-08-14)

edit: deploys pass staging first

One for you. One for your team.

A personal wiki holds how you think and what you decided. A team wiki holds the company, the products and the voice. Both read the same way in Claude Code, in chat and on your phone.

More on a personal wiki for Claude and a team knowledge base for Claude.

What visa paperwork do I still owe for the Barcelona move?

Checking your wiki

Two items left: the padrón appointment on Tuesday and the notarized rental contract. Everything else on your checklist is done.

rr@acme.corp · claude code

/commonground:ingest the pricing decision from today’s call

Checked the charter

> Created decisions/pricing-2026.md

Recorded and published. Anyone on the team who asks about pricing gets this answer now.

Using Claude Code?Plugin setup guide Using Claude Chat?Connector setup guide

Seed it, share it, maintain it.

Seed

Create your wiki in a conversation with Claude, then point your chat, or any Claude Code project to the wiki.

/commonground:seed · /commonground:point

Your wiki becomes one private repo. You or your teammates can keep a local clone, or ask directly to the server via MCP.

/commonground:push · /commonground:pull

Maintain

The wiki maintains its own index, reminds you of stale decisions, old pages and broken links, making sure the wrong answer does not stay in the wiki.

/commonground:lint

No meters. No credit packs. No AI bill.

Curation runs in your own Claude session on the plan you already pay for.

Free

Your wiki, on your machine.

One personal wiki, a plain markdown folder you can read, grep and back up.
Claude Code reads it in every project you point at it.
The full history, and the folder is yours to take at any time.

Pro

Your wiki everywhere, and your team’s.

$7.50 per month for up to 2 seats

Additional seats billed at $4.50 per month.

Your own wiki on every device, and in Claude Chat, through the connector.
Team wikis with invites, and admin, curator and member roles.
Seats match the people in your wiki. Beyond the first two, a new member's extra seat is added to your next invoice, and it comes off when they leave. Nothing is charged mid-period.

14 day trial, cancel any time. Prices exclude tax.

Questions worth asking first.

When do I get access?: We extend invites in small batches, regularly. You will get an email the moment you are in. An invite link from someone already inside works right away.
Do you see my prompts or my code?: No. Claude runs in your own session, exactly as it does without us; our backend only stores and serves the wiki’s pages. In chat, only the pages a question needs are sent to Claude’s cloud for that answer, never the whole wiki.
Do I still need my CLAUDE.md or my chat instructions?: Yes, and you keep what you have. In Claude Code, CommonGround adds a short pointer to your CLAUDE.md. In Claude Chat, the connector does the same job, and a line in your instructions can point at the wiki too. The wiki holds the rest: the decisions, the voice, and the history of how each one changed.
Does this spend my Claude usage?: Yes, it runs on the plan you already pay for. Seeding is one longer conversation, an ingest is a short one, and answering opens only the pages it needs. We spend nothing and meter nothing.
Where does my wiki live, and can I take it with me?: In a private git repo we host, with a plain-markdown clone on your disk that you can read, grep and back up. Leaving is a clone: the repo is yours.
How does my team get in?: Share an invite link from the web app. Members read and search, curators edit, admins manage the wiki and its surfaces.
What happens if my subscription ends?: Reading, search and everyone's local folders keep working, and nothing has been deleted.
Is this just a folder of markdown files?: Yes, and that is the point: plus a schema, a lint, a sync agent, and a history that shows how every line got there.

Every Claude session starts caught up.

A single, shareable source for all your context.

Every change stays on the record.

One for you. One for your team.

Seed it, share it, maintain it.

Seed

Share

Maintain

No meters. No credit packs. No AI bill.

Questions worth asking first.

Start your next session caught up.