Canvas and dashboard

The canvas is one graph of objects: nodes, documents, bash jobs, owners and custom objects. This page covers the node views, which are the dashboard and the browser; crtr canvas read, list, search, watch and edges work on every kind of object (see Documents and preferences). You can see every agent as a node on the canvas, find work that is blocked, and return to the exact conversation that needs you. Use the dashboard for a quick terminal view and the browser when you want to navigate the graph interactively.

Read the dashboard

Run:

crtr canvas dashboard

The dashboard prints the canvas as an ASCII subscription tree. Each row includes the node id, name, status, kind, mode, context-token count, and pending human asks. Add --root <node-id> to limit the tree to one root and its work.

A node's active status means its broker process is live; it does not necessarily mean that the model is generating text. A node may be dormant while it waits for an inbox message, a child report, a human answer, or a scheduled event.

Browse the graph

Run crtr canvas browse in a terminal for the interactive graph view. It has tabs, a collapsed tree, and / search. Press Enter on a node to resume it, or press q or Escape to leave the browser. In a viewer, the graph command opens the same canvas information without losing the conversation you were reading.

Find a blocked node

Use the human-attention view when you want to know which work is waiting for you:

crtr canvas attention list

It identifies the nodes that have pending human interactions across the canvas, oldest first. Run crtr human list when you need the individual tickets. You can also run crtr canvas attention count for a number only.

To inspect one node's neighbors and drill-in paths, run:

crtr node inspect show <node-id>

The documents a node wrote, including its reports, are objects it owns: crtr canvas list --owner <node-id> lists them, crtr canvas read <node-id>/reports/<name> opens one, and crtr canvas search finds one by its text. crtr node inspect transcript <node-id> reads its saved conversation, and crtr node inspect context opens its context directory of scripts and data. crtr canvas history search searches what nodes in the current working directory were told and said — past inboxes and conversations, not reports or documents.

Reopen work

crtr surface node focus <node-id> is the normal way to return to a conversation or inspect finished work. It brings a running viewer into view, opens a parked resident's saved conversation, or shows a finished node's read-only transcript.

Use crtr node lifecycle revive <node-id> when you specifically need to relaunch a node's broker and resume its saved conversation. After an outage or reboot, crtr canvas revive --all previews every eligible disconnected node and, without a confirmation, launches nothing. Review that list, then use crtr node lifecycle revive <node-id> for the node or nodes you intend to bring back. The canvas preview does not include nodes that are done or canceled by choice.