Folio 0.4.4: notifications, review of agent edits, page owners and team skills
· Sergii Kravtsov · Folio
Folio (foliowiki) 0.4.4 is about working with other people and with agents in one wiki: who was mentioned, what an agent changed, who owns a page and where the team keeps its instructions for agents.
Notifications for comments
The bell reports an @mention in a comment and a reply in a thread you took part in. Only a person who can see the page is notified. A comment written by an agent through MCP notifies in the same way. Typing @ in the comment field offers people from the space. There is no email.
Comments on whiteboard elements and table cells
You can comment on a single element of a board or on a cell of a data table, in the browser and through add_comment (elementId; rowId and columnId). The link in a notification opens the thread and shows the element or the cell. The thread of a deleted element, row or column stays in the list with a note.
Review mode for edits by agents
The setting is per space: space menu, AI agents, then Edit at once or Send edits for review. The default is Edit at once, and only a space admin can change it.
- In review mode
update_page,create_pageandPUT /api/pages/:idwith an API token create a proposal and leave the page text as it is, until an editor or admin accepts it in the On review list, which shows line-by-line differences. - If the page has changed since, the proposal is marked and can be accepted only after the differences against the current text are shown.
- Only Markdown pages are covered. While the mode is on, the agent tools for boards, tables, forms, bases, properties, tags and artifacts are refused.
- Comments from agents are posted at once. People editing in the browser do not go through the queue, and
git pushis not intercepted.
Page owner and review date
The properties owner, verified and review_by are stored in Git as ordinary page properties. In the properties section under the title (in edit mode) you choose the owner, set the date of the next review and press Mark as verified; the term is 90 days, or the page's previous period.
- A badge under the title shows Verified, Changed after verification or Review overdue, and an overdue page is marked in the tree.
read_pageandfetchgive an agent averificationblock with the state.- Once a day, overdue pages send a reminder to the owner's bell, or to the space admins when there is no owner, at most once a week per page.
Team skills over MCP
A page with the tag skill and a description property is offered to agents through the tools list_skills and get_skill and as MCP prompts. Only pages the user can see are available, public sites refuse the calls, and a new page is visible to the agent at once. When someone edits the page, the next read returns the new text; nothing is redeployed. Because an agent reads a skill as an instruction, keep skill pages in a space with a small circle of editors, and do not put secrets in them. Setup and safety notes are in TEAM-SKILLS.md. For the general connection steps, see integrations.
A fix for stale writes
update_page and PUT /api/pages/:id no longer silently replace newer edits. read_page and GET /api/pages/:id now return bodyRevision; pass it back as baseRevision and a write based on a stale read is refused (revision_conflict, HTTP 409) instead of replacing what was typed in the page meanwhile. Without baseRevision the call replaces the whole page as before. This was reported in issue 11. The MCP server now has 51 tools.
Also in 0.4.5: Folio AI on Claude
This section is about a separate release, 0.4.5, published alongside 0.4.4. Folio AI can now run on Claude through an Anthropic API key, next to Cursor. Setups that use Cursor keep working as before.
The key is billed by usage, and a Claude subscription cannot be used. The models are Claude Opus 5.5, Sonnet 5.5 and Haiku 5.5. A key can be personal, set for one space or for the whole instance, or come from an environment variable; it is stored encrypted. A public site never uses a personal key. A reply is produced by the provider you choose, so the pages the assistant reads go to that provider.
One limit: between your messages, Claude remembers only the text of earlier messages, not earlier tool results.
Before you upgrade
Back up first. Migrations 061, 062 and 063 come with 0.4.4, and migration 064 with 0.4.5. They are one-way, so an upgraded database cannot go back to 0.4.3 without restoring the backup. The 0.4.4 release notes have the full list. The public demo is shared and resets daily. To run Folio yourself, start with the install guide; the code is on GitHub under the MIT license.
See it in a running Folio
Open the live demo and click through a real Folio instance, or install it and move one space over. Folio is open source and stores everything in Git.
Related
More from the blog
- LLM wiki for a team: Markdown in Git, readable by agents over MCP
- Obsidian Bases outside Obsidian: open and edit .base files in a browser
- Obsidian MCP: ways to give an AI agent your vault
- Notion vs Obsidian for a team: what each one gives you, and when neither fits
- Mermaid vs PlantUML: which to use for docs in Git
- Groups and single sign-on in an open-source wiki: free, in one MIT edition
- Side-by-side comparison of wiki pages and versions: see what changed
- Publish a Cursor canvas to your team wiki: dashboards that outlive the chat
- Publish a Claude artifact to your team wiki: interactive pages that live in Git
- Make any page a template: custom templates for your Folio space
- Confluence MCP, Notion MCP and a wiki that is its own MCP server
- Export Confluence to Markdown and keep it in Git
- Mermaid diagrams in a team wiki: keep them as code
- See how your team's knowledge connects: graph, Canvas and Bases in Folio 0.4
- Open an Obsidian vault as a team wiki, without changing a file
- Publish a wiki space as a public website, and let visitors ask it questions
- Docs-as-code without the IDE: edit your repository's docs in a browser
- New hires ask the wiki, and the wiki learns what it lacks
- Folio boards: built on Excalidraw, made for teams