🔍 Read the full analysis: How I Gave My AI Agents A Shared Desk With Thrymvault on ThorstenMeyerAI.com
Get movie nights delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
Thorsten Meyer says his StrongMocha News Group is building Thrymvault into a shared workspace where AI agents and an editor can track newsroom work. The system is designed around approved applications, attributed changes and a ban on agent deletions; backup hardware is planned but not yet running.
Thorsten Meyer has described how his StrongMocha News Group is using Thrymvault as a shared desk for AI agents working on newsroom assignments. The workspace is intended to make story status, editorial instructions and agent changes visible in one place, replacing a workflow Meyer says had relied on chat and a code-oriented task tracker.
Meyer’s account, published November 13, says that on one day earlier in the month his team used agents to handle nine articles, including source gathering, drafting and graphic preparation. He said he had to ask agents for status updates, send headline changes through chat and lacked a shareable link to a completed explainer page. He presents those problems as the reason to give agents a persistent, shared workspace.
Thrymvault is described as a self-hosted workspace for pages, databases and boards, built and run on the group’s own machines. Agents can access it through an MCP server with 20 tools, a REST API or a command-line tool. Meyer says the agent guide is generated from the same tool catalogue as the server, so its instructions match the available tools.
Under the proposed newsroom workflow, stories move through board stages from topic selection to source-kit preparation, drafting and publication. Agents update a card with status, draft links and open questions; the editor can comment on the card and mention an agent application to request a revision. Decisions such as a new headline rule are recorded in a database and linked to the relevant rule. Meyer says changes are attributed to the approved application that made them, while agents cannot delete content.
The shared desk · animated
How a story moves through the shared desk
One card per story. The editor moves it and asks questions in its thread; the agent does the work, keeps its status current and answers there. Every agent change is signed with its application.
Editorial board
Thread on the card
Editor@Editorial agent shorter title, no colon
AgentDone: title shortened, draft updated.
via Editorial agent
Signed history
- Moved to Kit · by the editor
- Status and draft link updated · via Editorial agent
- Comment mentions Editorial agent · by the editor
- Reply in the same thread · via Editorial agent
- Approved and scheduled · by the editor
- Published link added · via Editorial agent
Agents add and edit. They cannot delete anything.
Source: Thrymvault agent integration guide and rollout plan, November 2026. Shows the desk as designed for StrongMocha News Group; the board templates and the pick-up of mentions are still being rolled out.
Animation: Thorsten Meyer AI
A Traceable Desk for Agent Work
The approach addresses a practical challenge for teams using multiple AI agents: work can happen in parallel, but chat threads may not preserve a clear, durable record of a story’s status, instructions or edits. A shared board could give editors a single place to review work and steer it without relying on agents to interpret old messages.
Attribution and limits on agent access also matter for accountability. Meyer says changes carry the name of the approved application used to make them, and access is granted only through applications approved by a workspace owner. If implemented as described, that record could help an editor investigate a mistake or identify which process needs correction. It does not, by itself, establish that agent-generated reporting is accurate or that every error will be caught.
The system is presented as an internal workflow for Meyer’s network, not as evidence of a wider newsroom standard or independently tested product. Its relevance to other publishers lies in the operational question it raises: how to retain editorial control and traceability when software agents share assignments and make changes.
Popular right now
Vitamix 5200 Blender with 64 oz Container, Black
Bose QuietComfort Ultra Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones with Spatial Audio, Driftwood Sand
Bose QuietComfort Ultra Earbuds (2nd Gen), Wireless Noise-Cancelling Earbuds with Immersive Audio and Wireless Charging Case, Black
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer says StrongMocha News Group operates a network of niche and news sites with AI agents involved in production. In the earlier process, chat carried instructions and status updates, while a task tracker designed for code work helped coordinate tasks. His account says that setup became harder to manage as agents handled multiple parts of the same stories.
Thrymvault is compared in general shape to Notion, but Meyer emphasizes its self-hosted setup and agent access controls. The planned editorial flow treats a board card as the shared record for a story. Moving a card from “Topic” to “Kit” signals an editorial decision that agents are expected to follow; Meyer clarifies that moving the card is not itself a software switch that automatically starts work.
The account distinguishes the system’s current state from planned infrastructure. Thrymvault runs on the group’s own hardware, while a second standby machine and hourly backups are described as next steps, not live features. The published description is Meyer’s account of his own organization and its tools.
“Agents write fast. What they lack is a desk.”
— Thorsten Meyer, describing the newsroom’s earlier workflow
Rollout and Safeguards Still Developing
Meyer’s account does not specify which parts of the described workflow are already operating regularly, how many agents or stories are currently using Thrymvault, or how often editors verify agent work. The article says some features run today and others are being rolled out, but does not provide a detailed deployment schedule or independent performance results.
The source also does not explain the full technical enforcement behind application permissions, how credentials are revoked, or how the system handles mistakes beyond recording changes and preventing agent deletions. The standby machine and hourly backups are planned, so the article does not establish that a second-machine recovery setup is currently available.
More Infrastructure and Workflow Rollout
Meyer identifies a second machine on standby and hourly backups as the next infrastructure step. He also says parts of the system are still being rolled out, but gives no dates for completion. The newsroom’s next visible milestone would be broader use of the shared board and publication workflow, alongside the planned backup arrangements.
For now, readers have Meyer’s description of the design and his account of the newsroom’s needs, rather than an independent evaluation of Thrymvault. Further detail about deployment, operational safeguards and results would clarify how well the workspace performs in day-to-day editorial use.
Key Questions
What is Thrymvault?
Thrymvault is described by Thorsten Meyer as a self-hosted workspace for pages, databases and boards, used to coordinate AI agents and editorial work at StrongMocha News Group.
How do agents access the workspace?
Meyer says agents can use an MCP server with 20 tools, a REST API or a command-line tool. Access is through applications approved by a workspace owner.
Can AI agents delete newsroom content?
According to Meyer, agents cannot delete anything. He also says their changes are attributed to the approved application used to make them.
Are hourly backups already running?
No. Meyer describes a second standby machine and hourly backups as planned next steps, not live capabilities.
Does the article show that Thrymvault improves reporting accuracy?
No independent accuracy results are provided. Meyer argues that a traceable workspace can make it easier to review and correct work, but the account does not establish that it prevents reporting errors.
Source: ThorstenMeyerAI.com
