corezoid-dashboard-manager

Corezoid Dashboard Manager

What dashboards are

A Corezoid dashboard visualizes task counters in process nodes — it shows how many tasks are accumulated in (or have passed through) specific nodes. The data comes directly from running processes, not from external databases.

Key implication: processes must be deployed and have tasks flowing through them for data to appear.

---

MCP Tools Reference

Tool	Purpose
create-dashboard	Create a new dashboard, returns obj_id (= dashboard_id)
get-dashboard	Get dashboard details including all charts and series
add-chart	Add a chart to a dashboard, returns obj_id (hex chart ID)
get-chart	Get a single chart with its series
modify-chart	Modify an existing chart — always provide full series array
set-dashboard-layout	Save chart positions on the grid — required to make charts visible
pull-process	Pull process JSON to find node IDs for series

---

Workflow: Create a dashboard with charts

Step 1 — Identify the process (MANDATORY FIRST STEP)

Before doing anything else, resolve the target process:

1. Check whether the user already provided a process identifier — a file path, process name, or process ID — in the current message or conversation history.

2. If no identifier is provided, ask:

   "Which process(es) do you want to monitor? You can provide a file path (e.g. 123_payment.conv.json), a process name, or a process ID."

   Do not call any MCP tools until the user provides an identifier.

3. If the user gave a name or ID (not a file path), search the local working directory for the matching .conv.json file using the find or grep Bash tools (the project is already pulled locally).

4. Once the file path is known and the file exists locally, open and read it to find node IDs in scheme.nodes[].id — note the IDs of nodes you want to measure. End nodes are best as primary metric sources.

   If the process is not available locally, fall back to:

   pull-process(process_id=<PROC_ID>)