Roomie Wiki - Collaborative Docs Your Team and Your AI Can Both Read

Every team has the same problem with documentation. The docs live in one tool, the work happens in another, and the AI you ask for help has never seen either. So people write things down, nobody reads them, and the knowledge quietly rots.

Roomie Wiki fixes this by putting your team's docs inside the same workspace as your chat, mail, tasks, and calendar. Multiple people edit the same page at the same time, everyone in a space reads and writes together, and because Roomie works as an MCP server, your AI agents have direct knowledge of every page your team writes.

One place to write. One place to work. One source of truth for humans and AI.

What Is Roomie Wiki

Roomie Wiki is a collaborative documentation system built into Roomie Workspace. It is organized around three simple ideas:

• Spaces hold your team's pages. Everyone in a space reads and edits together, in real time.
• Pages are rich documents with headings, lists, tables, emoji, @mentions, and board tags.
• Folders keep related pages grouped so a growing space stays navigable.

You will find it in the left sidebar of Roomie, right alongside Chat, Mail, Tasks, and Calendar.

No separate tool. No separate login. No separate bill.

Getting Started: Spaces, Pages, and Folders

Open Wiki from the sidebar and you land on your spaces. A space is the top-level container — think "Engineering", "Design", "Company Handbook", or one space per client.

Click New space, give it a name, and you are in. Inside a space, you create pages or folders with one click.

Folders nest pages, pages hold the content, and everyone in the space sees the same tree. That is the whole mental model. There is nothing else to learn.

Real-Time Collaboration, Like a Multiplayer Doc

This is the core of it. When two people open the same page, they edit it together, live. You see your teammate's cursor with their name on it, watch their edits land as they type, and never deal with "someone else has this file open" or merge conflicts.

The editor itself handles everything a working document needs:

• Headings, bullet lists, and checklists
• Tables with rich content inside cells
• Emoji, @mentions of teammates, and #tags that link to your Roomie boards
• Double-click anywhere to edit — no separate edit mode to hunt for

Because @mentions and board tags connect to the rest of Roomie, your docs are not isolated text files. A launch plan can point at the actual sprint board. A postmortem can mention the actual people involved.

Your Docs Live in Your AI's Context

Here is what makes Roomie Wiki different from Notion, Confluence, or Google Docs: your AI agents can read it.

Roomie works as an MCP server. Connect Claude, Kimi, or any MCP-compatible AI agent to your workspace once, and it can search and read your wiki pages the same way it reads your tasks and messages. Your documentation becomes part of your AI's working knowledge, automatically.

That changes how docs get used:

• Ask Claude to "implement the feature described in the API design page" and it reads the actual spec your team wrote.
• Ask your AI to draft onboarding notes for a new hire and it pulls from your real handbook, not a guess.
• Ask "what did we decide about pricing?" and the answer comes from the decision doc, with the reasoning intact.

Documentation stops being write-only. Every page you write makes your AI smarter about your team.

Who It's Built For

Engineering teams. Keep RFCs, API specs, runbooks, and postmortems next to the sprint boards they describe. Tag the board, mention the owner, and let your AI agent read the spec before it writes the code.

Design and consulting studios. One space per client. Briefs, research notes, and decision logs stay together, and when the project ends you export the deliverables as PDF and hand them over.

Regular office work. Meeting notes, company policies, onboarding checklists, holiday calendars. The unglamorous documents every company runs on finally live where everyone already works — not in a fifth tool nobody opens.

Export to PDF, Import from Word

Your docs are never locked in. Every page exports as a clean PDF — for clients, auditors, or anyone outside your workspace. And if your existing documentation lives in Word files, you import a .docx and keep working from where you left off.

Moving in is one click. Moving out is one click. That is how it should be.

Share Publicly or by Email

Not everything stays internal. Each page has two sharing modes:

• Public link. Flip a toggle and anyone with the link can read the page — no account needed. Public visitors get a read-only view and cannot see who else is in your workspace. Turn the toggle off and the old link dies immediately.
• Share via email. Send a personal read-only link to a specific person. You see when it is opened, and you can revoke access per person at any time.

This makes wiki pages work as lightweight client deliverables, published changelogs, or one-off documents for external partners — with access you actually control.

Part of the Workspace, Not Another Tool

The reason wikis fail is distance. When docs live in a separate tool, updating them is a chore and reading them is an afterthought. Roomie Wiki removes the distance: the docs sit one click from your chat, your tasks reference them, your AI reads them, and your whole team edits them together in real time.

If your team already uses Roomie, open the sidebar and click Wiki — it is live in your workspace today. If not, get started with Roomie and bring your chat, mail, tasks, calendar, and docs into one place.