Read your agent sessions.
Store runtime-native transcripts from supported agents. Set up your space and runtime
integration once, then launch a session with OWL9_ENABLE=1 to enable
collection. Read the session and follow links to related child sessions when the
runtime provides enough information to discover them.
Install the integration. Choose what to capture.
Install the CLI, choose your own space, and run the setup command for your installed
runtime. The example uses uuidgen to choose a new space and prompts for
a secret of 8–72 bytes. Save that secret before the first upload to keep the space
private; adding a secret later does not turn an existing open space private.
# install, choose a new space, and save its secret $ npm install -g @sys9/cli $ sys9 owl set space "$(uuidgen)" --secret - # install the integration for your runtime $ sys9 owl setup claude-code $ OWL9_ENABLE=1 claude
Keep each session in its native format.
owl9 stores source transcripts and links discoverable child sessions without merging them into a synthetic trace. Collection is limited to enabled sessions and their supported child-session relationships. It does not provide run/span tracing or a complete audit log of every service an agent calls.
# supported runtime integrations $ sys9 owl setup codex $ OWL9_ENABLE=1 codex # other supported runtimes: set up the one you use $ sys9 owl setup pi $ sys9 owl setup opencode
Set up. Capture. Read.
A transcript workflow for the sessions you choose to collect.
Configure your runtime
Install the CLI, configure a unique space and its secret, and run sys9 owl setup for your runtime. When joining an existing space, use its authorized ID and matching secret.
Enable selected sessions
Launch the configured runtime with OWL9_ENABLE=1. Its integration starts collection automatically; supported child-session links preserve the relationship to the parent.
Transcripts for humans
Open the viewer to read uploaded runtime records and navigate related sessions. The public owl9 plugin marketplace supplies the Claude Code and Codex collection integrations.
Integrations for four agent runtimes.
Set up the integration for the runtime installed on your host.
Session context for your agent workflows.
A collected transcript can show the tool calls recorded by the runtime. Each service retains its own operational and audit records.
Sandboxes
Configure owl9 inside a Box to collect supported runtime sessions there.
run9 → smith9Hosted agents
Run hosted agent sessions through Smith9's own session lifecycle.
smith9 → mem9Memory
Give agents memory they can use alongside collected session history.
mem9 → db9Postgres
Use database tools from an agent and inspect what its transcript records.
db9 →Capture your next session.
Install the CLI, configure your space and runtime, then enable collection for the session you want to keep.