🔍 Read the full analysis: Could Thrymvault Be Part Of A Shared Workspace For AI Agents? on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Thorsten Meyer says his StrongMocha News Group is using Thrymvault as a shared workspace for AI agents and editors, replacing chat and code-focused task tracking with story cards, reports and comments. The system is designed to attribute agent changes to approved applications and prevent agents from deleting content, but parts of the setup remain in development.
Thorsten Meyer says his StrongMocha News Group is introducing Thrymvault as a shared workspace where editors and AI agents can track newsroom stories, drafts and decisions. The development addresses a practical problem Meyer describes from his own publishing operation: chat and a code-oriented task tracker did not give him a clear, persistent view of what agents were doing or an easy way to steer their work.
Thrymvault is a workspace for pages, databases and boards that Meyer says his group built and hosts on its own machines. In his November 13 account, he describes using agents to gather sources, draft stories, create graphics and prepare articles. He says that in one day this month, the team handled nine articles through a chat window and a task tracker. The account does not independently document or verify that production figure.
The proposed newsroom workflow puts each story on an editorial board as a card. An editor can move a card through stages such as topic, source kit and draft, while agents update their status, attach draft links and record open questions. Meyer says an editor can request a change in a card’s comment thread by mentioning the relevant agent application. The story card is intended to retain the discussion and link to the agent’s report.
According to Meyer’s description of the agent guide and integration documentation, agents can connect through an MCP server with 20 tools, a REST API or a command-line tool. The design calls for workspace-owner approval of agent applications, one key per machine and changes labeled with the application that made them. Meyer also says agents cannot delete content. These are descriptions of the system’s intended or documented controls; the article does not report an independent security review.
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 Desk for Agent Work
The change matters because AI-assisted publishing can involve several agents and editorial decisions moving in parallel. Meyer’s account highlights a basic operational issue: a chat transcript may contain instructions, but it does not necessarily provide a lasting, shared record of a story’s status, the latest editorial decision or who changed a draft. A board tied to the story could make those details easier for an editor to see and correct.
Attribution and limited access are also relevant to accountability. If each change records the approved application behind it, a newsroom may have a clearer trail for investigating errors and identifying where a revision came from. That could help an editor review how a story was produced. It does not, by itself, establish that the work is accurate, that the controls cannot be bypassed, or that an agent followed its instructions.
For other organizations experimenting with agents, Thrymvault offers a particular approach rather than evidence of a general solution: keep work in a shared system, give applications bounded access, and make editorial decisions visible. The practical value will depend on how reliably the workflow works in day-to-day use and whether it fits the publishing systems and oversight needs of other teams.
Products Worth Considering
Jackery Explorer 1000 v2 Portable Power Station
Samsung 37-inch Odyssey G7 Curved 4K UHD Gaming Monitor (G75F)
Amazon Kindle Scribe Colorsoft 64GB with 11-Inch Color Display and Premium Pen, Graphite
As an affiliate, we earn on qualifying purchases.
From Chat Threads to Story Cards
Meyer frames Thrymvault as a response to the limits he encountered while coordinating agents through chat and a task tracker designed for software work. In his description, story status depended on asking an agent, instructions could scroll out of view, and a completed explainer page could not readily be shared as a link. Those are his observations about the group’s workflow, not an independently reported comparison of collaboration products.
In the planned process, a topic first appears on the board, and Meyer decides whether it advances. Moving a card from “Topic” to “Kit” signals that an editorial agent should gather primary sources and check figures; Meyer says the move is an agreement agents follow, not an automatic software trigger. An agent then drafts and reports progress on the card. Once the article is scheduled and published through the group’s publishing system, the card is meant to retain the live link.
Separate from individual stories, a Decisions database is intended to record changes in working rules, including the wording, date, scope and link to the rule being changed. Meyer says the rule itself remains where agents can read it, while the database records the decision and points to it. This aims to connect editorial choices with the instructions that govern later work.
“AI-run newsroom outgrows chat.”
— Thorsten Meyer, describing his newsroom workflow
Rollout and Safeguards Still Developing
Meyer says the workspace runs on the group’s own machines, but a second machine on standby and hourly backups are planned rather than live. The article does not provide a rollout schedule or say which newsroom functions are already in routine production. It distinguishes the intended workflow from what is running today, but the supplied material does not give a full feature-by-feature status.
Other details are also not established in the account: there are no independent tests of the access controls, no security audit, and no evidence about how well the system handles mistakes, conflicting agent instructions or outages. The statement that no agent can delete anything describes the stated design; implementation details and verification are not provided. Meyer also does not give comparative measures for speed, accuracy or cost against the previous workflow.
The Next Steps for Thrymvault
The next stated infrastructure step is adding a standby machine and hourly backups. Meyer’s description also points to continued rollout of the newsroom workflow, including story boards, agent reports, comment-based edits and the decisions database. He does not specify dates for those steps.
Readers and potential users will be able to judge the system more fully as the group reports what is already running, what remains in development and how the controls perform in practice. Until then, Thrymvault is best understood as Meyer’s account of a workspace being introduced for his own AI-supported newsroom, not as a broadly validated platform or a proven model for every newsroom.
Key Questions
What is Thrymvault?
Thrymvault is a workspace for pages, databases and boards that Thorsten Meyer says his group built and hosts on its own machines. He describes it as a shared desk for newsroom editors and AI agents.
How would agents use the newsroom workspace?
Meyer says agents can connect through an MCP server, a REST API or a command-line tool. In the planned workflow, agents update story cards, attach draft links and respond to editor comments.
What controls does Meyer say are planned?
According to Meyer, workspace owners approve agent applications, each machine uses its own key, changes are attributed to the application involved, and agents cannot delete content. The source does not include an independent security review of these controls.
Is Thrymvault’s full setup already running?
Not according to the account. Meyer says a standby machine and hourly backups are still planned, and does not provide a complete feature-by-feature rollout status or schedule.
Does the account show that Thrymvault improves story accuracy?
No comparative accuracy results are reported. Meyer argues that a persistent record could make work easier to review and correct, but the material does not provide measured results or independent verification.
Source: ThorstenMeyerAI.com
