Dashboards

Dashboards present local context and stored routine results. A page does not receive service credentials or silently start an agent when opened.

Read local and cached data

HTML dashboards find context files through window.codesense.queryContext(), or stay live with subscribeContext() (see Query your context). A page sees team content across your orgs, and private items from its own org only. Routine-backed pages use the documented routineResult or routineStatus SDK methods to read a cached result and its status. Show when a result is missing, stale, or failed instead of presenting it as current service data.

For external data, a configured routine runs an agent with its own authorized tools. The agent collects the data and publishes a result using routine_publish_result. CodeSense stores the result for dashboard reads; it does not proxy the external service request.

Refresh deliberately

A Refresh button can invoke routineRefresh for a configured routine. This is an explicit action; it runs when the page calls it. Passive rendering and cached reads must not trigger it.

A routine may also run on its configured schedule. That schedule is separate from opening a dashboard.

Author and share

Ask an agent to read get_live_data_contract, create the page, and check it with validate_live_data_doc. Keep credentials out of page files and routine result data. A page calls action verbs such as openWorkspace or routineRefresh directly; there is nothing to declare and no prompt.

A rendered page snapshot or exported document captures a view for sharing. It is different from the routine result snapshot that supplies the page’s data. See Have an agent build a dashboard for the workflow.