List nodes (paged)

List the nodes in your workspace (GPU and CPU shapes): name, chip, state, and - while placed on a region-labeled machine - the region it runs in (absent = not placed or not reported; CPU nodes may run far from your GPU nodes, so check it before assuming a LAN). A private-network member also shows its network with stable mesh addresses, DNS name, region/zone, and data_plane (up, converging, not_placed, or unavailable; attach_network explains each). Work on a node with run_command; poll a pending node with get_node. THESE ARE NOT ALL YOUR NODES: a workspace is shared, and other agents in other sessions - plus every human member - create nodes here too. Each row carries yours, created_by, and the mission it was created for, plus sessions and running_commands when work is live on it; a shared block counts what is not yours. PASS mission: "<what you are working on>": yours is an ACCOUNT fact, and the several agents one person runs at once share that account, so without it a node from your own other investigation reads as yours. With it, every row gains same_mission - work only where that is true. Create your own node rather than borrowing one: reusing a node overwrites its files and environment, and stopping or deleting it destroys work you did not start. A node whose state reads "stopped (no restorable disk copy)" cannot start, because the platform has no copy of its disk that it can restore. The platform refuses every wake of it, and get_node's stopped.note says why.