Understand Agent Activity
See local session activity without confusing it with task completion.
Agent Activity helps your team see which local agent sessions are active, their Project, and when they were last observed.
It is an awareness view. It is not a work reservation, an assignment, or proof that an Agent completed a request.
Enable observation deliberately
Local observation is opt-in and limited to confirmed Project folder connections. Check the computer and Project before enabling the relevant Activity settings.
A folder found during discovery is not an approved connection.
Open Activity
Open a Project's details and use its related Agent Activity link. Activity may also be available through workspace navigation or search; it is not always in the primary rail.
Filter or group the view to find the Project and Agent you need. Check the last observation time before treating a status as current.
What can appear
Activity can include the agent tool, its user-visible session title, model, state, branch, and timestamps. Supported details depend on the tool.
Session titles can themselves contain meaningful information. Review your sharing choice even though Activity is not a transcript view.
What it does not share
Activity does not expose full prompts, replies, reasoning, tool output, file contents, diffs, terminal commands, credentials, or absolute local paths.
Removing a Project connection stops new collection for that folder. It does not rewrite already accepted history.
Before you act on an observation
Confirm responsibility with the teammate doing the work. Two agents can be active on related work without either owning the whole task.
To check an OpenMeld request, open its original Space, thread, or Routine Run. Use the result and failure details there.
Next: Track Space Tasks.