When to use each option
| Action | Use when |
|---|---|
| Open in tab | You want to read the full task conversation inside Alter |
| Export Chat | You need a local .md file for your records, docs, or offline review |
| Share trace | Something failed or behaved unexpectedly — send diagnostics to the Alter team |
| Save Conversation as Markdown (⌘⇧S) | You want the parent Hub/QuickHub chat exported, not just the task sub-thread |
Where to find task actions
- Run a task-producing tool (for example ask Alter to Computer Use a goal, or invoke Flow)
- In the Hub or QuickHub, open the Inspector panel for the conversation (sidebar inspector toggle)
- Select the tool run in the inspector — the row for
computer_use_task, Flow, or another task agent - Scroll to the task conversation action block (highlighted accent background)
- Open in tab
- Export Chat
- Share trace
Open in tab
Open in tab jumps to the read-only task conversation — the subagent thread with its own messages, tool calls, and results. Use this when:- The parent reply summarized the outcome but you want step-by-step detail
- You need to copy a specific tool argument or result from the sub-thread
- You are reviewing a long Computer Use run before exporting
Export Chat
Export Chat saves the task conversation as a Markdown document:- Click Export Chat in the Tool Inspector
- Choose a location in the save panel (defaults to Downloads)
- Alter writes a
.mdfile named from the task title (or Task Chat if untitled) - Finder opens the containing folder
Share trace
Share trace uploads a diagnostic bundle to Alter’s API so the team can investigate bugs, permission failures, or unexpected agent behavior.Requirements
- You must be signed in to Alter (a valid account JWT). If you are logged out, sharing fails with an authentication error.
- A task conversation must exist for the selected tool run — the inspector derives it from the tool result or the live task registry.
What is sent
The upload includes:- Title — task conversation title
- Markdown — formatted task messages (same as Export Chat)
- Tool name — for example
computer_use_taskor a Flow tool id - Task conversation id — internal identifier linking parent and sub-thread
- App version — Alter build string for reproduction
Privacy expectations
Traces are intended for support and debugging, not public sharing:- Content reflects what the task subagent saw and did — prompts, tool arguments, and results
- Screen content, window titles, and file paths from Computer Use may appear in the markdown if the agent captured them
- Home directory paths in Doctor reports are redacted when you use Copy Report, but task exports are not automatically redacted — review before sharing if the run touched sensitive apps
Save Conversation as Markdown (parent chat)
Save Conversation as Markdown — default ⌘⇧S — exports the active Hub or QuickHub conversation to markdown via the Hub menu or shortcut. It does not replace Export Chat on a tool run:- ⌘⇧S → entire parent thread (your messages + assistant replies + tool summaries as shown in main chat)
- Export Chat (inspector) → subagent task thread only
Troubleshooting
Task actions missing in the inspector- The tool must be a task-producing run with an associated sub-conversation
- Wait for the tool to finish starting — some agents register the task id after the first subagent message
- The task conversation was released from memory — re-run the tool or open the parent conversation while the task is still loaded
- Sign in under Settings → Profile or the account menu, then retry
- Share trace uploads to Alter support; it does not copy a public URL to your clipboard. Use Export Chat and share the
.mdfile through your own channels if you need a link outside Alter.
Related docs
Computer Use
Goal-based agent that produces task conversations
Background Computer Use
Watch preview and Edge Bar sessions
Shortcuts reference
⌘⇧S and Hub shortcuts
Doctor settings
Permission diagnostics when tools fail