TL;DR
Thorsten Meyer says his AI-run publishing network is developing Thrymvault, a shared workspace where editors can track stories and agent activity. The November 2026 account describes existing features alongside agent access, templates and automated mention handling that are still being rolled out.
Publisher Thorsten Meyer has described a shared editorial workspace called Thrymvault for his AI-run publishing network, StrongMocha News Group, after finding that chat and a code-focused task tracker made it difficult to monitor stories and steer agents. The system is designed to attach status, editorial comments and a signed history of changes to each story, though Meyer says some agent integrations are still being rolled out.
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Meyer says the need became clear on a day this month when the network moved nine articles through an agent-assisted process. Agents gathered sources, drafted material, created graphics and prepared drafts. Yet the editor had to ask in chat to learn a story’s status, and requests such as changing a headline depended on the appropriate agent seeing and acting on a message. Finished work could not readily be shared as a link.
Thrymvault is a workspace for pages, databases and boards, built and hosted on the publisher’s own hardware. Its proposed editorial workflow gives each story a card that moves through stages such as proposed, source kit, draft, scheduled and live. Editors can leave comments on the card or mention an agent; agents are meant to update status, attach draft links and respond in the same thread.
The development log dated November 13, 2026, says the workspace, comments and mentions, notifications, templates, calendar views, version history, two-factor sign-in and nightly backups are running. The agent interface includes an MCP server with 20 tools and a REST API. However, the publisher’s own agents do not yet have their keys, ready-made editorial templates are still being rolled out, and automatic mention pickup is planned to run about every five minutes. A standby machine with hourly backups and scripted failover is also not yet live.
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 editorial problem: when several agents and people work on related parts of a story, instructions and status updates can become scattered. Keeping each story’s comments and changes together could make it easier for an editor to see what is pending, ask for a correction and identify how a draft changed.
Meyer says agent changes will be labeled “via” the approved application that made them. Workspace owners approve applications and set rights for each key; agents can add and edit but cannot delete. That design could help publishers review work and recover from mistakes, though a signature identifies the application, not necessarily which individual or model operation was responsible.
The account is a report from the system’s builder, not an independent evaluation of reliability or editorial outcomes. It describes a publishing workflow in development. Whether it improves accuracy, speed or accountability in routine use remains to be shown.
Products Worth Considering
EcoFlow DELTA 3 Max Portable Power Station, 2048Wh LFP Battery
Bose TV Speaker (2nd Gen) Compact Soundbar
Bose SoundLink Max Portable Bluetooth Speaker, IP67 Waterproof, Black
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer frames Thrymvault as a response to the limits of using chat for newsroom coordination. A message may describe a story’s state at one moment, but later instructions can be hard to find, and parallel agents may interpret a request differently. Attaching updates to a persistent story record is intended to keep the work and editorial direction together.
The publisher says Thrymvault is a self-hosted workspace with a general shape similar to Notion, combined with board and calendar views and an interface for agents. The described board shows a story moving from proposal through sourcing, drafting and approval to publication. The board templates and automated response to mentions in the accompanying example are explicitly described as still rolling out, so the illustration represents the planned workflow rather than proof that every step is active.
The deployment plan includes a second machine for standby and hourly backups, but the development log says that setup is not live. Nightly backups to a second machine are listed among features already running. Meyer says that until standby is operational, nothing lives only on the desk.
“That is the point where an AI-run newsroom outgrows chat.”
— Thorsten Meyer, describing the problem that prompted the project
Agent Access Is Still Pending
The rollout account does not say when the publisher’s agents will receive their application keys, when the editorial templates will be ready, or when automated mention pickup and standby failover will be fully operational. It also gives no independent measurements of how often agents miss instructions, how accurate their work is, or whether the system reduces correction time.
The described controls establish application-level attribution and restrict deletion, but the account does not explain how disputes about an agent’s actions would be resolved or provide security testing results. These are open questions about a system whose agent integrations remain in rollout.
Completing the Newsroom Rollout
According to the rollout plan, next steps include issuing keys to the publisher’s agents, completing editorial board and reporting templates, activating regular checks for comments that mention agents, and setting up a standby machine with hourly backups and a scripted switch-over. Team access is planned once the publisher names participants and the mail server is running.
The next useful evidence will be whether those integrations are put into routine use and whether story records make editorial handoffs and corrections easier to follow. Meyer has not provided a completion date for the remaining rollout work.
Key Questions
What is Thrymvault?
Thrymvault is a self-hosted workspace developed for pages, databases and boards, including a proposed editorial board for tracking AI-assisted stories.
What problem is it meant to address?
Meyer says chat and a code-focused task tracker made it hard to see story status, keep editorial instructions attached to a story and trace changes. Thrymvault is designed to put those updates on a shared story card.
Can agents use the workspace now?
The workspace and an agent interface are reported as running, but Meyer says his own agents do not yet have their application keys. Several workflow features, including templates and automated mention pickup, are still being rolled out.
How are agent changes attributed?
The design labels changes with “via” and the approved application name. Owners approve applications and set permissions for keys. The stated guardrails also prevent agents from deleting content.
Are backups and failover fully in place?
Meyer reports nightly backups copied to a second machine as running. A separate standby setup with hourly backups and scripted switch-over is still planned, according to the November 13, 2026, rollout status.
Source: Thorsten Meyer AI
