Session journal & export

Vibrai keeps an always-on journal of everything you do — every MCP tool call and every vibrai CLI invocation — written to a local file as you work. Any stretch of that journal can be exported as a runnable script of vibrai commands, so you can replay a build, hand it to a teammate, or drop it into CI. Nothing to turn on; it records by default.

The journal is local only — it never leaves your machine, and a journal failure never affects the command you ran. Names containing key/secret/token/password and license keys are redacted at write time.

What gets recorded

Every call, across both surfaces, lands in a per-day journal file. Vibrai splits the stream into segments at idle gaps (default 30 minutes), so a “session” is one continuous working stretch. Read-only calls (list, get, show) are recorded but skipped on export by default — the exported script is the sequence of changes that built your set.

Replay a session

List your sessions

Segments are shown newest-first, with their index, id, name (if you set one), time range, and call count.

vibrai session list

{
  "tool": "list_sessions",
  "arguments": {}
}

Name the current segment (optional)

A marker makes a session easy to find later and becomes a comment in the exported script. The call itself is the marker — the journal records it in place.

vibrai session mark "big room jam" --note "124 BPM, F minor"

{
  "tool": "mark_session",
  "arguments": { "name": "big room jam", "note": "124 BPM, F minor" }
}

Export it as a script

With no selector it exports the latest session; you can also pass an index, id, or name, or a --from/--to ISO-8601 range. Omit --out to print to stdout.

vibrai session export "big room jam" --annotate "recreate the drop" --out build.sh

{
  "tool": "export_session",
  "arguments": {
    "session": "big room jam",
    "annotate": "recreate the drop",
    "out_path": "build.sh"
  }
}

The result is an annotated shell script of vibrai commands. Any command that carried a file payload (e.g. notes JSON) gets a sidecar file written next to build.sh.

Replay

Run the script against a fresh Live set to rebuild the arrangement deterministically.

sh build.sh

Notes & limits

Reads are excluded by default. Pass --include-reads / include_reads: true to render read-only calls as live commands too — useful for a full transcript, noisy for a build script.
Raw journal. --format jsonl / format: "jsonl" emits the underlying journal entries instead of a script, for tooling.
Tunable via env vars. VIBRAI_SESSION_DISABLE=1 turns recording off entirely; VIBRAI_SESSION_GAP_MINUTES (default 30) sets the idle gap that starts a new segment; VIBRAI_SESSION_RETENTION_DAYS (default 30) controls how long journal files are kept.

See the Sessions reference for every flag and parameter.

​What gets recorded

​Replay a session

​Notes & limits

What gets recorded

Replay a session

Notes & limits