Pre-submit Checks

• I have searched Warp feature requests and there are no duplicates
• I have searched Warp docs and my feature is not there

Describe the solution you'd like?

I’d like Warp to support a machine-readable local export for agent conversations, alongside the existing Markdown export.

A small first step could be adding an explicit structured format to the existing export flow, while keeping Markdown as the default human-readable format. For example: /export-to-file --format jsonl <optional filename>

Longer term, it may also be useful to have an opt-in setting to save conversations automatically as local structured trace files, so users do not have to manually export important sessions.

Is your feature request related to a problem? Please describe.

Warp can export agent conversations as Markdown, which is useful for humans. But Markdown is a presentation format, not a structured trace. Tools have to infer turns, roles, tool calls/results, timestamps, IDs, model metadata, and events from prose.

SQLite is useful as Warp’s internal restore/cache layer. Markdown is useful for reading. There does not appear to be a user-owned local artifact for structured agent traces.

That makes it harder to inspect, debug, archive, version, or transform agent conversations locally without relying only on Warp’s internal storage or cloud conversation storage.

Additional context

Other local AI developer tools, including Claude Code, Codex CLI, and pi, use line-oriented JSON session files for local persistence. That style of artifact is easy to inspect, diff, archive, and transform.

I have a small local prototype scoped to the existing export command and an isolated serializer. Happy to open a PR or write a short spec if useful.

Operating system (OS)

macOS

How important is this feature to you?

4

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None