Export
Nothing is locked in. Every result copies, saves or exports from the screen you are already on.
On this page
From Scrape
Copy and Save as file act on the visible tab, under the tab’s own name:
| Tab | Saved as |
|---|---|
| Markdown Render | page.md |
| llm / text / json / html / raw | page.llm.txt, page.txt, page.json, page.html, page.raw.html |
| Extracted JSON | extracted.json |
| XHR | xhr.json |
| Brand | brand.json |
| Viewport | page.png (the screenshot — it saves, it does not copy) |
A tab with nothing behind it falls back to the page’s Markdown. Read-only mode — trial used, licence lapsed — keeps every export working.
From Crawl
The finish panel (and History’s Output tab) previews the first 50 records and exports the run through the native save dialog as jsonl, json, csv or sqlite. Corpus runs export jsonl/json only. Open folder reveals the run’s <runId>.jsonl and its numbered .part resume parts on disk — plain files you can post-process with anything. What lands in each format is on Export formats.
From Research
A finished report exports three ways:
- Markdown — the report, citations inline.
- Sources CSV — one row per footnote: footnote, url, quote, checked_at, content_hash.
- BibTeX — one entry per cited snapshot.
For DOCX or PDF, export the Markdown and run the copied pandoc research-<runId>.md -o research-<runId>.docx line — the app ships no exporter and no dependency for it.
The Compare screen’s Export… writes a word diff through the same save dialog.
From History
Every run row opens a drawer with three tabs. Output holds what the desktop kept — a scrape’s Markdown and extracted record, a crawl’s records preview and export buttons. Reproduce is the run as a command (next section). LLM calls is the per-call ledger: purpose, provider, model, tokens, USD — the audit trail behind the cost column.
CLI runs appear here too; the desktop and the terminal share one store, so a script’s output is exportable from the GUI the moment it finishes.
Copy as CLI, MCP or Go
Beside every Run button, Copy as… shows the exact run as:
- CLI — a
magpie …command line, POSIX sh, runnable as printed. - MCP — a
tools/callpayload for the MCP server. - Go — a
package mainsnippet against the library.
The snippets are built from the same options the button sends, so they cannot drift. Secret material is redacted honestly — a per-run key or pasted cookies keep only a placeholder, and the notes say so. CLI runs and older runs keep no saved options; the panel says that instead of guessing.