Inspect tool calls and assistant activity

Unity's assistant uses tools to inspect context, run queries, change report objects, and check results. The activity shown with a conversation lets you follow those operations and distinguish an intended action from a saved result.

A multi-step build can include many tool calls inside one request.

Inspect activity

Open the relevant conversation.
Expand its work or activity entries.
Read operation names, targets, statuses, and available result details.
Open query or visual details where supplied.
Compare the completed operations with the assistant's final response and the actual report.

The activity is an execution record. It is not a transcript of private model reasoning, and each entry does not necessarily display every raw tool argument.

Tool families

Family	What it enables
Report inspection	Find pages, native and HTML visuals, datasets, and connections across the current report.
Model inspection	Discover entities, fields, relationships, definitions, and their usage.
Query execution and planning	Run supported read-only calculations and inspect model/filter compilation.
Native visual editing	Create, update, replace, arrange, inspect, and remove native objects.
Page operations	Create, rename, duplicate, update, and delete report or HTML pages.
HTML authoring	Register datasets and visuals, edit source, and update supported page content.
HTML verification	Read execution feedback, capture rendered previews, and run focused browser checks.
Reference files and assets	Find files, read/search/preview sections, and reuse original images.
Filters	Change supported persistent filter scopes or inspect their effects.
Change history	Inspect recorded mutations and undo supported operations.
Inline chat previews	Inspect or revise a preview associated with a conversation message.

The agent tool reference lists every registered tool, its availability, required parameters, and exact schema. The reference labels compatibility tools separately from tools available to current assistant runs.

Follow a page build

A typical HTML task might produce this sequence:

Inspect report and model
Read the relevant report files
Create the HTML page
Save datasets, registered visuals, and layout
Read query and renderer feedback
Preview the saved page
Inspect the screenshot
Patch a specific issue
Preview again and complete

The exact sequence depends on the request and existing state. For example, updating CSS on an existing visual need not repeat an unrelated data-model change.

Read saved-change receipts

A supported mutation can identify the affected object, operation, persisted state, and before/after revision or snapshot. Use that receipt to establish what actually changed.

Evidence	What it establishes
A proposed action or progress message	The assistant's intended next step.
Successful read/query result	The requested inspection or execution returned.
Persisted mutation receipt	A particular change was saved.
Successful renderer feedback	The checked page or component executed.
Inspected screenshot	Evidence about its visible appearance at the captured state.
Recorded browser check	A specific condition or interaction was tested.

No single row establishes complete business correctness. A query can execute at the wrong grain, and a page can render with an outdated label.

Understand failures and repairs

An operation may fail because of SQL, missing fields, invalid bindings, permissions, revision conflicts, or renderer behavior. The assistant can inspect the failure and make a targeted correction.

Earlier successful operations can remain saved when a later operation fails. A recovered failed attempt in the activity does not necessarily mean the final result failed; inspect the later repair and final state.

Inspect the activity for the last build. Identify which changes were
saved, which failed, and whether the final HTML preview reflects the
latest saved revision. Continue only the unfinished work.

Inspect the right scope

Current report chat has tools for both native and HTML work. Available operations still depend on resource permissions and valid object identities.

An active page, selected visual, or attachment narrows focus but does not grant access. Organization membership likewise does not authorize arbitrary company reports.

See Background work for run states and Change history for recovery.