🔍 Read the full analysis: Giving AI Agents A Common Workspace At StrongMocha News Group 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
StrongMocha News Group says it is using Thrymvault as a shared workspace for AI agents handling newsroom tasks, replacing chat and a code-focused task tracker as the main way to coordinate work. The system is designed around approved agent applications, traceable changes and limits on what agents can do, but its backup plan is not yet live and the article distinguishes the design from features already operating.
StrongMocha News Group says it is giving its AI agents a shared newsroom workspace called Thrymvault, after coordinating work through chat and a code-oriented task tracker left story status and editorial changes difficult to follow. The workspace is built and hosted on the group’s own machines, with agent access limited to approved applications; its author says the setup is intended to make work and changes easier to track.
In an article dated November 13, 2026, Thorsten Meyer described a day when agents helped produce nine articles for the site by gathering sources, drafting, making graphics and preparing copy. He said editors had to ask the chat to find out where stories stood, and had to rely on the right agent seeing a message when a headline needed changing. Completed explainer pages could not be shared as links, he wrote.
Thrymvault is described as a workspace for pages, databases and boards, with a general layout Meyer compares to Notion. Agents can connect through an MCP server with 20 tools, a REST API or a command-line tool. The agent guide is published in plain text and as a machine-readable manifest, generated from the same tool catalogue as the server, according to the article.
The stated access model requires a workspace owner to approve an application before an agent can use it. Each agent key acts with the rights of the person who created it, within one workspace, and no agent can delete content, Meyer said. Changes carry the name of the application used, displayed as “via” that application. These are descriptions from the system’s creator and documentation, not an independent audit of the controls.
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 proposed change addresses a practical problem as AI agents take on parallel newsroom tasks: chat messages can be missed, instructions can become separated from a story, and editors may struggle to identify who made a particular change. A shared board can keep status, draft links and open questions beside the story rather than spread across conversations.
For readers, Meyer argues, a record of who drafted a story, requested an edit and applied a rule could make errors easier to investigate and correct. The workspace does not by itself establish that reporting is accurate or that every edit is appropriate. Its potential value is in making parts of the production process more visible and attributable, provided the records are complete and the controls work as described.
The approach also reflects a broader operational choice: rather than treating agents as anonymous users of a chat, StrongMocha is assigning them access through named applications and limiting their permissions. Whether that model improves reliability or editorial oversight in routine use remains to be seen.
Products Worth Considering
DJI Mini 5 Pro Fly More Combo with DJI RC 2
EcoFlow DELTA 3 Max Portable Power Station, 2048Wh LFP Battery
Jackery Explorer 1000 v2 Portable Power Station
As an affiliate, we earn on qualifying purchases.
From Chat to Story Boards
Meyer’s account begins with a newsroom workflow managed through a chat window and a task tracker designed for code work. In that arrangement, he said, the latest message effectively determined a story’s status; instructions could scroll out of view, and parallel agents might interpret the same message differently. The nine-article workday is his example of why he believes that arrangement no longer fits the group’s needs.
The Thrymvault workflow is presented as a sequence: an editor or agent proposes a topic card; the editor decides whether it proceeds; moving it to a “Kit” stage prompts an editorial agent to gather primary sources and check figures; the agent drafts and records its status and questions on the board. Editors can leave a comment mentioning an agent application, while the agent’s reply and changes remain in the story thread. A card marked “stopped” is meant to signal agents to leave the work alone.
Those card movements are workflow agreements, not automatic software triggers, Meyer said. The article also describes a “Decisions” database for recording policy changes, including their wording, date and scope. The rule itself remains where agents read it; the database records the decision and links to the rule.
“Agents write fast. What they lack is a desk: one place where their work is visible, where the editor steers, and where every change can be traced back to whoever made it.”
— Thorsten Meyer, StrongMocha News Group
What Is Live and What Is Planned
The source article distinguishes the intended workflow from the capabilities already running, but the supplied material does not fully enumerate which parts of the newsroom process are in production today. It says the workspace runs on the group’s own hardware and describes the agent interface as built, while also noting that some elements are still being rolled out.
A second machine on standby and hourly backups are described as the next step, not a live feature. The article does not provide independent uptime, security or performance testing, nor does it say how often agents miss instructions or how editors verify the source kits and drafts. It also does not identify the specific applications currently approved or give a detailed account of how access is revoked.
The claims about traceability and permissions come from Meyer and Thrymvault’s own guide and development documentation, as cited in the article. No outside assessment is included, so readers cannot determine from this account alone how the controls perform under failure or misuse.
Backup Plans and Wider Rollout
Meyer says the next infrastructure step is adding a standby machine and hourly backups. He does not give a deployment date. The newsroom’s described process also depends on agents keeping their board entries current and responding to editor comments, so continued rollout will show how consistently those steps work in practice.
The article does not announce an external launch date, availability for other organizations or measured results from the new workflow. For now, the next developments to watch are the completion of the backup plan, further rollout of the agent-facing tools and evidence about whether story records remain useful and accurate during day-to-day production.
Key Questions
What is Thrymvault?
Thrymvault is a self-hosted workspace for pages, databases and boards that StrongMocha says it is using to coordinate editors and AI agents.
How do agents access the workspace?
According to Meyer, agents connect through an MCP server, REST API or command-line tool, and can enter only through applications approved by a workspace owner.
Can agents delete newsroom content?
Meyer says agents cannot delete anything. He also says agent keys are limited to the rights of the person who created them and to one workspace.
Is the backup system already running?
No. The article describes a second machine on standby and hourly backups as a next step, not as a live part of the system.
Does Thrymvault automatically move stories through the workflow?
Not as described. Meyer says moving a card represents an agreement agents follow; it is not a software switch that automatically starts the next stage.
Source: ThorstenMeyerAI.com
