🔍 Read the full analysis: How I Made A Shared Desk For AI Agents 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 founder Thorsten Meyer says the group is building Thrymvault, a self-hosted workspace where newsroom staff and AI agents can track stories and editorial changes. The design includes approved agent applications, attributed changes and restrictions on deletion; standby hardware and hourly backups are planned, not live.
Thorsten Meyer, founder of StrongMocha News Group, says the organization is developing Thrymvault, a self-hosted workspace where editors and AI agents can track articles, exchange instructions and record changes. The project addresses a workflow problem Meyer encountered while coordinating nine articles through chat and a code-oriented task tracker: story status and editorial requests were difficult to see in one place.
Meyer describes Thrymvault as a workspace for pages, databases and boards, hosted on StrongMocha’s own machines. Agents can connect through an MCP server with 20 tools, a REST API or a command-line tool. The agent guide is published as plain text and a machine-readable manifest generated from the same tool catalogue as the server, according to Meyer’s account.
In the proposed newsroom workflow, a story begins as a card on an editorial board. The editor decides whether it proceeds; moving it to a kit stage signals an agent to collect sources and prepare research. An agent then drafts the article and updates its board entry with status, a draft link and open questions. Editors can request changes in a comment that mentions the relevant agent application, with the response kept in the same thread.
The workflow ends with a scheduled and published article link on the card. Meyer says a stopped card tells agents to leave the story alone. Editorial decisions, such as a new headline rule, are also recorded in a decisions database with their date, scope and a link to the rule. The account describes how the system is intended to work; it does not establish that every part of this workflow is already deployed.
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 proposal shifts coordination from individual chat threads to a shared record tied to each story. For an editor overseeing agents working in parallel, a board that shows status, drafts and unresolved questions could make it easier to spot stalled work and keep instructions attached to the relevant article.
Attribution also matters for correction and oversight. Meyer says changes carry the name of the approved application used to make them, displayed as “via” that application. That could help staff trace which agent interface made a change, though it does not by itself verify whether the resulting copy or research is accurate. The newsroom still needs editorial review and reliable sourcing.
For readers, the potential benefit is indirect: a clearer internal record may help a publisher identify how a mistake entered a story and respond to it. Meyer presents traceability as a way to support correction, not as evidence that errors will be prevented.
Products Worth Considering

LG UltraGear 32GX870A-B 32-inch 4K UHD OLED Dual-Mode Gaming Monitor

Logitech MX Master 4 Ergonomic Wireless Mouse with Haptic Feedback, Graphite

Logitech MX Keys S Combo Wireless Keyboard and Mouse, Graphite
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer says that on one day in November, StrongMocha used a chat window and a tracker designed for code work to coordinate nine articles. Agents gathered sources, drafted stories and prepared graphics, but Meyer had to ask for status updates. Requests for headline changes depended on the right agent seeing a chat message, and completed explainer pages could not readily be shared as links.
That experience led him to frame the need as a newsroom “desk”: a visible place for each story’s status, attached editorial notes and defined permissions. He argues that the need is heightened when agents work in parallel and do not reliably retain prior instructions unless those instructions are recorded. Thrymvault is the group’s proposed response, rather than a report about an established industry standard or an independent evaluation of AI newsroom systems.
“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 founder
Deployment and Safeguards Still Developing
Meyer’s account distinguishes the system’s design from what is running today but does not provide a full feature-by-feature deployment status. He says a second machine on standby and hourly backups are next steps and are not live yet. The extent of the current rollout, its reliability under routine newsroom use and the timeline for those infrastructure additions are not specified.
The source also does not provide independent testing, security assessments, uptime figures or a detailed explanation of how agent actions are reviewed before publication. It describes approved applications, application-attributed changes and a ban on agent deletion, but does not fully detail permission enforcement, incident handling or how the system handles errors. The claimed workflow and safeguards should therefore be understood as Meyer’s description of his organization’s system, not independently verified findings.
Standby Hardware and Wider Rollout
Meyer identifies the next infrastructure step as adding a standby machine and making hourly backups; both remain planned rather than operational, according to his account. He also says parts of the system are still being rolled out, but gives no schedule or specific launch milestones.
The practical test will be how the workspace performs as agents and editors use it on live stories: whether status stays current, requests reach the right application, and records help staff resolve mistakes. StrongMocha has not supplied results from a formal evaluation. For now, the described development is a newsroom’s internal effort to build a shared control and recordkeeping layer for AI-assisted work.
Key Questions
What is Thrymvault?
Thrymvault is described by Thorsten Meyer as a self-hosted workspace for pages, databases and boards, intended to let StrongMocha editors and AI agents coordinate newsroom work.
How would agents connect to the workspace?
Meyer says agents can use an MCP server with 20 tools, a REST API or a command-line tool. Access is described as limited to applications approved by the workspace owner.
Can AI agents delete newsroom content?
Meyer says agents cannot delete anything. His description does not include an independent audit of how that restriction is enforced.
Is Thrymvault fully deployed?
The source describes a mix of current capabilities and features still being rolled out. A standby machine and hourly backups are explicitly described as not live yet, and no full deployment timeline is provided.
Does the workspace verify that an AI-written article is accurate?
No such verification is established in Meyer’s account. The workspace is intended to track work, instructions and changes; editors still need to check sources and review article accuracy.
Source: ThorstenMeyerAI.com
