one knowledge base for your team & its agents

One knowledge base. Every project, every teammate, every agent.

agent-wiki gives your team one workspace with a wiki per client project. Every teammate's Claude — or any MCP-connected agent — reads and writes the same decisions, plans, and notes, so a new chat or a new teammate starts with context instead of an archaeology dig.

Start your team workspace → see how it works

why it helps

Claude is helpful. Starting over is not.

Your team already knows this feeling: the new hire's two-week archaeology dig through Slack, the "wait, which client did we decide that for?" thread, the decision that lives in one person's chat history. agent-wiki turns that scattered context into a clean shared wiki — one your whole team, and everyone's Claude, works from together.

one workspace per team, one wiki per client — click a file ↓

client project

meridian-rebrand.wiki

Priya's Claude is editing

§ orientation · index.md

Meridian Coffee — rebrand

v14 · updated 2m ago last edited by Priya's Claude

This is the home page every teammate's Claude reads first. What this client project is, where things live, and how to keep it tidy.

Studio North workspace · lead: Dana · team of 4 · kicked off 2026-06-02.

What's in here

current-state.md — where the project actually stands. Read first.
inbox.md — messy captures from anyone. Triaged weekly.
brand-voice.md — how Meridian sounds. Claude follows this when drafting.
decisions/ — durable client choices, dated, with the why.
plans/ — current work. One file per plan.
meetings/ — notes from client calls.
stakeholders.md — who's who on the client side.

Right now

Phase: identity locked, launch prep — see plans/current-plan.md
Next client call: Thursday — agenda in meetings/
Open inbox items: 4

House rules for Claude

Put new captures in inbox.md. Don't make new top-level files without asking.
Client decisions go in decisions/ with a date and the alternatives considered.
Match brand-voice.md in anything drafted for Meridian.
Keep dates in ISO format (2026-07-06).

FOR CLAUDE

new teammate? have them read this page + current-state.md first.

§ capture · inbox.md

Inbox

v31 · updated 14m ago last edited by email capture

Anyone on the team drops things here — in a chat, or by forwarding an email. The maintenance agent files them weekly.

This week

[ ]client asked if the new mark works at 16px — favicon check
[ ]fwd: "RE: packaging vendor quote" — from Dana's email, needs a decision
[x]palette v3 approved → decisions/palette.md
…plus a pile of half-thoughts(4 more)

Sort me

↓ the maintenance agent moved these here for review. Confirm or send back.

[ ]"Meridian's CMO prefers Thursday calls" — stakeholders.md?
[ ]"no exclamation points, ever" — brand-voice.md?

CAPTURE

forward emails to this wiki's capture address — they land here.

§ status · current-state.md

Current state

v18 · updated yesterday last edited by maintenance agent

identity lockedon track

Wordmark, palette, and voice approved. Launch prep underway. Public reveal target 2026-08-01.

This week

[x]palette v3 signed off by client (see decisions/)
[ ]packaging vendor quote — waiting on Meridian ops
[ ]launch-channel plan draft for Thursday's call

Blocked / waiting

Legal review of the new tagline — with Meridian's counsel since 2026-07-01.

…owners, timeline, and the full status history below

REVEAL

public launch target: 2026-08-01.

§ decision · decisions/launch-channel.md

Launch channel — earned press first

v1 · updated just now last edited by Marco's Claude

decided2026-07-03

Reveal goes earned press + owned channels first; paid follows two weeks after, once the story lands.

Why

Meridian's audience distrusts ads; the founder story is the asset.
Budget stretches further amplifying coverage than buying reach cold.
Client's CMO explicitly asked for this sequencing on the 06-26 call.

What we considered

Paid-first blitz. Fastest reach, weakest story.
Simultaneous everything. Splits the team across too many deliverables for one week.
…and a few more we ruled out(2 more)

§ people · stakeholders.md

Meridian stakeholders

v7 · updated 3d ago

June Reyes · CMO · final sign-offPortland · GMT-8

What matters to June

Thursday calls only. Never book Mondays.
Wants options framed as trade-offs, not recommendations.
Founder story is sacred — don't polish it into blandness.

…ops contact, counsel, and the founder's pet peeves(3 more people)

HANDY

new teammate? read this before your first client call.

§ voice · brand-voice.md

Brand voice

v5 · updated last week

The short version: Meridian sounds like a knowledgeable friend at the counter — warm, specific, never breathless. Every Claude on this project drafts in this voice.

Do

Name the farm, the roast date, the process. Specificity is the brand.
Short sentences. Room to breathe.
Say "we" — the founders still pull shots on Saturdays.

Don't

✗ "Unlock a world of flavor!"
✗ exclamation points, ever
✓ "This one tastes like a plum that studied abroad."

…vocabulary list, sample captions, and the words June banned

§ plan · plans/current-plan.md

Launch prep plan

v11 · updated 2026-07-05

One plan file, always current. Owner, status, next step, blockers.

Workstreams

press kit — Priya · drafting · next: founder Q&A
packaging — Dana · waiting on vendor quote
site refresh — Marco · in build · next: copy pass in brand voice
…social rollout, email sequence, launch-day runbook(3 more)

…timeline, dependencies, and the risks we're watching

RULE

if it's not in the plan file, it's not happening.

§ meeting · meetings/2026-07-06.md

Client call · Jul 6

v2 · updated 1h ago last edited by Dana's Claude

Decided

[x]palette v3 approved — June signed off live
[x]launch channel: earned press first → decisions/launch-channel.md

Action items

[ ]Priya: founder Q&A draft to June by Thursday
[ ]Dana: chase the packaging quote

Worth remembering

June pushed back on "artisanal" — banned word, added to brand-voice.md. She lit up at the plum line. More of that.

…full notes & who said what

what you get

One shared memory. Every Claude on the team uses it.

A workspace for your team with a wiki per client project. Decisions, plans, voice guides, and meeting notes live in focused markdown files — not in one person's chat history.

p. 012

№ 01

One connection, every project

Each teammate connects Claude once. That single connection reaches every project they can access — including projects added later.

* How it works. Approve the connection once and Claude can list your projects, search across all of them, and read or update the right wiki per request. Every action is checked against your current access, and you can revoke the connection anytime.

p. 013

№ 02

A workspace your whole team shares

Invite teammates with a link. Owners and admins manage roles; client-confidential wikis can be restricted to specific members.

* How it works. Workspaces have owner, admin, and member roles. Wikis default to workspace-wide access, or restrict one to explicitly granted members — removing someone also revokes their Claude connections to it. An activity feed shows who (or whose Claude) changed what.

p. 014

№ 03

It maintains itself

Forward emails into the inbox, get a weekly digest of what changed, and let the maintenance agent triage and tidy — so the wiki stays current without a librarian.

* How it works. Every wiki gets a staleness report: pages going out of date, inbox backlog, structure drift. On Team Starter, the maintenance agent can also file inbox items and refresh stale pages weekly — every edit is attributed, capped, and one click to revert.

p. 015

№ 04

Private, auditable, exportable

Private by default, every read and write logged, full version history with revert — and the whole wiki exports as plain markdown anytime.

* How it works. Sign-in goes through Google. Every page keeps its full version history — compare, diff, and revert any change, human or Claude. Hit export and get a zip of plain .md files that open in any text editor. No lock-in, ever.

how it works

Create the memory once. The whole team reuses it.

Set up a workspace, invite the team, connect Claude once each — then work anywhere while the shared wiki stays current.

Create your workspace

Start a wiki per client project from a template — agency client, campaign war room, consulting engagement, or your own house template.

Invite the team, connect Claude once

Teammates join with a link and approve one Claude connection that covers every project they can access.

Claude keeps it tidy!

Work — it stays current

Decisions and notes land in the right files as everyone works. The weekly digest tells the team what changed.

simple pricing

Start free. Bring the team when it sticks.

start here

Free

· $0

1 project wiki, 20 files
Up to 3 workspace members
Wiki health report & weekly digest
Export & revoke anytime

for solo work

Solo Plus

· $9.99/mo

Up to 10 project wikis
500 files per wiki
Everything in Free
Fair-use limits so it stays reliable

for teams

Team Starter

· $39/mo per workspace

No member cap · roles & restricted wikis
Up to 25 project wikis, 500 files each
Automatic maintenance agent
Custom house templates
Everything in Free & Solo Plus

Start a team workspace →

confused?

Doesn’t Claude already do this?

kind of. also, not quite. there’s a short field note about why project memory still needs a real home.

read the note →