Agent activity and project mentions
3 minute read · Chats & Local Agents
Use the robot button in the sidebar footer to follow running conversations across workspaces. Open the chat that needs attention without moving or reorganizing the work. When a request belongs in another project, start a separate root chat with a leading project mention.
- Follow running work
- Follow subchats in their parent
- Start a project chat with a leading mention
- Find project tools and connections
Follow running work
Select Agent activity on the robot button. Its badge shows the running count. The compact popup shows each active chat, its project and whether it is Working, Stopping, Finishing or Needs your input. The number of visible rows fits the available space, up to six.
Entries keep a stable order while messages arrive. New activity does not constantly move the chat you are about to select. Choose a row to open that conversation. The separate window action opens its chat; Stop requests cancellation and does not undo files already changed. An empty list means no agents are currently running.
The workspace rail also marks work in progress with colour. Hover a workspace icon for its full name and activity summary. A request for input has a distinct attention indicator. Opening another tool or workspace does not stop a running chat.
Follow subchats in their parent
Linked assignments appear in subchats below their parent while their work is needed. Expand the box to inspect a child and use Back to return. A coordinator waiting for linked work can resume locally when a result or request for attention arrives.
Fully completed child conversations are cleaned up after their result is handed back and no pending work still needs them. Follow the integrated result in the parent conversation. Cleanup does not remove the checkout or undo code changes. Work still awaiting review, follow-up or an approval must not be treated as fully complete. See linked project tasks.
Start a project chat with a leading mention
Begin a composer message with @ and choose a project from the Projects suggestions, or type its project token as the first item followed by the task. For example:
@foodcard Review the empty state and suggest a focused UI improvement.
The app starts a new root chat in that locally attached project, including a project in another workspace. It leaves your current chat selected and sends only the new request and any attachments/context you explicitly selected for it. It does not copy the current conversation history. Select the exact workspace and project from the suggestions when names or tokens are duplicated; an ambiguous typed mention is rejected instead of guessed. Add a task after the mention; a bare mention cannot start work.
This leading @project form is composer syntax, not a callable tool or /command. Other @architect, @ux, @design, @ui, @security and @qa suggestions describe working steps for the current agent. They do not automatically create more agents or promise a fixed pipeline. Keep the task scoped and follow its progress through Agent activity.
Find project tools and connections
Open Project settings → Connections to select resources for a project. Open a global tool from Tools in the sidebar footer or from command search. Project pinning remains supported through the saved project settings and available Vortex tools; a pin is a project reference, not a credential copy or a connection attempt. See project environments and resources for saved resource workflows.
Related guides: chats and drafts, linked tasks, workspaces and projects.