Interface: CrashReport

What the session knew at the moment a program died unexpectedly.

“Unexpectedly” means the child exited on a signal, or with a non-zero code, without the harness being asked for it: neither close() nor an explicit signal() produces a report.

Properties

diagnosticsTail

readonly diagnosticsTail: readonly SessionDiagnostic[]

Defined in: driver/src/api.ts:1000

Tail of the session diagnostics log.

exit

readonly exit: ExitStatus

Defined in: driver/src/api.ts:985

lastSemanticTree

readonly lastSemanticTree: SemanticSnapshot | null

Defined in: driver/src/api.ts:996

Last fully paired semantic revision, when the session had one.

recentInputs

readonly recentInputs: readonly CrashInput[]

Defined in: driver/src/api.ts:998

The most recent inputs, oldest first — what was sent just before the end.

screenTail

readonly screenTail: readonly string[]

Defined in: driver/src/api.ts:994

Last lines of scrollback plus the visible grid, oldest first, with trailing blank lines trimmed — where a stack trace or a panic message ends up.

This is what the terminal showed, verbatim and unscrubbed: whatever the program (or the tty’s echo) displayed is here, secrets included. Treat a crash report like a screenshot when storing or forwarding it.

timeMs

readonly timeMs: number

Defined in: driver/src/api.ts:1002

Milliseconds since session start, on the same clock as every event.