Instances

An instance is where users open chat, upload files, and read output. Each instance has its own state (running, stopped, error) and maps to the left list and top tabs.

Lifecycle

• Create — Usually from Run on a template. Filter by All / Public / My instances, and pin frequently used ones.
• Edit after creation — Change name, description, model, region, and cloud resources. Changing resources saves and restarts. Re-editing a published agent lets you reselect resources and triggers a redeploy.
• Run and pause — Running means it can serve; pause to save quota or stop accidental batch runs.
• Sleep and wake — Conversation is unavailable while sleeping; wake when needed.
• Stop and delete — Stopped: no new requests. Before delete, export results and check share links and downstream tasks.

Day to day

• After opening, sub-tabs may include Agent chat and Workflow.
• For HR today, resumes and JDs are often uploaded in instance chat; exploratory chat with the assistant can stay separate.

List affordances

• Status, lock icons, and “more” menus follow the live product. Locks often mean private or restricted access.

From a template: Templates. Public links: Public access and sharing. Bind knowledge or workflows: Capabilities and workflows.