Skip to main content

​
1. What is the Wiki?

​
It captures the organizational language that used to slip away in meetings

Every organization has its own language. Phrases like “the payment system overhaul project” or “the price increase decision we put on hold last time” mean that the same people, decisions, and topics keep coming up across different meetings, and each time they recur, the relationships between these vague terms become a little clearer. The problem is that this language mostly evaporates the moment a meeting ends. Unless you take the time to open up the minutes again, your next meeting starts over from scratch, with the context lost. The Wiki, a new feature in Tiro, automatically captures and organizes this language and these relationships that used to slip away. There’s no need to organize anything separately. Just write your notes, and the people, topics, and decisions that come up are organized into pages, and the relationships between them are turned into a map that expresses the context and knowledge of both individuals and the organization. Of course, you can also edit the Wiki content yourself or change the connections.

​
From records to the Wiki, from the Wiki to agents

Tiro turns your team’s conversations into assets in three stages.
  1. Record: Record meetings, calls, and memos, then automatically transcribe and summarize them.
  2. Wiki: Organize the people, decisions, and topics scattered across those records into your organization’s own language.
  3. Agent: Based on that organized language, AI works with knowledge of your team’s context. We support a variety of tools that agents can access, such as MCP, API, and CLI.
For an organization’s AI transformation, meeting minutes are not the end but the beginning. Between records and agents, the Wiki preserves conversations that would otherwise vanish the moment they’re spoken, turning them into knowledge you can reuse anytime. The more meetings you hold and the more notes you accumulate, the more naturally the Wiki grows. It starts with just a few pages, and as your notes reach 200 or 1,000, the relationships connecting them become clearer. The Wiki works smartly: if you delete Wiki entries that Tiro previously created or edit their connections, it understands this and is built to grow in line with the changed Wiki content.

​
How is the Wiki structured?

The Wiki is made up of four elements.
  1. Pages: The units of people, topics, and decisions extracted from notes. The pages (nodes) that appear in the Wiki fall into the following three kinds.
    1. People who appeared in meetings
    2. Topics that are mentioned repeatedly
    3. Decisions that were agreed upon
  2. Sources: Links that point to which statement in which note a page came from. Clicking one takes you straight to that note paragraph, where it’s highlighted.
  3. Relationships: The connections between pages. Each relationship has a type, such as colleague, reports to, belongs to, or related.
  4. Personal notes: Descriptions that each person can organize differently for the same page, visible only to themselves. AI writes a draft first, and you can freely edit on top of it.

​
Why do you need the Wiki

The value of the Wiki is clearest when you use it together with an AI agent. There are three main benefits.
  1. AI knows your team’s context and answers accurately. Without the Wiki, AI tends to sift through the entire conversation transcripts of hundreds of notes all at once, producing answers that look plausible but are actually wrong (hallucinations). With the Wiki, AI first finds the relevant page, follows the exact sources and relationships to answer, and says it doesn’t know when it doesn’t.
  2. AI answers become faster and lighter. Since only the exact pages and relationships are passed along, AI has less to process and answers come back faster. Once your notes exceed 10,000, having the Wiki or not can be the difference between getting an answer at all or not.
  3. You can trace where AI found its answer. You can check which source on which page the AI followed, so you can find and fix incorrectly connected parts, and from then on you’ll get accurate answers.
The Wiki gathers the words scattered across your organization into a well-organized form and makes them easy for people to fix and manage. On top of that, AI agents operate more accurately, more lightly, and more reliably.

​
Who does it help

  • When you use it alone: It becomes a map of your thoughts, people, and topics. What decision you made a month ago, and who you talked with about what, no longer disappears.
  • When you use it with a team: It becomes a shared language that works without explaining everything from scratch each time. Onboarding new people, recurring meetings, 1:1 prep, and quarterly retrospectives all get much faster.
  • When you use it with AI: AI agents like Ask Tiro and Claude know your team’s context and bring back accurate answers rather than plausible-sounding ones.

​
2. How do you use the Wiki?

The Wiki is available on the Pro plan and above. If you’re on the Light or Free plan, a plan upgrade prompt is shown. Wiki extraction and AI usage are included in the Pro plan and above subscription plans, at no additional cost. (The Team and Enterprise plans can use it as well.)

​
Enabling the Wiki

The Wiki is provided only for workspaces that have explicitly enabled the Wiki feature.
  1. Go to [Wiki] in the workspace sidebar.
  2. Review the Wiki activation guidance and enable it.
  3. From the moment of activation, the most recent 3 months of notes are processed to build your starting Wiki. This usually takes about 1 to 2 hours, though it varies by timing.
This release is enabled in stages starting with heavy-user workspaces, and in the second week of June 2026 it will be available to enable on all Pro plan and above workspaces. If you’d like to enable the Wiki for notes older than 3 months as well, contact hello@theplato.io and we’ll guide you individually.

​
A tour of the Wiki screens

You can view the Wiki across three main screens.

​
Page list

The people, topics, and decision pages accumulated in your workspace are gathered in one place. You can find the page you want right away with search. On the Wiki home, you can see the total page count, connection count, and a graph preview at a glance.

​
Page detail

When you open a page, you see its sources, relationships, aliases, and personal notes together.
  • Sources: Shows which statement in which note the page came from. Clicking one takes you straight to that note paragraph.
  • Relationships: Shows which other people, topics, or decisions this page is connected to.
  • Aliases: Groups together other names that refer to the same subject.
  • Personal notes: A description visible only to you. You can edit directly on top of the AI draft.

​
Wiki graph

A map where people, topics, and decisions are connected by relationship lines. Hovering over a node reveals its connections and definition, and you can click or drag a node to look closer. Each time a conversation is added, the graph grows on its own.

​
Organizing the Wiki

​
The Wiki fills in automatically

From the moment you write a note, the Wiki fills in automatically. There’s no need to create pages separately. Items that are mentioned multiple times in a single note or that you add yourself become pages. The more notes you accumulate, the more the Wiki grows automatically. Pages are usually organized within 1 to 2 minutes after you finish a note, and the Wiki updates when you finish a new note, re-record or re-summarize, or upload a new file.

​
Organizing the Wiki yourself

When the automatic organization isn’t perfect, you can refine it yourself. What you’ve organized yourself always takes priority over the automatic organization. In the page detail, opening the [Page actions] menu lets you do the following.
  • Rename / add alias: Refine the page name, or group name A and name B together with an alias as the same subject.
  • Merge this page: Combine two pages into one when the same subject was split across them. Aliases, relationships, and sources all get moved over.
  • Block automatic extraction: Exclude a page you don’t want appearing in the Wiki from automatic extraction.
  • Delete page: Removes the page along with its connected aliases and relationships. The original mentions left in the notes do not disappear.
If there’s a person or topic you want to set up in advance, you can also add a page yourself. Sources are then connected automatically as related notes accumulate later.

​
Tiro suggests cleanups for you

As automatic organization builds up, similar pages can split into two, or a page mentioned once may never be used again. Tiro finds pages worth tidying and suggests them to you. Suggestions come a few at a time, and only the ones you review and accept are applied to the Wiki. Nothing changes all at once — you look and choose. Which pages become cleanup candidates? Tiro suggests two kinds of cleanup.
  • Merge suggestion: When the same subject is split across two pages because their names or aliases overlap, Tiro suggests combining them into one. On merge, aliases, relationships, and sources all move to the surviving page.
  • Delete suggestion: Tiro suggests tidying an isolated page that is barely connected to other notes or pages. Deleting a page does not remove the original mentions left in your notes.
Pages you’ve touched yourself are left out of suggestions. A page where you added an alias, linked a relationship, or wrote a personal description is treated as something you’ve organized yourself, so it’s excluded from cleanup suggestions. The principle that what you’ve organized yourself always takes priority holds here too.

​
Using the Wiki in Ask Tiro, MCP, CLI, and the REST API

The Wiki isn’t just for browsing on screen. You can query it right inside Ask Tiro, inside AI agents like Claude, and from the terminal.

​
Ask Tiro

When you ask Ask Tiro a question, it answers by referencing not only your notes but also the people, topics, and decisions in the Wiki.
Summarize the decisions the Tiro PM made last quarter
Ask Tiro follows the decision relationships from the “Tiro PM” page in the Wiki and shows you an answer organized in chronological order, along with the sources. The more the Wiki accumulates, the more accurate the answers become. If the Wiki is enabled, Ask Tiro accesses it on its own as appropriate and answers based on the Wiki.

​
Claude and external AI agents (MCP)

When you connect the Tiro MCP in Claude Desktop or Claude Code, the following tools work right away. For each tool’s parameters and response format, see the Wiki tools page in the developer docs. For example, ask Claude something like this.
Where did the payment system overhaul come up in this week’s meetings? If anything was decided, summarize it.

​
Tiro CLI

You can search and look up the Wiki directly from the terminal. This is useful in environments where external AI use is restricted within the company, or when you want to plug Wiki data into your own workflow.
Installation and authentication take just one tiro auth login. For details, see Tiro API & MCP & CLI usage guide.

​
REST API

If you want to build your own automation workflow, you can query all of the Wiki’s data through the REST API. The page list, page details, graph, and search are all provided under the same permission model. For the detailed specification, see the developer documentation.

​
3. Wiki security and permissions

Wiki security starts from note permissions. The Wiki will never make note information that you couldn’t originally view become visible. Each person sees only as much of the Wiki as they’re allowed to view. For an account without permission to view a note, that note’s information is exposed nowhere.

​
The Wiki is per workspace

  • Different workspaces have different Wikis.
  • Someone in one workspace cannot see any of another workspace’s Wiki pages, relationships, or sources.
  • If the same person appears in two workspaces, a separate page is created in each workspace.

​
It follows note permissions exactly

  • Everyone in the workspace views the Wiki’s pages, relationships, and sources together.
  • Statements from notes you can’t access don’t appear anywhere in the Wiki. Even if the page itself is visible, sources that came from notes you don’t have permission for are automatically left out.
  • If you leave a workspace or are removed as a note collaborator, the information that note created is no longer visible to you.
  • If you delete a note, all of that note’s sources, relationships, and search results disappear.

​
Personal notes are visible only to you

Personal notes look different for each person, even on the same page. The description you wrote is visible only to you. Neither workspace administrators nor Tiro operators can access another person’s personal notes. Personal notes are protected in two stages: the app’s permission checks and personal-key encryption.

​
Permission flows shown by example

​
When using it together as a team

When you accumulate meeting notes in a team workspace, the people who can access those notes view the same people, topics, and decision pages together. However, sources that came from notes only you can access, such as a 1:1 note conducted privately, are not visible to others without permission. Even if the page is visible, only those sources are hidden.

​
When using it alone and then adding a collaborator

Suppose an individual has accumulated notes in a workspace and built up a Wiki, and then adds a colleague as a Collaborator on a certain note. From that point on, that colleague can see the sources of the pages that came from that note. Conversely, if you remove them as a collaborator, the sources that note created are no longer visible to that colleague. Even in this case, personal notes are not shared.

​
How is data stored and protected

  • Wiki data is stored only within the domestic (Seoul) region.
  • Both at rest and in transit it is encrypted, and sensitive information like personal notes is locked once more so that only you can open it.
  • The original audio is not stored in or passed to the Wiki. The Wiki only takes the text-organized note body as input.
  • The AI used to build the Wiki does not train models on customer data.
If you need an enterprise security review (data location, compliance, subprocessors, and so on), please contact our sales team or use the security review materials request form.

​
Exporting Wiki data

You can export your own workspace’s Wiki data anytime. The exported data is in JSON format. It contains the pages (name, kind, aliases), the sources for each page, the relationships between pages, and the personal notes you wrote.
  • Download it all at once as a JSON file from the [Export] menu on the Wiki screen.
  • You can also receive the same JSON data through the REST API, MCP, and CLI.

​
Frequently asked questions

Q. How is this different from a wiki like Notion? A Notion wiki is filled in by people writing it themselves. Tiro’s Wiki grows automatically from the conversations in your meetings, calls, and get-togethers. Every time a person, project, or customer is mentioned, it gets connected, and subjects that recur take on their meaning within your company. The difference is that it fills in as much as you work, without organizing anything separately. Q. If I move a note to another workspace, does the Wiki follow it? In the original workspace’s Wiki, that note’s traces are cleaned up, and in the new workspace’s Wiki, that note’s people, topics, and decisions are newly organized. Q. If I edit the note body directly, does the Wiki change along with it? The Wiki updates when you first finish a note, when you re-record or re-summarize, and when you upload a new file. If you’ve only lightly touched up the body, it may stay in its previous state until the next update.