🔍 Read the full analysis: Why My AI Agents Needed A Shared Desk on ThorstenMeyerAI.com
Prime made for students and young adults
- Fast, free delivery for dorm and study essentials
- Prime Video and Amazon Music included
- Member-only deals
TL;DR
Thorsten Meyer says his AI-run newsroom is building Thrymvault, a shared workspace for story status, editorial instructions and traceable agent changes. The system is described as a design and a work in progress; the source says a standby machine and hourly backups are planned, not live.
Thorsten Meyer says his AI-run publishing network is building Thrymvault, a shared workspace where editors and agents can track story progress, exchange instructions and record who made changes. The project responds to a practical problem Meyer encountered while coordinating nine articles through chat and a code-oriented task tracker: story status and editorial direction were difficult to see in one place.
Meyer describes Thrymvault as a workspace for pages, databases and boards, built and hosted on the network’s own machines. Agents access it through an MCP server with 20 tools, a REST API or a command-line tool. According to Meyer, the agent guide is generated from the same tool catalogue as the server, so the published instructions are intended to match the available tools.
In the newsroom workflow Meyer outlines, stories begin as cards on an editorial board. The editor decides which topics proceed; moving a card into a “Kit” stage signals the editorial agent to gather sources and prepare a source kit. Agents then draft stories, update their status and attach reports and draft links to the relevant card.
Editors can request changes in a card’s comment thread by mentioning the relevant agent application. Meyer says agents’ responses and edits are associated with the approved application that made them. The design also includes a “stopped” status intended to tell agents to leave a story alone, and a separate database for recording decisions such as changes to headline rules.
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
The proposed desk addresses a coordination problem that grows when several agents handle different parts of a story at once. In a chat-based process, instructions can scroll out of view, updates may be scattered across conversations, and an editor may need to ask an agent for the current status. A shared board could put story state, editor notes and draft links together rather than relying on the latest message.
Traceable changes may also make it easier to review and correct work. Meyer says changes carry the name of the approved application used to make them, giving the newsroom a record of which agent integration acted. That is a stated design feature, not evidence that the system has already improved accuracy or prevented errors. For readers, the potential relevance is indirect: a clearer record may help the newsroom identify how a story changed when it needs correction.
Popular right now
KitchenAid Artisan 5-Quart Tilt-Head Stand Mixer, Almond Cream
Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Bluetooth 5.3, USB-C Charging, IPX4, Black
Ninja Foodi 7-Qt MegaZone FlexBasket Air Fryer, 6-in-1, Black, DZ071
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer says that during one day in November, his team steered nine articles using a chat window and a task tracker designed for code work. Agents gathered sources, drafted material and prepared graphics. But he says he had to ask for progress updates, send headline changes through chat and rely on the right agent to notice them. He also could not share one completed explainer page as a link.
That experience led to the distinction at the center of his account: chat can support a conversation, while a newsroom needs a lasting record attached to each story. Thrymvault is described as resembling a general-purpose workspace such as Notion, but with agent access through controlled integrations. The article presents the newsroom process as a design for how work should move across the desk, alongside a separate description of what is running and what remains in rollout.
“That is the point where an AI-run newsroom outgrows chat.”
— Thorsten Meyer, writing on ThorstenMeyerAI.com
Features Still in Rollout
Meyer’s account does not establish how much of the proposed newsroom workflow is already operating in routine publishing, how often agents follow card changes or mentions correctly, or whether the setup has reduced errors or saved time. The article distinguishes the intended workflow from the features currently running, but the supplied material does not provide independent testing or performance measurements.
The infrastructure plan also has an outstanding step: Meyer says a second machine on standby and hourly backups are planned but not live. The source does not specify a deployment date, service-availability figures or a detailed recovery process. Its description of access controls and change attribution is the project’s own account and has not been independently verified here.
Backup Plans and Wider Rollout
Meyer says the newsroom is still rolling out parts of Thrymvault and identifies a standby machine with hourly backups as a next step. The project’s next practical test will be whether editors and agents can use the board, comments and decision records consistently across the full path from topic selection to publication.
No timetable for the backup deployment or broader rollout is given in the source. Further reporting would be needed to establish which workflow components are live, how access is reviewed over time and what happens when an agent misses an instruction or makes an incorrect change.
Key Questions
What is Thrymvault?
Thrymvault is a workspace for pages, databases and boards that Thorsten Meyer says his network built and hosts on its own machines. It is intended to give editors and AI agents a shared place to coordinate newsroom work.
How do the agents access the workspace?
Meyer describes three access routes: an MCP server with 20 tools, a REST API and a command-line tool. He says agents can enter only through applications approved by a workspace owner.
Can agents delete newsroom material?
According to Meyer’s description of the current agent interface, agents cannot delete anything. Changes are associated with the approved application through which they were made.
Are backups already running on a second machine?
No. Meyer says a standby machine with hourly backups is a planned next step and is not live yet.
Does the article show that Thrymvault improves newsroom accuracy?
No. Meyer explains the system’s intended workflow and its record-keeping features, but the source gives no independent evaluation or accuracy measurements.
Source: ThorstenMeyerAI.com
