Follow external AI work in Chats
Chats shows external clients that used dtxWiki through MCP. MCP is the connection that lets a supported AI client read or propose changes to workspace content. See MCP connections to set it up.
You need Editor or Owner access to the Chats surface. For those roles, Chats is always under Knowledge in the left navigation. Unlike Ask and Agent, it is not an experimental menu and needs no Labs setting.
Understand what is recorded
Chats records MCP tool calls, inputs and results retained under the trace policy, and linked items. It does not receive a separate copy of the message you typed into the external client. It is tool activity, not a full chat transcript.
| Screen | Purpose |
|---|---|
| Ask | Questions and evidence-based answers inside dtxWiki. An experimental menu, shown after you turn on Settings → Labs → Show Ask menu. |
| Chats | Provenance for external MCP sessions and their tools. |
| Activity | Workspace events across changes, reviews, tools, and jobs. |
For example, an external client may search for Launch plan, read it, and propose a revised draft. Chats can show that sequence and link the affected page. It cannot reconstruct every sentence exchanged in the external app.
Inspect a session
- Open Chats.
- Filter by Client, Period, or Writes only. Use the title/summary search if you remember the topic.
- Open a chat. Session info (times, call counts, and the client) and, when the chat touched documents, Linked artifacts are collapsed at the top; open them when you need them. Work flow lists the steps; select a step to see its calls, including errors or refused operations.
- On a call card, use the Inputs, Result, Linked, and Metadata tabs. A failed call opens on Result, and a write call opens on Inputs. See Read a call's inputs and metadata.
- Follow a linked Context or Library item to inspect its current accessible content.
- For a proposed edit, use Review to check what became published.
A write call does not by itself prove that a page was published. A refused call is evidence that an operation did not pass its checks. Tool-level Technical inputs can help an administrator diagnose a problem, but the page and review state determine the knowledge readers receive.
Conversations can group related sessions when the external client preserves the conversation token returned by dtxWiki. Clients that do not carry that token may create separate session records for related activity.
Read linked artifacts
An artifact here is a linked workspace item, such as a Context page or Library source. In v0.2.1, Linked artifacts in chat detail groups up to the 100 most recent link rows and shows each item once, with separate badges for actions such as Created, Edited, Cited, Referenced, or Search match. A badge such as Edited ×3 means the edit link was recorded three times; it does not mean three different pages or three published versions. The section's artifact count counts distinct items within those rows, while its action summary can count the same item under several actions. These counts cover the returned recent links, rather than the chat's full history.
The Chats list samples up to the four most recent link rows, excluding Search match links. It names the most recently linked item and adds and more when other items appear in that sample. This hint is not the total number of linked documents. Open the chat and expand Linked artifacts for its item cards; choose Show all … artifacts if offered to see all items represented in the detail's recent 100 link rows. Follow a card to open the item's current accessible content, and use the call's version labels and page History to check which revision the client used.
This summary groups resources from the session's recent link rows. Inside an individual call's Linked tab, links still appear by action, so the same item can appear for more than one action. Use that tab when you need to understand the specific call.
Read a call's inputs and metadata
The Inputs tab shows what the AI client sent, from top to bottom:
- The call's main facts, such as a link to the requested document and its version labels.
- Technical inputs, with a readable name for each field. Workspace comes first and shows the workspace name with a shortened ID, or Workspace name unavailable when the ID does not match one of your workspaces. Type values, such as Context Page, appear as small labels, and long text such as Body gets its own block.
- Raw request details at the end, collapsed: page, version, and other IDs. Open it only when you need an exact ID, for example for an administrator.
Version labels. Input version, Base version, Editing version, and Cited version show a number such as v3, the same numbering as the page's History. It is the version the AI client named in that call, not necessarily the page's current version, so compare it with History before assuming an edit reached readers. A label appears only when that version is available and you may see it; for example, another author's private MCP editing version is never shown.
Overwrite protection number. This number, inside Raw request details, identifies the state of the AI client's private MCP edit that the request was based on. If the draft changed after the client read it, dtxWiki saves nothing instead of overwriting newer text: the call shows the status Conflict, the error Outdated base version, and No changes made. It is not a page version.
IDs. Long IDs are shortened to their first and last characters. Select a shortened ID to show or hide the full value, or use the copy icon beside it (Copy full ID: …). If the browser blocks copying, dtxWiki selects the full ID instead; press Ctrl+C (⌘C on macOS). These controls appear on Workspace, in Raw request details, and on Call ID.
The Metadata tab lists Status, Started, Completed, Latency, Error, Schema, Raw headline (the full technical summary), and finally Call ID. When you ask an administrator to investigate a call, copy its Call ID.
Rename, archive, and restore
Use Edit title in chat detail to make a session easier to find. A title is one line of up to 120 characters and cannot be blank. The field starts with the title shown, so shorten a long automatic title before you choose Save title; longer text shows Use 120 characters or fewer. and nothing is saved. Archive hides it from the default list; it is not deletion of the linked pages. Turn on Show archived and use Restore to return it to the list.
If there are no Chats
- Check the selected workspace and period filter.
- Turn off Writes only to include read/search sessions.
- Confirm that the external client actually called dtxWiki MCP tools. Ordinary conversation in the external app does not create a record here. An empty list offers Open MCP setup, which opens Settings → MCP access.
- Confirm your role and the connection's workspace grant with the Owner.
Review connection access before sharing trace details outside the workspace. Retained technical inputs, copied IDs, and Raw request details can themselves contain workspace material. Give an administrator the Call ID rather than pasting whole inputs into public channels.
Read 0.2 MCP edit results
An edit can return version IDs, a content hash, review state and a summary of changed regions instead of the whole body. Read the returned version when you need to inspect the body. Reopening this chat's own still-pending submission can reuse it and replace its review; other chats, authors and already-decided submissions are separate.
A Register references call actually adds or removes references on an editing version. A successful call does not mean the page was published: check submission, review and the current published version. See contract revision 29.
Implementation reference: Chats UI, input labels and ID controls, recording notice and actions, MCP chat service.