Activity shows what agents do right now, request by request. Analytics adds it up: which tools agents use, how fast they answer, how often they fail and how much of the agent's context they cost. Everything stays on this computer
Activity
Activity has four views, picked at the top left. Sessions and Plans add a count, such as Sessions (2)
| View | What it shows |
|---|---|
| Requests | Every request agents sent, newest first |
| Sessions | The agents connected to this server now, see Sessions |
| Plans | Plans that haven't run yet, with their instance, items and when they expire |
| Audit | Every call that wrote or planned a write, from the audit log, see Audit |
Requests
Search requests and payloads at the top finds text in the requests and in what they sent and got back. A pill each for Status, Agent, Request and Time filters the list, and Clear All ends every filter
| Filter | What it picks |
|---|---|
| Status | How a request ended: Succeeded, Failed, Refused, Blocked or Stopped |
| Agent | The agents that sent it |
| Request | The tools or methods |
| Time | Any time, Last hour, Last 24 hours, Last 7 days or Last 30 days |
| Column | What it shows |
|---|---|
| Time | Local time |
| Status | How it ended, such as OK, Error, Invalid arguments, Refused, Cancelled or Timed out, with ×3 when the same request came again |
| Request | The agent's icon and the tool, without intellijsfcc_, or the method. Hover the icon for the agent, its client ID and protocol |
| Instance | The host it reached, or This project |
| Message | The error code and text, or why it was refused |
| Duration | Waiting plus running, such as 41 ms or 6.8 s |
| Tokens | About how much the answer cost the agent's context, such as 1,180 |
| Size | How large the answer was |
On a narrow tool window Instance and Message hide first, and Status keeps only its icon. Tokens and Size show on a wide one
The line under the list counts the requests, such as Requests: 46 · Not succeeded: 3. Hover it for how much is stored and where
Purge at the top right deletes requests Older Than a Day, Older Than a Week or Older Than 30 Days, or All Requests… after asking. It also shows the folder and opens Activity Settings…
Request details
Select a request to see its details beside the list on a wide tool window, or under it on a narrow one
| Tab | What it shows |
|---|---|
| Overview | The request, the agent, how it ran and its HTTP facts |
| Request | What the agent sent, with credentials masked |
| Response | What the agent got back, exactly as it received it, with credentials masked. Show as, Content Only, Soft-Wrap and Copy Text sit over it, with its size, such as 1,204 characters |
Show Only This Agent in the details' title filters the list to that agent, and Close Details hides them. Payloads are kept while Keep request and response payloads is on, see Where it is kept
Sessions
Every agent connected to this server now, from every open project
| Column | What it shows |
|---|---|
| Client | The agent |
| Client ID | Its client ID, see Client keys |
| Project | The project it calls |
| Protocol | The MCP version it speaks |
| Exposure | Its tool mode, such as Global or Compact |
| Opened | When it connected |
Select one and click Show Requests to see only its requests, or Disconnect to cut it off. With none it reads No agents connected
Audit
The audit log keeps every call that wrote or planned a write for 90 days: planned, allowed, blocked, run or failed. Each entry holds the time, the agent, the tool and its risk, the plan's paths, hosts and code versions, the effect the agent expected and the result. It sits in <IDE system folder>/intellij-sfcc/mcp/audit/, one file a month
Analytics
Analytics has four views, picked at the top left: Overview, Tools, Agents and Instances. Tools, Agents and Instances add a count
Pick Today, Last 7 Days or Last 30 Days in the bar under them, on every view but Instances. The bar also sums the range
| Figure | What it counts |
|---|---|
| Calls | Calls in the range |
| Error Rate | The share of calls that failed |
| Tokens Sent | About how many tokens the answers held |
| Context Saved | How much shorter the answers were than the raw data behind them |
Token numbers are estimates made on this computer, with no tokenizer service, so they show as about
Overview
Calls over time charts the range, split by Outcome, Tool, Instance or Agent. By outcome the series are Succeeded, Failed, Refused and Other. Click a series to hide or show it
Tools and Agents
Tools has a row per tool. Click a header to sort
| Column | What it shows |
|---|---|
| Tool | The tool, without intellijsfcc_ |
| Calls, Errors | How many calls, and how many failed |
| p50, p95 | The usual and the slow answer time |
| Tokens, p95 Tokens | The context cost in all, and of a large answer |
| Cut | How often answers were shortened |
| Saved | How much shorter than the raw data |
| Hints Followed | How often the agent took the next tools the answer suggested |
Agents has a row per agent, with Calls, Errors, p95, Tokens and Saved
The same numbers mark tools on the Tools tab: Fails often, Refused often, Often cut, Answers over budget or Slow, see The Tools tab
Instances
Every B2C instance of the project: the active connection first, then the loose connections, then each group. Filter instances finds one. Each instance has a bar of the calls agents made there in the last 30 days, succeeded, failed and refused. Credentials never show here
Export and clear
Export saves the numbers as JSON, CSV or Markdown: numbers only, never arguments or answers. Clear Analytics asks first, then deletes every daily figure and the calls in memory
Where it is kept
| What | Where | For how long |
|---|---|---|
| Requests and their payloads | <IDE system folder>/intellij-sfcc/mcp-activity/, one folder per project | Keep requests for:, 30 days by default, within Maximum size per project:, 256 MB by default |
| Recent calls | Memory, the last 5,000 | Until the IDE closes |
| Daily records | <IDE system folder>/intellij-sfcc/mcp/analytics/, one file a day | Keep daily analytics:, 30 days by default |
| Daily totals | The same folder | A year |
A payload that holds a stored credential is never written. The analytics folder never grows past 50 MB: the oldest days go first. Nothing is sent anywhere