/export [FILE]
Export/code/commands/interactive/export
Export the conversation to a file or selected format.
- Options
- 1
- Arguments
- 1
- Examples
- 1
- Industry
- 4 of 5 mapped
About
Supported options and rules: --format markdown|text|json; default markdown. No FILE opens save flow.
Syntax
The canonical syntax string as recorded in the catalogue. It is authoritative — it is never reconstructed from the option and argument lists below.
Arguments
filepathOptionalposition 1File path.
Options
Defaults, allowed values, conflicts and scope come from the catalogue; blank fields mean the catalogue records nothing, not that the constraint is absent.
--format <enum>enumOptionalChoose the export or output format. Allowed values: markdown, text, json. Default: markdown.
Allowedmarkdown, text, jsonDefaultmarkdown
Examples
With arguments
WITH ARGUMENTS/export review.md
Export the conversation to a file or selected format.
Availability & requirements
Nothing recorded — this command is offered in the default session, with no repository, authentication, capability or platform requirement attached to it.
Relationships
Industry comparison
4 of 5 products mapped
Command-level mappings against 5 audited products, each with its documentation source and capture date. No documented equivalent means the audit found nothing in that product’s official documentation — it is not a claim that the product lacks the capability.
Every canonical command was reviewed against all 5 products in one pass captured 2026-09-18. A product with no mapping is a reviewed finding of no documented equivalent, not an unreviewed pair.
Captured 2026-09-18 · 238 commands × 5 products
/export
/export-session
/export
/share file|html|gist