Skip to main content

​
How it works

  1. Oobo reads the session transcript from disk
  2. All secrets are redacted using gitleaks patterns (or regex fallback)
  3. Output is a clean JSON document with messages, stats, and metadata
  4. You can save locally, print to stdout, or upload to your configured server

​
Save locally

oobo share <id>                       # preview in terminal
oobo share <id> --out session.json    # save to file
oobo share <id> --agent               # JSON to stdout
Local saves never touch any network.

​
Upload to server

When authenticated, running oobo share without --out uploads to your configured server and returns a shareable URL: 
oobo auth login --key sk-oobo-v1-abc123
oobo share <id>
# → shared: https://app.oobo.ai/s/shr_abc123

​
Self-hosted

oobo auth set-remote https://oobo.mycompany.com
oobo auth login --key sk-oobo-v1-your_key
oobo share <id>

​
Redaction

All session content is redacted before sharing:
  1. gitleaks (if installed): comprehensive secret detection
  2. Regex fallback: API keys, tokens, passwords, AWS credentials
Secrets are replaced with [REDACTED]. No raw secrets ever leave your machine.

​
Output format

{
  "session_id": "abc-123-456",
  "source": "composer",
  "model": "claude-sonnet-4",
  "messages": [
    { "role": "user", "text": "Add auth flow for..." },
    { "role": "assistant", "text": "I'll create the auth module..." }
  ],
  "stats": {
    "input_tokens": 5000,
    "output_tokens": 12000,
    "duration_secs": 120
  },
  "shared_at": "2026-03-04T12:00:00Z",
  "oobo_version": "0.1.0"
}