Export Session To File

Exports a specific session's data to a JSON file for offline analysis.

Terminal

opencode export <session_id> > <path/to/session>.json

opencode export <session_id> > <path/to/session>.json

#!/bin/bash

# Export Session To File
opencode export {{session_id}} > {{path/to/session}}.json

When To Use

During a critical audit of session activities.

Pro Tip

Leverage the '--compress' flag for reduced file size if the data is extensive, but be aware that this may increase write time.

Command Builder

Tune the command before you copy it

Generated Command

opencode export <session_id> > <path/to/session>.json

Command Result

Shell behavior

Primary Effect

Writes to file. The command sends content into the output file instead of printing the final result to the terminal.

Terminal Expectation

A successful run is usually quiet. Verify the destination file after execution rather than expecting visible stdout.

Power User Variants

opencode export 12345678 > /tmp/session.json --compress

Exports session with compression.

opencode export 12345678 > /dev/null

Discards output but runs the export.

Troubleshooting

One of the input files does not exist

Solution: Check each input path before running the command.

The destination file or directory is not writable

Solution: Verify write permissions on the target path and parent directory.

Shell redirection points to the wrong file

Solution: Double-check the output path before executing, especially when overwriting with >.

Command Breakdown

opencode: Base Command; The executable that performs this operation. Here it runs Opencode before the shell applies any redirect operators.
<session_id>: session id; The value supplied for session id.
>: Output Redirection; Writes the command output to the output file, replacing any existing content.
<path/to/session>: Destination Path; The file that receives the final written output.

Alternative Approaches

Alternative data processing tools for the same job.