Guides
Meeting notes to a wiki your agent keeps current
To turn meeting notes into a wiki, keep each transcript as an immutable source, then have an agent write and update pages for people, projects and decisions that link back to it. In Cozy, Granola and Italic connectors land transcripts in sources/, and your own agent maintains the pages in wiki/ through MCP.
Meeting tools are good at capturing a single conversation. They are weaker at the question that comes three weeks later: what did we decide about pricing, who owns the migration, and what did that person say last time? Answering that means reading across many meetings. A wiki that an agent maintains does that reading once and keeps the result.
This page explains the workflow in Cozy, a private wiki and file space for each person and their AI agents. Cozy runs no model itself, so the agent doing the work is the one you already use.
The shape of the workflow
Three layers do the work.
- Sources. Every meeting note or transcript arrives as a file under
sources/with a stable ID, a URL and a timestamp. Sources are evidence, and Cozy treats them as untrusted data. Agents read them but do not rewrite them. - Pages. Curated Markdown under
wiki/holds one page per person, project, decision or recurring meeting. Each page cites the sources it was built from. - Maintenance. Your agent reads new sources, updates pages, records conflicts and fixes broken links on a schedule you choose.
Keeping sources apart from pages is what makes the wiki trustworthy. When a page says "launch moved to March", you can follow the link to the meeting where that was said. See source citations for how links into sources/ are tracked.
Step 1: connect Granola or Italic
Cozy lists Granola and Italic among its connectors. Connect either one and meeting content arrives as sources. Connected material goes to the built-in Inbox by default, so nothing lands in your curated pages until an agent or you place it there.
If your meeting tool is not on the connector list, push it yourself. The ingest API accepts documents with a stable ID:
curl -X POST "https://cozy.cloud/api/wiki/workspaces/$COZY_WORKSPACE/ingest" \
-H "Authorization: Bearer $COZY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"documents":[{"id":"meetings/2026-11-04-pricing-sync","content":"# Pricing sync\n..."}]}'
A request takes up to 25 documents of up to 1.5 MB each. Because the ID is stable, pushing the same meeting again updates the existing source instead of creating a duplicate. A source you delete is never re-imported, which matters when a transcript contains something you do not want back.
Step 2: connect your agent
Cozy has one MCP URL per account, https://cozy.cloud/mcp, for all your workspaces. For Claude Code:
claude mcp add --transport http --scope user cozy https://cozy.cloud/mcp
Then run /mcp to sign in and approve the agent on Cozy's consent page. For Codex, run codex mcp add cozy --url https://cozy.cloud/mcp. Tools use My wiki unless the agent passes a workspace argument, and cozy_workspaces lists the workspaces. See the MCP server page for the full tool list.
This job needs the wiki:read, wiki:write and sources:write scopes when you approve the agent. If the agent runs headless, for example on a schedule, use the workspace URL https://cozy.cloud/wiki-mcp/WORKSPACE_UUID with a bearer credential from Agents that has the read, wiki-write and source-write scopes, optionally limited to a folder prefix. Agents cannot see connector credentials or permanently purge anything.
Step 3: let the agent build pages
Ask your agent to organize the Inbox. The tools it reaches for are:
cozy_ingestto bring new material in.cozy_resolveto match names in a transcript to existing pages and flag likely duplicates, so "Dana" and "Dana Reyes" do not become two people.cozy_write,cozy_editandcozy_appendto create and update pages. Edits require an expected revision, so two agents editing at once produce a conflict instead of silent overwrites.cozy_contextto read a page together with its typed neighbors and evidence before changing it.
The graph comes from Markdown conventions on every save. A decision page might look like this:
---
type: decision
description: Moved launch to March
status: active
as_of: 2026-11-04
owner: [[Dana Reyes]]
project: [[Pricing relaunch]]
---
Launch moved from January to March after the vendor delay.
See [[sources/meetings/2026-11-04-pricing-sync]].
Frontmatter keys whose values are wikilinks become typed relations, and the link into sources/ becomes a citation. Read more in typed links.
What to put in each page type
| Page type | Holds | Typical sources |
|---|---|---|
| Person | Role, what they care about, open asks | Every meeting they attended |
| Project | Status, owners, decisions, next steps | Standups, planning calls |
| Decision | What was decided, who, when, why | The one meeting it was made in |
| Meeting series | Recurring agenda, running notes | Each instance of the meeting |
Keep person pages factual and work related. Notes about colleagues are sensitive. Your workspaces are private to you and the agents you authorize, so give each agent only the scopes and folders it needs.
Keeping it correct over time
Meetings contradict each other. A transcript from Monday says one thing and Thursday says another. Cozy gives your agent two ways to handle this.
First, Health flags pages whose cited source changed after the page was last edited, along with broken links, orphans, unsourced pages and CONFLICT: lines. The score is an average across pages, and the "next" list orders fixes by priority. See wiki health.
Second, Dreaming is an offline pass your own agent runs. It orients with cozy_health, looks only at what changed since the last run using cozy_changes, verifies claims against sources, keeps superseded values with their dates and records conflicts rather than guessing. The run is logged in agents/dream/state.md. Details are on the memory consolidation page.
Edits can be undone: the last 50 revisions of a page are readable and restorable, and deletion is a tombstone.
Limits worth knowing
- Search is lexical. There are no embeddings or vector database, so agents should use names, aliases and exact terms. Good aliases on person and project pages help a lot.
- Curated pages are capped at 90,000 bytes and imported sources at 1,500,000 bytes. Very long recurring meetings should be split into one source per session.
- Quality depends on your agent and its instructions. Cozy stores, links and checks the content. It does not summarize anything itself.
- Granola and Italic have their own summaries and search. If you only need to look up one recent meeting, their apps are the faster route. The wiki pays off when you need answers that span many meetings.
A small routine that works
After a day of calls, ask your agent to process the Inbox, resolve names, update the affected person and project pages, and append new decisions. Once a week, ask it to run a dream pass and report the Health score. Review the diffs through page history when something looks off.
Frequently asked questions
Does Cozy summarize my meetings?
No. Cozy runs no model itself. It stores transcripts as sources and exposes tools, and your own agent writes the summaries and pages.
Which meeting tools connect directly?
Granola and Italic are listed connectors. For anything else, push transcripts with the ingest API using a stable ID, or upload Markdown, text, JSON or CSV files.
What happens if I re-push the same meeting?
A stable ID updates the same source instead of creating a copy. A source you deleted is not re-imported.
How do I know a page claim came from a real meeting?
Pages link into sources/, which Cozy records as citations. Health also flags pages whose cited source changed after the page was last edited. See source citations.
Give your agents a memory worth keeping
Cozy gives every account a private wiki that Claude, Codex, ChatGPT and other MCP clients can read and maintain.
Start your wiki