Activity and gaps
Every request agents make is logged. It's the best way to see how your context is being used and what's missing from it.
Updated
Activity in the sidebar shows two things: what agents asked for, and what agents changed.
Requests
Every get_context, search and get_file call is logged, from MCP and the REST API alike. Owners and admins see the log; members don't, because what someone asks their AI can be sensitive.
Each row shows:
- When the request came in.
- From:
mcporapi, and which tool was called. - Request: the task or query the agent sent, with the titles of the pages that came back underneath.
- Pack: the first pack that applied to the task, if any.
- Pages: how many pages came back. Zero is highlighted.
- Time: how long the request took.
The log shows the most recent 200 requests.
Finding gaps
Switch the filter to Nothing found to see only requests that came back empty. This is the most useful view in the product for deciding what to write next.
Every row there is a moment when someone's agent needed something from your workspace and got nothing, and probably either guessed or asked the person to fill in the blank. Read through them every week or two and you'll start to see patterns: a competitor nobody has written up, a product that launched without a page, a question about security that keeps coming up.
Requests that returned only a few loosely related pages are gaps, too, just less obvious ones. If the titles under a request don't look like what you'd have given that task yourself, open a page and see whether the answer is actually in there, under a heading that says so.
A good routine, if you own a workspace:
- Open Nothing found and note the topics that come up more than once.
- Skim the full log for requests where the pages listed don't look right.
- Write or fix a page for the biggest one, with specific headings.
- Publish, and try the same task with your own agent.
Agent edits
Above the request log, Agent edits lists the 50 most recent changes connected agents have made: pages created, text edited, properties changed, pages moved, access changed. Each shows which connection made it (an API key by name, or a sign-in connection with the person's email) and a short summary.
Everyone who can see the page can see its edits here. Undo restores the page to how it was before that change, if you can edit the page. Body edits are drafts until someone publishes them, so the usual flow is to open the page, check the change in its Changes view, and publish it.
See When agents write back for more.
On the Overview page
The Overview page for each workspace has the headline numbers: published pages, searchable sections, packs, and agent requests in the last seven days. It also shows how many pages aren't live for agents yet, with a link to review them.