TL;DR
Thorsten Meyer says StrongMocha News Group is building Thrymvault into a shared workspace for its AI-assisted newsroom, with story boards, comments and a record of changes. The workspace and agent tools are running, but agent access, editorial templates and automated mention handling are still being rolled out.
StrongMocha News Group is rolling out Thrymvault, a self-hosted workspace intended to let editors and AI agents track stories, instructions and changes in one place. Thorsten Meyer said on November 13 that the workspace and its agent interface are running, while agent keys, editorial templates and automated responses to mentions remain in rollout.
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Meyer described the need for a shared workspace after a day in which agents handled nine articles through a chat window and a task tracker designed for code work. He said editors had to ask agents for updates, send headline changes through chat and lacked a shareable link to a completed explainer page. The account is Meyer’s description of his newsroom’s workflow; the source does not provide independent measurements of how often these problems occur.
Thrymvault is a workspace for pages, databases and boards that StrongMocha built and runs on its own machines. Its planned editorial board gives each story a card that can move through proposed, source-kit, draft, scheduled and live stages. Editors can leave instructions in a card’s discussion thread, while agents are intended to update status and attach draft or published links there.
Meyer says the workspace currently includes board, calendar and database views, comments with mentions, notifications, templates, version history, two-factor sign-in and a nightly backup copied to another machine. The agent interface includes an MCP server with 20 tools, a REST API and an agent guide generated from its tool catalogue. These features describe the system available as of November 13, according to Meyer’s development log and rollout plan.
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 Stories
A shared board could make it easier for an editor to see which stories need attention and where drafts stand, without reconstructing progress from separate chat threads. Keeping a comment attached to its story also gives an agent a place to receive a correction or answer a question. That matters in a newsroom where multiple agents may work at once and an editor needs to review work before publication.
The proposed record of changes addresses another practical concern: accountability. Meyer says changes made through an agent are labeled with the name of its approved application, and the system does not allow agents to delete content. If those controls operate as described, the history could help staff trace who changed a draft and which application made the change. The source does not report an independent security review or explain how the controls have been tested.
For readers, a visible record may help the newsroom investigate and correct errors. It does not establish that stories are accurate or that an editor has reviewed every change. Those outcomes depend on editorial practice as well as the workspace.
Products Worth Considering
Apple Watch SE 3 GPS 44mm Smartwatch
Bose TV Speaker (2nd Gen) Compact Soundbar
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer frames Thrymvault as a response to StrongMocha’s use of AI agents across a network of niche and news sites. In his account, chat works for individual exchanges but leaves the latest story status buried in messages. A task tracker made for code work did not give the newsroom a suitable place to share finished pages or keep editorial instructions with a story.
The alternative draws on a familiar newsroom structure: a board that displays story status, with notes and decisions attached to each item. Thrymvault’s general layout may feel familiar to people who use Notion, Meyer writes, but it is built and hosted on the group’s own hardware. The article presents the system as a design for StrongMocha’s newsroom, not as a report of a finished, generally available product.
The distinction between available features and planned rollout is material. The source says a nightly backup already goes to a second machine, but a separate standby machine with hourly backups and scripted switch-over is still planned. It also says nothing lives only on the desk until that standby setup is running.
“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, describing the newsroom’s workflow
What the Rollout Has Yet to Prove
Thrymvault is not yet operating with all the workflow features Meyer describes. The newsroom’s agents do not yet have their own application keys, and ready-made templates for editorial boards, reports and decisions are still being rolled out. Automated pickup of mentions, intended to prompt agent responses about every five minutes, is also pending.
The source does not specify when those steps will finish, how many staff or agents will use the system, or whether the setup has been evaluated against the chat-based process. Team access is also pending while Meyer identifies the people to add and the mail server is brought online. The reported controls and backup arrangements come from Meyer’s own development log and rollout plan, not an external audit.
Agent Access and Backup Plans
The next steps listed by Meyer are to create approved applications and keys for StrongMocha’s agents, finish the editorial templates, and enable agents to pick up mentions and reply in the relevant thread. He also plans to add a standby machine with hourly backups and a scripted switch-over, then enable team access after identifying users and bringing the mail server online.
Meyer has not given dates for these milestones. Until they are complete, the workspace remains a partly rolled-out newsroom system, and the described board workflow is a design rather than a fully deployed process across the group.
Key Questions
What is Thrymvault?
Thrymvault is a workspace built and hosted on StrongMocha’s own machines. Meyer describes it as a place for pages, databases, boards, comments and AI-agent tools.
Is the newsroom workflow fully live?
No. Meyer says the workspace and agent interface are running, but agents do not yet have their own keys. Editorial templates and automated handling of mentions are also still being rolled out.
How are agent changes identified?
Meyer says changes made through an approved agent application are labeled with “via” followed by that application’s name. He also says agents cannot delete content.
What backup system is in place?
The status report says a nightly backup is copied to a second machine. A standby machine with hourly backups and a scripted switch-over is planned, but is not yet live.
When will the remaining features be ready?
Meyer has not provided dates for completing the rollout. Agent keys, templates, mention handling, standby backups and team access are listed as pending or in progress.
Source: Thorsten Meyer AI
