CLI command
jeden show
Print one durable session: each event under its own heading, or the whole record as JSON.
Exact invocation#
jeden show <session-id-or-path> [--json]Inputs and options#
- Required: a session identifier under the session root or a session directory path containing a slash.
- Optional:
--jsonprints the full export.
Output and state effect#
Reads the session state and validated transcript ledger. Without --json it prints the session id and path and each event's time, type and data; with --json it prints its id, path, ledger version, active leaf, recovery flag, and exported events. It does not mutate the session.
Refusals and boundaries#
- The functionality is
jeden.session.export;jeden errors show jeden.session.exportprints every cause with its test (tests/sessions/listing/records.mjs). Read before the session, each exit2:session-missing(show requires a session id or path, and the command line ends before one) andargument-unexpected(show takes one session id or path, and `ARG` is none of them). - Finding the session is
jeden.session.find, exit1:session-not-found(session not found: <path>; nothing is at that path, observed: the session root a name without/is looked up under; fix:jeden sessions, orjeden sessions search <query>to find one by what it holds),session-unexaminable(<path> cannot be examined, never reported as not found),session-not-a-directory,session-state-absent(RPCsession/openof a directory withoutstate.json) andlast-session-unrecorded(a session command that names none in a workspace that recorded none). - Reading it has every cause of
jeden.session.ledger.read, listed on the sessions page: an unreadable ledger (cannot read <path>) or state, a state that is not a JSON object, and a ledger line that is malformed JSON, not an event, of another schema, changed after its seal, out of sequence, recorded twice, off the active lineage, of another session or with broken links, each naming<path>:<line>. id-not-text: the session's path is not UTF-8 text or ends in no name, such as one ending in... Nothing is printed on stdout.- A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits
2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits69; any other refusal or failure exits1. A refusal a functionality declares ends withfix: …andcause: <operation>.<cause>, andjeden errors show <operation>lists every cause of that functionality.