🔍 Read the full analysis: From Separate Agents To A Shared Desk: My AI Workflow on ThorstenMeyerAI.com
Get the latest gadgets 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 AI-run publishing network is building Thrymvault, a shared workspace to track stories, agent tasks and editorial decisions. It is designed to make changes attributable to approved applications, but some infrastructure plans remain in development.
Thorsten Meyer says his StrongMocha News Group is building Thrymvault, a shared workspace for coordinating AI agents that gather sources, draft articles and prepare graphics. The project aims to give editors a visible record of story status and changes, replacing a workflow Meyer says relied on chat and a code-focused task tracker.
Meyer describes Thrymvault as a workspace for pages, databases and boards, built and hosted on the group’s own machines. He says agents can access it through an MCP server with 20 tools, a REST API or a command-line tool. The agent guide is generated from the same tool catalogue as the server, according to the article, so its instructions are intended to match the available tools.
In the proposed newsroom workflow, an editor or agent puts a topic on a board. The editor decides whether it proceeds; moving a card to a “Kit” stage signals the editorial agent to collect sources and prepare a source kit. The agent then drafts the article, updates its status and records open questions on the board. Editors can request changes in a thread by mentioning the relevant agent application, with the response recorded there.
Meyer says agents enter only through applications approved by a workspace owner, and changes are attributed to the application used. He also says agents cannot delete material. The article describes a planned record for editorial decisions, including when a rule was made and which existing rule it affects. These are descriptions of the system’s design and intended workflow, not independent evidence of newsroom performance.
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 Workflow for AI Editors
A shared board could make parallel agent work easier for an editor to monitor than separate chat threads. Story status, draft links, questions and requests for revisions would remain attached to the same card, according to Meyer, giving staff a place to see what is pending without asking an agent for an update.
The project also focuses on accountability and access control. Recording which approved application made a change may help editors investigate errors or identify how a draft was altered. Meyer argues that a traceable record makes correction easier, though the article does not report measured results or describe an independent audit of the system.
For readers, the potential relevance is indirect: a clearer internal record could help a newsroom review and correct work. Thrymvault’s existence alone does not establish that articles are more accurate, that errors are prevented, or that the workflow is faster.
Popular right now
Hisense 75-Inch U7 Mini-LED ULED 4K UHD Smart Google TV (75U7SG)
Ninja Foodi DualZone Smart XL Air Fryer, 10 Qt, 6-in-1, Black (DZ550)
Vitamix VX1 Professional-Grade Blender, 64 oz, Black
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer’s account begins with a day in which his team handled nine articles using a chat window and a task tracker designed for code work. He says staff had to ask agents for status, send headline changes through chat and could not share a completed explainer as a link. The article presents those problems as the reason for building a dedicated desk.
Thrymvault is described as having a general shape familiar to users of Notion, but with agent access through limited integrations. Meyer says each access key acts with the rights of the person who created it, within one workspace, and cannot grant more rights than the application allows. The article also distinguishes between what is running and what is planned: a second machine on standby and hourly backups are described as next steps, not live features.
““Agents write fast. What they lack is a desk.””
— Thorsten Meyer, in the November 13, 2026 article
What Is Live and What Is Planned
The article does not provide an independent technical review, usage data or evidence that the workflow has improved accuracy, speed or correction rates. It also does not specify how often the planned board-and-comment process is already being used across the group’s sites, or whether every part of the described workflow is operational.
Meyer says a standby machine and hourly backups are not live yet. The article does not give a completion date. It also does not detail how the team will handle disputed agent changes, mistakes in source kits, or access being revoked after an application is approved.
Backup Plans and Rollout
Meyer says the next infrastructure step is adding a second machine on standby and hourly backups. The article does not give a schedule for that work. It also indicates that parts of Thrymvault are still being rolled out, but does not set out a full deployment timetable or identify a launch date for each feature.
The next meaningful evidence will be practical: whether the workflow is used consistently, how changes are reviewed, and whether the promised records help editors track and correct work. For now, the published account describes the system’s design and the author’s plans rather than a measured evaluation.
Key Questions
What is Thrymvault?
Thrymvault is a self-hosted workspace for pages, databases and boards that Meyer says is being developed to coordinate AI agents and editors.
How do AI 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 limited to applications approved by the workspace owner, according to his article.
Can agents delete newsroom material?
Meyer says agents cannot delete anything. The article does not include an independent technical verification of that restriction.
Is the system fully deployed?
The article describes a mix of existing capabilities and work still being rolled out. Meyer says the planned standby machine and hourly backups are not live yet, and gives no completion date.
Does Thrymvault show that AI-written articles are more accurate?
No performance results are reported. Meyer describes a workflow intended to make tasks and changes more visible, but the article does not establish that it improves accuracy or prevents errors.
Source: ThorstenMeyerAI.com
