.docx files from any shell. It exposes the same operations as the Document API through a stdio-based process.
The CLI is in alpha. Commands and output formats may change.
Installation
Workflow
The CLI uses persistent sessions. Open a document, run operations, then save and close:Tracked mode for mutations
Use--tracked on mutating commands to apply edits as tracked changes instead of direct edits.
--tracked is shorthand for --change-mode tracked:
TRACK_CHANGE_COMMAND_UNAVAILABLE.
User identity
By default, the CLI attributes edits to a generic βCLIβ user. Pass--user-name and --user-email on open to identify your automation in comments, tracked changes, and collaboration presence:
Commands
Lifecycle
Document operations
The CLI exposes all Document API operations as commands. The command name matches the operationβs member path, converted to kebab-case:
Run
superdoc --help for the full list, or superdoc describe for machine-readable metadata.
Session management
Introspection
JSON I/O
All commands accept--input-json or --input-file for structured input and return JSON output. Use superdoc call <operationId> for raw operation invocation:
Related
- SDKs β typed Node.js and Python wrappers over the CLI
- Document API β the in-browser API that defines the operation set

