agent-exporter

agent-exporter is a local-first archive and governance workbench for AI agent transcripts.

This Pages home is not a second primary door. It is a lighter public companion surface that helps a first-time visitor answer:

  1. what this repo actually is
  2. how to get the first successful result
  3. what the archive shell proof really proves

Front Door Rule

In plain language:

Pages explains the door. The real primary entrance is still the CLI quickstart in the GitHub repo.

Run This First

If you only want to try the repo once, do not start by reading every surface. Run these three steps first:

  1. cargo run -- connectors
  2. cargo run -- export codex --thread-id <thread-id> --format html --destination workspace-conversations --workspace-root /absolute/path/to/repo
  3. cargo run -- publish archive-index --workspace-root /absolute/path/to/repo

First Success In 3 Steps

  1. Inspect the current connector surface
cargo run -- connectors
  1. Export one HTML transcript into the current workspace
cargo run -- export codex \
  --thread-id <thread-id> \
  --format html \
  --destination workspace-conversations \
  --workspace-root /absolute/path/to/repo
  1. Publish the archive shell proof
cargo run -- publish archive-index --workspace-root /absolute/path/to/repo

Success signals:

You Will Get

This Does Not Mean

Host-Native Packet Status

The public skill packet already has lane-specific truth:

That does not change the product hierarchy. The host-native packet remains a secondary public lane.

Release Shelf Truth

Use the latest release entrypoint when you want the newest published release packet.

Use the repo front door and Pages docs when you want the newest repository-side truth on main.

Those are neighboring shelves, not the same shelf. A newer main can sharpen public wording or packet truth before the next tagged release exists.

Start Here

Current Public Boundary