Attached context
Magellan sees what's on screen. Active-tool snapshots auto-attach. Pills show every attachment before send. Redaction strips passwords, tokens, AWS keys.
Magellan only sees what you select — but selecting is mostly automatic. Every chat turn shows a pill row above the message field with every piece of context that will leave your machine.
Active-tool snapshot store
The active tool registers a live snapshot of its output in a shared context store every time it produces a result. When you type in the right-rail chat, Magellan sees what’s on screen — not just what you deliberately attached. So you can run a packet capture, switch focus to the chat, and ask “what’s that retransmit pattern?” without manually attaching anything.
The snapshot store is Space-scoped — switching Spaces flushes it.
Attachment types
- Terminal output
- HTTP request snapshot
- HTTP response (opt-in per send — see below)
- DB query / result
- DB Health snapshot
- Document body
- Network-tool output (DNS, MTR, packet capture, etc.)
Pills visible before send
Pills render as Attached: <tool> · <size> the moment context is added. They stay visible until you send so there’s no doubt about what the model received. Click a pill to remove the attachment for this turn.
Redaction
Secret redaction strips before send:
- Obvious passwords (any field labeled
password,passwd,pwd) - Bearer tokens, API keys
- OAuth client secrets
- AWS secret-access-keys, session tokens
- Vault credential values
Secret env-var values are listed by key only — the value never goes out.
HTTP context — request vs response
- Request — automatic; the URL, method, headers, and body shape attach
- Response — opt-in per send; the response body is a PII boundary