Skip to main content
When a flow runs a New Super Magic Agent or Run Skill action, the agent does its work inside a Super Magic conversation. That conversation is now shared with your workspace automatically, and the run’s detail in the Logs tab links straight to it. You no longer need the flow’s creator to dig the chat out of their own history: any admin reviewing a run can open the full transcript and see exactly what the agent read, decided, and did. Prerequisites:
  • Chat sharing is enabled for your workspace. The links open Super Magic’s shared, read-only chat view.
  • The run you’re reviewing includes a Super Magic action. Runs of flows with only classic actions (set status, assign, reply, and so on) have no conversation to link.

Open the conversation behind a run

1

Open the Logs tab

In Thread Admin, go to Flows and select the Logs tab.
2

Select a run

Select the run you want to review. The run’s detail opens with the flow’s conditions and the steps the run executed.
3

Expand the Agent conversations row

Look for the Agent conversations row, which sits directly after the step that handed the run to the agent. Expand it to list the conversations the run produced, in the order the agent opened them — each with its title (or Conversation if it has none) and when it started.
4

Open a conversation

Select one to open the full transcript as a read-only view.
An agent action in the log reports Dispatched, not Success — that only means the run handed off to the agent. The conversation is where you confirm what the agent actually did.
In the read-only view you can scroll the whole conversation and expand tool-call cards to see each action the agent took, but you can’t send messages or run anything. The view works the same way as any shared Super Magic chat, including the Shared by label naming the conversation’s owner. The links are readable by every signed-in member of your workspace, the same audience as a Super Magic chat shared from Teams or Slack. They are not public URLs: someone outside your workspace who receives the link cannot open it. The conversation’s owner can still stop sharing it from the chat’s share dialog. After that, the link in the run detail shows a not-found message instead of the transcript.

Why a run shows no conversations

A run with no conversation links is normal in these cases:
  • The run predates this feature. Sharing applies to new conversations only. Nothing that already existed was shared retroactively, and log entries are kept for 7 days, so older linkless runs age out on their own.
  • The flow has no Super Magic action. Classic actions update the ticket directly and never open a conversation.
  • The owner stopped sharing. A revoked conversation link shows not found when opened.
If the row is missing on a run you know used an agent, open Super Magic → Flow Chats as a fallback, and see when it goes wrong for the full troubleshooting checklist.