TL;DR
StrongMocha News Group is developing Thrymvault as a shared workspace where its editor and AI agents can track stories, communicate and record changes. The November 13 account says core workspace and agent tools are running, while agent keys, newsroom templates and automated mention pickup remain in rollout.
Thorsten Meyer says StrongMocha News Group is building Thrymvault, a shared workspace for the AI agents working across its network of niche and news sites. The system is intended to give editors a visible story board, a place to direct agents and a record of changes; Meyer says some core tools run today, while several newsroom-specific features remain in rollout.
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Meyer describes the need for the workspace through a day when the site’s team moved nine articles through a chat window and a task tracker designed for code work. Agents gathered sources, drafted copy, made graphics and prepared drafts. But the editor had to ask for status updates, send headline changes through chat and could not share a completed explainer as a link. Those details are Meyer’s account of his operation, rather than independently verified performance data.
Thrymvault is a self-hosted workspace for pages, databases and boards, designed to put story status and editorial discussion in one place. In the planned workflow, each story gets a card that moves through stages such as proposed, source kit, draft, scheduled and live. The editor can move the card or leave a comment mentioning an agent; the agent is meant to update its status, respond in the same thread and attach the draft or published link.
Meyer’s status box, dated November 13, 2026, lists workspace pages, databases, board and calendar views, comments with mentions, notifications, templates, version history, two-factor sign-in and nightly backups as running. The agent interface includes an MCP server with 20 tools, a REST API and a guide generated from the tool catalogue. Meyer says agent changes are marked “via” the approved application, and agents cannot delete material. However, the agents do not yet have their own keys, and the ready-made editorial templates and automated mention pickup are still being rolled out.
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 Agent Work
The proposed desk addresses a practical coordination problem: when several agents work on related stories, the editor needs to see what is happening, give instructions in the relevant context and identify which application made a change. A board and attached discussion could make those steps easier to follow than scattered chat messages, particularly when drafts, sources and deadlines overlap.
The change log and access rules also matter for corrections. If an article needs revision, the newsroom can potentially trace who requested an edit, which approved application made it and what changed. That record may support accountability, but it does not establish that an agent’s reporting is accurate or that an editor will catch every error. Meyer presents the system as workflow infrastructure, not proof of improved journalism.
For other organizations using agents, the account illustrates one approach: give automated tools a defined workspace, approved access and a shared record of work. Its practical value will depend on the features being completed and on whether the workflow works reliably in day-to-day use.
Products Worth Considering
Bose QuietComfort Wireless Noise-Cancelling Headphones, White Smoke
Apple Watch SE 3 GPS 44mm Smartwatch
Bose TV Speaker Compact Soundbar with Bluetooth and HDMI-ARC, Black
As an affiliate, we earn on qualifying purchases.
From Chat to a Newsroom Board
Meyer says StrongMocha’s agents previously worked through a chat window and a task tracker intended for software projects. In that setup, story state depended on recent messages, and instructions could scroll out of view. The newsroom’s proposed alternative uses a persistent story card and thread so that status, editor comments and agent responses stay with the work.
Thrymvault is described as resembling a workspace for pages, databases and boards, hosted on StrongMocha’s own machines. The source material says the integration guide and rollout plan inform the design, while the current status is based on a development log and rollout plan. The illustrated board is a depiction of the intended workflow; its templates and automated response to mentions are not yet fully deployed.
The plan includes a standby machine, hourly backups and a scripted switch-over. Meyer says these are next steps rather than live capabilities; the current backup described in the status box is a nightly copy to a second machine. He also says team access depends on naming users and getting the mail server running.
“Agents write fast. What they lack is a desk.”
— Thorsten Meyer, describing the newsroom’s workflow
What the Rollout Has Yet to Prove
The account does not provide independent testing, usage figures or evidence that Thrymvault has improved publishing speed, accuracy or correction rates. The nine-article example is a description of one day’s work, with no comparison baseline or detail on how long the work took.
Several described functions are still planned or being rolled out: keys for StrongMocha’s own agents, editorial templates, automated pickup of mentions about every five minutes, a standby machine with hourly backups and scripted failover, and team access. The source does not give completion dates for these steps. It also does not explain how permissions will be audited over time or how the system handles an incorrect agent edit beyond its stated version history and restore options.
Agent Access and Backup Milestones
Meyer’s rollout plan calls for him to create approved applications and keys for the newsroom’s agents, then introduce templates for the editorial board, reports and decisions. Another planned step is automated mention pickup, with agents checking for relevant comments about every five minutes. These capabilities are described as in progress, with no firm delivery dates supplied.
The next infrastructure milestone is a standby machine with hourly backups and a scripted switch-over. Meyer says those safeguards are not live yet and that team access also depends on user setup and the mail server. The source does not report a launch date for the full newsroom setup, so the next clear measure will be which planned features move into routine use.
Key Questions
What is Thrymvault?
Thrymvault is a self-hosted workspace Meyer says StrongMocha built for pages, databases and boards, with an interface intended for AI agents as well as editors.
What problem is the shared desk intended to solve?
Meyer says chat and a code-focused task tracker made it difficult to see story status, keep editorial instructions attached to drafts and trace changes. Thrymvault is intended to put those activities on a shared story board and thread.
Which features are running now?
The November 13 status lists workspace pages, databases, boards, calendar views, comments, notifications, version history, two-factor sign-in and nightly backups. It also lists an MCP server with 20 tools and a REST API.
Can the agents already use the newsroom setup?
Meyer says agent keys have not yet been issued to StrongMocha’s own agents. The source also says editorial templates and automated mention pickup are still being rolled out.
Does the account show that AI-written stories are more accurate?
No. It describes a workflow and its planned audit trail, but gives no independent evidence about story accuracy, correction rates or publishing speed.
Source: Thorsten Meyer AI
