Version Coauthor
Every element save that an agent performs is attributed twice: the version's user stays the human who owns the chat session, and the version additionally carries a coauthor that names the agent. This makes agent-driven changes auditable in the Versions tab of Pimcore Studio, which shows a "Co-authored by" tag on every stamped version.
What gets stored
| Field | Value |
|---|---|
coauthorType | agent |
coauthor | The agent name of the chat session, for example data-management |
The agent name comes from the persisted chat session (AgentSession::agentName), resolved through the trusted
MCP token binding. For MCP tool calls the token reference identifies the session; for proposal approvals the
session id comes from the proposal payload. In both cases the session lookup is scoped to the authenticated
user, so a coauthor can only ever name an agent from one of the user's own sessions.
When stamping happens
- MCP tool calls: every request authenticated with a chat-session MCP token activates the coauthor context for the duration of the request. All element writes performed by MCP tools during that request stamp their versions, including tools added in the future.
- HITL proposal approvals: when a user approves a proposal, the resolver applies the change with the coauthor context active for the session that produced the proposal.
Saves performed by the same user outside a chat session are not stamped, and stamping never overrides a coauthor that was set explicitly. With pimcore/pimcore#19712, a job that is queued inside an MCP tool call (for example an automation action) carries the coauthor of that call into its worker.
External MCP clients
External MCP clients do not reach this bundle's endpoints (/pimcore-mcp/agent/* accept the chat's MCP access token
only). They connect through a configured MCP server of the Studio Backend bundle
(/pimcore-mcp/studio/<slug>), which stamps every direct write itself:
| Field | Value |
|---|---|
coauthorType | mcp-server (shown as "MCP server" in the Versions tab) |
coauthor | The server's URL slug, for example product-data |
The stamp is set on the server side for every tool call of that server. A tool never sets a coauthor, and the name
the client sends in its MCP initialize handshake is never used (the former mcp-client type is gone; versions that
already carry it keep their value). Inside any MCP tool call, coauthorType and coauthor in a tool's data are
ignored: the version gets the MCP coauthor, or none when stamping is switched off or no chat session is found.
Configuration
Stamping is enabled by default. Disable it project-wide:
pimcore_agent:
version_coauthor:
enabled: false
Related
- The underlying mechanism (
CoauthorContextInterface) is part of Pimcore core, see the Versioning chapter of the Pimcore documentation. - HITL Proposals
- Built-in Pimcore MCP Servers