Skip to main content

My Sessions

/my-sessions is the "where did my work land" page: every agent run you've started, with its outputs ready to collect. Asked an agent to build a report yesterday and can't remember where it went? It's here.

Your work survives disconnects​

The most reassuring thing about this page: agent runs keep going even if you don't. Execution continues on the server — close the laptop, lose the connection, go home — and the run finishes without you. Files land in your File Space, and the completed run appears here with everything it produced ready to download. Kick something off at 5pm, collect it over coffee tomorrow.

The list​

Each run shows:

  • Status — Running, Completed, Error, or Parked (waiting on something).
  • Agent — who did the work.
  • Intent — what the run was about.
  • Files — how many artifacts the run produced, and the name of the headline one. This column is the quickest answer to "did it actually make the thing?"
  • Tool calls, duration, and when it started.

A status filter narrows the list to just Running, Completed, Error or Parked, and the list is paginated when it gets long.

You don't need to refresh. While a run is in progress the page polls every few seconds (you'll see an indicator), so completions appear within moments of the server finishing. When nothing's running it settles down to a slower rhythm — and there's a manual Refresh button if you're impatient.

The detail drawer​

Click any row and a drawer opens with the full story of that run:

  • Goal — what the run set out to do.
  • Artifacts — every file or item it produced, with size and type. Files download directly; things created in external systems (a JIRA issue, a Slack message, an email) open in a new tab.
  • Outcome — what was completed, and anything still pending.
  • Tool calls — each step the agent took, with its status and duration, and logs links into File Space where execution logs were captured.
  • Errors — anything that went wrong, in plain sight.

Good to know​

  • This page shows your runs only. Your colleagues each have their own; the org-wide session log is an admin view.
  • Files here are the raw outputs of runs. For living, editable pages — dashboards, articles, slideshows — see Artifacts.
  • If a run shows Error, open the drawer and read the Errors section before retrying — it usually says exactly what was missing (often an expired connector or an unanswered approval).