Skip to main content
Every time Swan does anything — replies in chat, fires a trigger, or runs a delegated sub-agent — it’s recorded as a run (also called an execution; some parts of the UI say “job”). Nothing Swan does happens invisibly.

​
What’s recorded for each run

Each run keeps:
  • Its status (queued, in progress, completed, failed, cancelled, or waiting on a confirmation).
  • A narrative summary of what happened during the run, so you can understand what Swan did without replaying every step.
  • The credits used, so you can see the cost of that specific run. See credits and credit costs.
If a run created a task, was part of an outreach sequence, or was triggered by a specific automation, that context is linked from the run itself.

​
Searching past runs and conversations

There’s no dedicated search page for this — you ask Swan directly in a chat conversation (for example, “find that conversation where we discussed a competitor mentioning our pricing”). Swan matches on both the exact words and the underlying meaning of your query, so a vague description can still surface the right run even if it doesn’t contain those exact words.

​
Who sees which runs

Admins can see every trigger-driven run across the org. A standalone chat conversation that isn’t tied to a trigger is visible only to the person who ran it — being an Admin doesn’t grant access to other members’ private chats. Members see their own conversations plus runs from org-wide triggers. See Roles and permissions.

​
Common questions

Can I delete a past conversation or run from my history? No — conversations and runs can’t be deleted today. They persist as part of your organization’s operating history. Does a trigger’s run show up for everyone in the org? Only if the trigger itself isn’t scoped to a specific person. A trigger owned by one person’s runs are visible to that person and to admins, not to every member. Can I link directly to a specific run to share it with a teammate? Yes, each run has its own URL you can share; anyone with visibility into that run (per the rules above) can open it directly. A chat conversation’s URL is https://agent.getswan.com/chat/{id}; a run surfaced on your Desk can be opened at https://agent.getswan.com/desk/{executionId}. Does the run history include sub-agent runs from delegated work? Yes — a delegated batch creates its own runs, and each one is recorded the same way as any other run, linked back to the run that dispatched it.