🔍 Read the full analysis: A Shared Desk Brings My AI Agents Into One Workspace 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 StrongMocha News Group is moving AI newsroom work from chat and a code-oriented task tracker into Thrymvault, a self-hosted shared workspace. The design gives agents approved, limited access and records which application made changes, but backup redundancy is still planned rather than live.
Thorsten Meyer says his StrongMocha News Group is giving its AI newsroom agents a shared workspace called Thrymvault, replacing a workflow that relied on chat and a code-oriented task tracker. The workspace is designed to keep story status, editorial instructions and agent changes in one place, with access limited to approved applications; Meyer says some planned infrastructure, including a standby machine, is not yet live.
Meyer described the change in a November 13 article on ThorstenMeyerAI.com, drawing on a day this month when he said the network steered nine articles through a chat window and a task tracker built for code work. Agents gathered sources, drafted copy and prepared graphics, but Meyer said he had to ask for updates, send headline instructions through chat and could not share a completed explainer as a link. He presented that experience as the reason to build a dedicated editorial desk.
Thrymvault is a workspace for pages, databases and boards, built and hosted on the group’s own machines. According to Meyer’s description, agents can use 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, he said, so its instructions match the tools available. These details are based on Meyer’s account and cited Thrymvault documentation; the article does not provide an independent technical audit.
The proposed story workflow starts with a topic card on an editorial board. An editor decides whether it moves forward; moving it to a “Kit” stage prompts an editorial agent to gather sources and prepare a source kit. The agent then drafts the story and updates its board entry with status, a draft link and open questions. Editors can request changes in a comment thread that mentions the relevant agent application. After publication, the card is meant to retain a link to the live article.
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 change addresses a coordination problem that arises when several agents and an editor work on related material in parallel. In chat, Meyer argues, a story’s status can be buried in earlier messages, instructions may be interpreted differently and it can be hard to identify who made a change. A board that keeps status and comments attached to each story could make work easier to review and redirect.
For readers, Meyer’s stated rationale is traceability: a record of who drafted material, which application changed it and what editorial rule applied could help the newsroom investigate errors and make corrections. That benefit is a design goal, not an independently demonstrated outcome. The article does not report comparative accuracy, correction rates or productivity measurements for the new system.
The approach also points to a practical choice for organizations using agents: whether to coordinate them in general-purpose chat or in a workspace with visible assignments, defined permissions and a persistent record. Thrymvault is Meyer’s own system, so its reported capabilities should not be treated as evidence that all agent workspaces offer the same controls.
Products Worth Considering
Bose QuietComfort Ultra Headphones (2nd Gen), Wireless Noise-Cancelling Over-Ear Headphones with Spatial Audio, Driftwood Sand
Logitech MX Master 4 Ergonomic Wireless Mouse with Haptic Feedback, Graphite
DJI Osmo Mobile 8 Phone Gimbal with Mic Mini Transmitter, Infinity Black
As an affiliate, we earn on qualifying purchases.
From Chat to an Editorial Board
Meyer writes that StrongMocha News Group operates a network of niche and news sites with AI agents. Before Thrymvault, he says the group handled a day’s work on nine articles using chat and a task tracker intended for code projects. The account provides the immediate operational background for the workspace, rather than a broader evaluation of AI journalism.
In Meyer’s design, moving a card between stages communicates an editorial decision to the agents; he says the move itself is an agreement the agents follow, not a software switch that automatically starts a process. New rules, such as a headline guideline, are recorded in a Decisions database with wording, date, scope and a link to the rule. The rule remains where agents read it, while the database records the decision.
Meyer says agent changes are associated with the name of the approved application used, displayed as “via” that application. Access is granted through applications approved by a workspace owner; each key is limited to one workspace and cannot exceed the application’s permissions. He also says agents cannot delete anything. These are descriptions in the project’s integration guide and development log as cited in his article, not findings from an outside security review.
“When I wanted to know where a story stood, I had to ask.”
— Thorsten Meyer, describing the newsroom’s earlier workflow
Rollout and Safeguards Still Developing
Meyer distinguishes between the system’s intended design and what is already running, but the supplied account does not give a detailed feature-by-feature rollout status. He says the workspace currently runs on the group’s own hardware, while a second machine on standby and hourly backups are next steps, not live services. The article does not specify when those measures will be deployed.
It is also not clear from the account whether the complete editorial workflow is already operating across the network, how many agents or sites use it, or how consistently agents follow card movements and comments. Meyer describes moving a card as an agreement agents follow, rather than an automatic software trigger. No independent security assessment, uptime data, usage figures or measured comparison with the earlier workflow is provided.
The source is a first-person account by the system’s creator and operator. Its descriptions of permissions, audit trails and agent tools are attributable to Meyer and the project documentation he cites; they have not been independently verified in the material provided.
Backup Plans and Rollout Status
Meyer identifies the standby machine and hourly backups as upcoming work. He does not state a delivery date. The next point for readers to watch is whether those planned protections become operational and whether the described approval and audit controls are documented as the workspace expands.
Further reporting would also need to establish how much of the workflow is in routine use, what happens when an agent misses or misreads an instruction, and whether the change improves correction handling or editorial efficiency. Meyer’s article describes the design and his reasons for adopting it, but does not provide results from a formal evaluation.
Key Questions
What is Thrymvault?
Thrymvault is a pages, databases and boards workspace that Meyer says StrongMocha News Group builds and hosts on its own machines. It is intended to give editors and AI agents a shared place to track newsroom work.
How are agents supposed to work in the workspace?
According to Meyer, agents can access Thrymvault through an MCP server, REST API or command-line tool. They are meant to update story cards, prepare drafts and respond to editorial comments through approved applications.
What controls does Meyer say are in place?
Meyer says agents enter only through applications approved by a workspace owner, changes identify the application used, and agents cannot delete content. He also says keys are restricted to one workspace and to the permissions of their application. These claims are based on his account and project documentation, not an independent audit.
Is the backup system already operating?
No. Meyer says the workspace runs on the group’s own hardware, but a second machine on standby and hourly backups are planned and are not live yet. He gives no deployment date.
Has Thrymvault been shown to improve newsroom results?
The account describes the system’s design and the workflow problem it aims to address. It does not report measured effects on accuracy, speed, corrections or productivity, so those outcomes remain unestablished.
Source: ThorstenMeyerAI.com
