https://github.com/amalshaji/agent-thread
Share and convert Claude Code and Codex chat sessions
https://github.com/amalshaji/agent-thread
agent-tools bun chat-transcripts claude claude-code cloudflare-workers codex codex-cli nextjs openai
Last synced: 19 days ago
JSON representation
Share and convert Claude Code and Codex chat sessions
- Host: GitHub
- URL: https://github.com/amalshaji/agent-thread
- Owner: amalshaji
- License: mit
- Created: 2026-04-19T15:07:21.000Z (about 2 months ago)
- Default Branch: main
- Last Pushed: 2026-05-19T17:08:58.000Z (29 days ago)
- Last Synced: 2026-05-19T20:39:48.360Z (29 days ago)
- Topics: agent-tools, bun, chat-transcripts, claude, claude-code, cloudflare-workers, codex, codex-cli, nextjs, openai
- Language: TypeScript
- Homepage: https://agent-thread.com
- Size: 439 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Security: SECURITY.md
- Agents: AGENTS.md
Awesome Lists containing this project
README
# agent-thread
Share and inspect Claude Code and Codex chat sessions.
agent-thread is a TypeScript CLI and Next.js share viewer for exporting local agent chats to public links. It uses Bun for development, tests, and builds, while the published CLI is Node-compatible.
## Features
- Claude Code session discovery from `~/.claude/projects`
- Codex thread discovery from `~/.codex/sessions`
- Interactive session picker scoped to the current project
- Public share pages backed by Cloudflare D1 and R2
- Same-app imports for shared Claude Code and Codex sessions
- `bunx agent-thread` CLI entrypoint through the `agent-thread` binary
## CLI Usage
Export the latest Claude Code session to the default hosted service:
```bash
bunx agent-thread --latest
```
Export Codex threads instead:
```bash
bunx agent-thread --codex
```
Point the CLI at a local Cloudflare preview or self-hosted server:
```bash
AGENT_THREAD_SERVER_URL=http://127.0.0.1: bunx agent-thread
AGENT_THREAD_SERVER_URL=https://your-domain.example bunx agent-thread --codex
```
Import a shared session back into the same app it came from:
```bash
bunx agent-thread --import 0c5a0y4a406r
bunx agent-thread --import https://agent-thread.com/t/0c5a0y4a406r --workspace /path/to/project
```
Claude Code exports import into Claude Code. Codex exports import into Codex. Use `--dry-run` to inspect target paths without writing files and `--force` to overwrite an existing local import.
Use `--yes` to confirm uploads in non-interactive scripts after you have reviewed the session content:
```bash
bunx agent-thread --latest --yes
```
## Privacy and Safety
agent-thread uploads the raw Claude Code or Codex transcript files for the selected session, plus a normalized transcript used by the web viewer. These files can include prompts, tool outputs, local file paths, repository names, branch names, environment details, code snippets, and secrets that appeared in the conversation.
Anyone with a public thread link can view the rendered transcript. Anyone with the link can also fetch the export bundle and import it back into the source app. Review sessions before uploading and avoid sharing links publicly unless the transcript is safe to disclose.
## Requirements
- Bun
- A local Claude Code or Codex history if you want to export chats
- Cloudflare account, D1 database, and R2 bucket if you want to self-host the web app
## Local Setup
Install dependencies:
```bash
bun install
```
Run type checks and tests:
```bash
bun run check
bun test
```
Start the Next.js dev server:
```bash
bun run dev
```
The dev server is useful for UI work. Export and share APIs require Cloudflare bindings for D1 and R2, so use `bun run preview` or a deployed Worker when you need the full hosted flow.
## Self-Hosting
agent-thread deploys to Cloudflare Workers through OpenNext. The hosted app needs:
- D1 binding named `DB`
- R2 binding named `SESSIONS_BUCKET`
- `PUBLIC_BASE_URL` set to your public app URL
- `AGENT_THREAD_SERVER_URL` set to the same URL for CLI defaults in the deployed app
Create Cloudflare resources:
```bash
bunx wrangler d1 create agent-thread
bunx wrangler r2 bucket create agent-thread-sessions
```
Use `wrangler.example.toml` as a reference when configuring your deployment. Copy the values into your own `wrangler.toml` and update:
- `database_id` from the D1 create output
- `bucket_name` for your R2 bucket
- `routes` for your domain, or remove the `[[routes]]` block if you deploy to a workers.dev subdomain
- `PUBLIC_BASE_URL` and `AGENT_THREAD_SERVER_URL`
Apply the D1 migration:
```bash
bunx wrangler d1 migrations apply agent-thread
```
Build and test the Worker locally with Cloudflare bindings:
```bash
bun run preview
```
Deploy:
```bash
bun run deploy
```
After deployment, point the CLI at your instance:
```bash
AGENT_THREAD_SERVER_URL=https://your-domain.example bunx agent-thread --latest
```
## Project Scripts
```bash
bun run cli # run the TypeScript CLI locally
bun run dev # run Next.js dev server
bun run preview # build and preview the Cloudflare Worker
bun run deploy # build and deploy to Cloudflare
bun run build # production build plus CLI bundle
bun run check # TypeScript check
bun test # test suite
```
## Data Model
Exports store metadata in D1 and session JSONL payloads in R2. The first migration creates the `uploads` table and indexes public IDs and source session IDs.
The app stores raw source files alongside a normalized transcript representation. Public share pages render from the normalized transcript representation, and same-app imports restore from the raw source files.