Workspace, bots and ongoing work
Start from a channel or assistant and manage queued guidance, stopping and completion.
Workspace structure
Use the sidebar to select a channel or bot and confirm the workspace first. Channel conversations and direct-assistant work have different ownership contexts. Settings, skills, memory and administration remain scoped to current permissions.
A failed read is not proof that an empty list represents deleted data.
Direct-assistant work list
Open a bot and select or create work in its server-backed list. Filter active/completed work and load further pages as needed. Rename a work item to clarify its purpose without changing its identity.
Continue with more input
While a direct-assistant task runs, subsequent instructions can be saved as pending input and dispatched in order after the foreground run ends. Pending and executing work are separate states.
Release held input explicitly or withdraw input that is no longer needed. Accepted input has not necessarily executed. Do not assume channel events use this same manual-input flow.
Stop and complete
Stop ends current execution; Complete closes an idle work item. Active foreground work or retained input may prevent completion. Verify the terminal state after requesting a stop.
Neither action automatically retracts file changes, messages or other external effects. Inspect existing results before repeating work.
Artifacts, skills and memory
Inspect artifacts through supported entries and permissions. Saving, closing history, clearing history and restoring data are different actions. Skills and memory do not bypass tool approval.
See models and tools and data operations.