A knowledge base for Claude. Shared across devices and teams.
CommonGround is a version-controlled markdown wiki. You guide it, and your Claude creates, maintains, and reads from it. Use it as a personal wiki, or a shared database of information for your whole team.
Available as a plugin for Claude Code, and a connector for Claude Chat.
/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/deployment-rules.md
Recorded the decision and pushed the changes.
Can we push this to production?
> Checking CommonGround...
The team decided yesterday that all changes must go through the staging server first. Here’s the Slack thread of the conversation.
Seed it, share it, maintain it.
01
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
02
Share
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
03
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
Curated context, versioned like code.
Your wiki behaves like a private shared folder that keeps a changelog. Every change carries a diff and the reason it was made, so you can read what your team’s Claude believes, see who changed it and why, and correct it in one line. Nothing is ever stuck: you can put the whole wiki back the way it was on any earlier day.
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)
decision: deploys pass staging first
From the next message on, every session ships the new way.
One for you. One for your team.
CommonGround started as a personal wiki that could be shared across devices. You can keep a personal wiki that holds everything about how you think, your decisions, your voice and ideas, and have it across every Claude surface.
Then you can create a separate wiki for your team that holds all your shared information about your company, your products, your brand voice and everything work related.
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.
/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.
No meters. No credit packs. No AI bill.
Curation runs in your own Claude session on the plan you already pay for, so there is no usage for us to bill. What a price covers is hosting the wiki behind it.
Free
Your wiki, on your machine.
$0
- 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, billed $90 a year
Covers you and one more person. Each additional person $4.50 a month, billed $54 a year.
- Your own wiki on every device, and in claude.ai, through the connector.
- Team wikis with invites, and admin, curator and member roles.
- Seats follow your members, so the next invoice follows too.
14 day trial, card up front, cancel any time. Prices exclude tax. If you ever stop paying, your wiki stays readable and nothing is deleted.
Access is by invite while we are in private beta. Request one above.
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.
- 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.
- What does claude.ai see when I turn on chat?
- Only the pages a question actually needs, sent to Claude’s cloud for that answer, never the whole wiki. It is a per-wiki switch, off until you turn it on.
- 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.
- 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 explains why every line is there.
Every session starts caught up.
Free for one person. Invites go out in small batches.