Trajectory normalizes coding-agent session transcripts into stable, versioned records you can store, search, replay, evaluate, train on, and observe.
One product. Four native packages. The same wire contracts and conformance suite in every ecosystem.
| Ecosystem | Package | Install |
|---|---|---|
| .NET | Hypabolic.Trajectory |
dotnet add package Hypabolic.Trajectory |
| TypeScript | @hypabolic/trajectory |
npm install @hypabolic/trajectory |
| Rust | hypabolic-trajectory |
cargo add hypabolic-trajectory |
| Python | hypabolic-trajectory |
pip install hypabolic-trajectory |
Optional OpenTelemetry: Hypabolic.Trajectory.OpenTelemetry,
@hypabolic/trajectory-otel, hypabolic-trajectory-opentelemetry, and Python
extra hypabolic-trajectory[otel] (SDK sinks only — pure OTEL project is in core).
Optional live-session stream packages (0.1.3+): Hypabolic.Trajectory.IO /
.Ahp / .Hermes, @hypabolic/trajectory-node (file I/O) / trajectory-ahp /
trajectory-hermes, hypabolic-trajectory-io / -ahp / -hermes, and Python
extras hypabolic-trajectory[io] / [ahp] / [hermes].
Releases use the git tag as the version (same model as Hypa): push
vX.Y.Z and CI stamps packages, publishes NuGet/npm/crates/PyPI, and creates a
GitHub Release. See docs/publishing.md.
Published vs this tree: Latest synchronized registry cut is
0.1.3(NuGet / npm / crates / PyPI): prior sources plus live session streaming (core apply APIs, optional file I/O / AHP client / Hermes provider packages, sample CLI follow).0.1.2was Grok Build + AHP Shape A without stream engines. Install commands without a version pin resolve to the latest published tag.
- Multi-source ingest — Pi, Claude Code, Codex, OpenClaw, Hermes, AHP
(Shape A offline ChatState snapshots), Grok Build (
grok-build), and Cursor Agent (cursor) - Deterministic normalization — stable IDs, ordering, hashes, content-safe diagnostics
- Multiple outputs from one decode: Hypabolic trajectory, canonical identity, compact message arrays, OpenAI chat messages, minimal JSONL, and optional OpenTelemetry GenAI spans
- Local store listing with explicit roots and pagination
- Partial / chunked input where the source supports append-only sessions
- Live session streaming (library, not a daemon) — follow a growing JSONL session or AHP chat and receive snapshot + delta updates. See How to stream below.
- Native AOT–friendly .NET, ESM TypeScript (Node 22+), Rust 2024 (MSRV 1.85), Python 3.11+
# .NET
dotnet add package Hypabolic.Trajectory
# optional: dotnet add package Hypabolic.Trajectory.OpenTelemetry
# optional stream packages (0.1.3+):
# dotnet add package Hypabolic.Trajectory.IO
# dotnet add package Hypabolic.Trajectory.Ahp
# dotnet add package Hypabolic.Trajectory.Hermes
# TypeScript
npm install @hypabolic/trajectory
npm install @hypabolic/trajectory-node # local listing + stream file I/O
# optional: npm install @hypabolic/trajectory-otel
# optional stream packages (0.1.3+):
# npm install @hypabolic/trajectory-ahp
# npm install @hypabolic/trajectory-hermes
# Rust
cargo add hypabolic-trajectory
# optional: cargo add hypabolic-trajectory-opentelemetry
# optional stream packages (0.1.3+):
# cargo add hypabolic-trajectory-io
# cargo add hypabolic-trajectory-ahp
# cargo add hypabolic-trajectory-hermes
# Python (published from 0.1.1; pin a tag when you need a fixed cut)
pip install hypabolic-trajectory
# optional SDK sinks only:
pip install 'hypabolic-trajectory[otel]'
# optional stream extras (same wheel; 0.1.3+):
# pip install 'hypabolic-trajectory[io]'
# pip install 'hypabolic-trajectory[ahp]'
# pip install 'hypabolic-trajectory[hermes]'
# monorepo / tip checkout:
# python -m pip install -e './python[dev]'Trajectory is two steps:
- Find sessions in the agent’s local store (listing APIs know default roots)
- Normalize the transcript bytes into projections
You only pass a raw path when you already have one (export, upload, pipe). For “what’s on this machine?”, use listing first.
using Hypabolic.Trajectory;
// Discover Claude Code sessions under the default root (~/.claude/projects)
var page = await TrajectoryConverter.ListClaudeCodeTrajectoriesAsync(limit: 20);
var session = page.Items[0]; // Path, Id, UpdatedAt, …
byte[] transcript = await File.ReadAllBytesAsync(session.Path);
var engine = TrajectoryEngine.CreateDefault();
var ir = engine.NormalizeToIR(new NormalizeInput
{
Source = TrajectorySource.ClaudeCode,
Transcript = transcript,
});
var hypabolic = engine.Project<HypabolicTrajectoryV1>(
ir, OutputSchemaIds.HypabolicTrajectoryV1);
var canonical = engine.Project<LettaCanonicalResult>(
ir, OutputSchemaIds.LettaCanonicalV1);
var messages = TrajectoryConverter.NormalizeTranscript(
TrajectorySource.ClaudeCode, transcript);Same idea for any source (ListPiTrajectoriesAsync, ListCodexTrajectoriesAsync,
or ListTrajectoriesAsync(TrajectorySource.OpenClaw)). Pass root: to override
the default store. Codex partial/chunked input can still set GroupId and
BaseByteOffset when you feed append-only slices.
import { readFileSync } from "node:fs";
import { homedir } from "node:os";
import { join } from "node:path";
import {
normalizeToHypabolic,
normalizeToCanonical,
normalizeToLetta,
} from "@hypabolic/trajectory";
import { listClaudeCodeTrajectories } from "@hypabolic/trajectory-node";
// Node listing package — pass the store root (defaults are not assumed)
const page = await listClaudeCodeTrajectories({
root: join(homedir(), ".claude", "projects"),
limit: 20,
});
const session = page.items[0]; // id, path, updatedAt, sizeBytes
const transcriptBytes = readFileSync(session.path);
const request = {
source: "claude-code" as const,
transcriptBytes,
sourceContext: { partial: false },
};
const hypabolic = normalizeToHypabolic(request);
const canonical = normalizeToCanonical(request);
const messages = normalizeToLetta(request); // compact message trajectoryAlso: listPiTrajectories, listCodexTrajectories, listOpenClawTrajectories.
Rust listing always takes an explicit root (no home-directory default in
the library; the sample CLI applies the usual ~/.claude/projects etc.).
use std::fs;
use std::path::Path;
use hypabolic_trajectory::{
list_claude_code_trajectories, normalize_claude_code, project_canonical,
project_hypabolic, ListingOptions, NormalizeRequest,
};
let page = list_claude_code_trajectories(&ListingOptions {
root: Path::new("/home/you/.claude/projects"),
limit: 20,
cursor: None,
})?;
let session = &page.items[0]; // id, path, updated_at, size_bytes
let bytes = fs::read(&session.path)?;
let ir = normalize_claude_code(NormalizeRequest {
transcript: &bytes,
..Default::default()
})?;
let hypabolic = project_hypabolic(&ir)?;
let canonical = project_canonical(&ir)?;Also: list_pi_trajectories, list_codex_trajectories, list_openclaw_trajectories
with matching normalize_* helpers.
Listing always takes an explicit root (no home-directory default in the library). Pure OTEL GenAI projection needs no OpenTelemetry SDK.
from pathlib import Path
from hypabolic_trajectory import (
NormalizeRequest,
TrajectorySource,
list_trajectories,
normalize_to_ir,
project_canonical,
project_hypabolic,
project_otel_genai,
serialize_projection,
)
page = list_trajectories(
source=TrajectorySource.CLAUDE_CODE,
root=Path.home() / ".claude" / "projects",
limit=20,
)
session = page.items[0]
ir = normalize_to_ir(
NormalizeRequest(
source=TrajectorySource.CLAUDE_CODE,
transcript=Path(session.path).read_bytes(),
)
)
hypabolic = project_hypabolic(ir)
canonical = project_canonical(ir)
spans = project_otel_genai(ir) # pure; no opentelemetry-* required
wire = serialize_projection(hypabolic)Also: any wire source name ("pi", "codex", "openclaw", "hermes", "ahp",
…). Package docs: python/README.md (filters, dual
timestamps, identity formulas, OTEL import matrix, filtered conformance argv).
| Source | Typical input | Default local store |
|---|---|---|
| Pi | Session JSONL | ~/.pi/agent (PI_CODING_AGENT_DIR) |
| Claude Code | Session JSONL | ~/.claude/projects |
| Codex | Rollout JSONL | ~/.codex/sessions |
| OpenClaw | Session JSONL | ~/.openclaw or legacy ~/.clawdbot |
| Hermes | Message array or { session, messages } JSON |
Export file; core listing is SQLite-free |
| AHP | Shape A chat snapshot { chat, session? } JSON |
Export file only; listing is Phase 3 (empty stub) |
| Grok Build | chat_history.jsonl (alias grok) |
$GROK_HOME/sessions or ~/.grok/sessions |
| Cursor Agent | <session-id>.jsonl (alias cursor-agent) |
$CURSOR_HOME or ~/.cursor |
Override listing roots with --root / TRAJECTORY_<SOURCE>_ROOT in the sample
CLIs, or pass an explicit root to listing APIs.
Trajectory is a library, not a daemon. Your process owns lifetime, paths,
and (for AHP) transport. The core applies complete JSONL lines or AHP
snapshots/actions and emits a StreamUpdate with a snapshot, a record delta,
and a cursor you can persist.
Product model: docs/live-session-streaming.md.
Wire contract: contracts/spec/streaming.md.
Apply API: docs/streaming-core-api.md.
File follow: docs/streaming-file-io.md.
Unpublished monorepo samples — pick a session from the local store and follow it as complete lines are committed.
# .NET
dotnet run --project dotnet/samples/Trajectory.Cli -- \
browse --source grok-build --watch --show-content
# Rust
cargo run -p trajectory-cli --manifest-path rust/Cargo.toml -- \
browse --source grok-build --watch --show-contentWhat you get:
- Sessions sorted by last-active time (
just now,5m ago, …). - A live tail of the latest records (not the start of the transcript).
- A ticking
watchingline until the JSONL grows by a complete line.
--watch skips the Watch live / Show snapshot prompt. --show-content prints
text snippets (private). Ctrl-C stops follow.
Grok Build: the stream tails chat_history.jsonl. Items appear when Grok
commits a finished conversation item — not token-by-token updates.jsonl.
Other file sources work the same: pi, claude-code, codex, openclaw.
# Follow a known path (one poll unless --follow)
dotnet run --project dotnet/samples/Trajectory.Cli -- stream \
--source pi --path path/to/session.jsonl --follow --show-contentInstall the optional I/O package and poll or iterate. Only LF-terminated lines become records; a partial last line stays pending.
using Hypabolic.Trajectory;
using Hypabolic.Trajectory.IO;
using Hypabolic.Trajectory.Streaming;
await using var stream = FileTrajectoryStream.Open(new FileTrajectoryStreamOptions
{
Root = root, // store root that contains Path
Path = sessionPath, // e.g. chat_history.jsonl
Source = TrajectorySource.GrokBuild,
GroupId = sessionId, // Grok listing id (session UUID)
});
await foreach (var update in stream.FollowAsync(ct))
{
// update.Kind: updated | unchanged | reset-required | error
// update.Snapshot.Records — full current view
// update.Delta.Operations — upserts / removes since last revision
// update.Cursor — persist this to resume
}from hypabolic_trajectory.io import FileStreamOptions, FileTrajectoryStream
fs = FileTrajectoryStream.open(FileStreamOptions(
root=root, path=session_path, source="grok-build", group_id=session_id,
))
try:
for update in fs.follow(interval=0.05):
print(update.kind, len(update.snapshot.records) if update.snapshot else 0)
finally:
fs.close()import { openFileStream } from "@hypabolic/trajectory-node";
const stream = openFileStream({
root, path, source: "grok-build", groupId: sessionId,
});
for (;;) {
const update = await stream.poll();
if (update && update.kind !== "unchanged") { /* … */ }
}use hypabolic_trajectory::TrajectorySource;
use hypabolic_trajectory_io::{FileStreamOptions, FileTrajectoryStream};
let mut stream = FileTrajectoryStream::open(FileStreamOptions {
root, path, source: TrajectorySource::GrokBuild,
group_id: Some(session_id),
..Default::default()
})?;
if let Some(update) = stream.poll()? { /* … */ }If you already own I/O, skip the file package and call core apply_snapshot /
apply_append (or apply_ahp_*) yourself. Portable resume is cursor +
re-apply source material, not serialized IR.
AHP live hosts: inject your own WebSocket AhpTransport into
Hypabolic.Trajectory.Ahp / @hypabolic/trajectory-ahp /
hypabolic-trajectory-ahp / hypabolic_trajectory.ahp_client. Samples only
demo fake://. See docs/ahp-client.md.
Unpublished developer tools that list agent stores on disk, normalize a selected session into a privacy-safe summary (counts, roles, tools, diagnostics—no transcript body by default), or watch a live JSONL session as it grows.
| Runtime | Path | Binary / entry |
|---|---|---|
| .NET | dotnet/samples/Trajectory.Cli |
dotnet run --project … |
| TypeScript | typescript/packages/trajectory-cli |
node packages/trajectory-cli/dist/cli.js |
| Rust | rust/tools/trajectory-cli |
cargo run -p trajectory-cli |
| Python | python/samples/trajectory_cli |
PYTHONPATH=python/samples python -m trajectory_cli |
| Command | Purpose |
|---|---|
browse (default) |
Interactive: pick source → session → Watch live or Show snapshot |
list |
Table of sessions for one source |
show |
Normalize one --path or listing --id |
stream |
Follow a JSONL session file (optional file I/O + core stream) |
ahp-stream |
Optional AHP client demo (fake:// FakeAhpHost) |
Shared flags:
| Flag | Meaning |
|---|---|
--source <name> |
pi, claude-code, codex, openclaw, hermes, ahp, grok-build, cursor (aliases grok, cursor-agent) |
--root <path> |
Override store root |
--limit <n> |
Listing page size (default 50) |
--format <f> |
both (default), messages, or hypabolic |
--show-content |
Include text snippets (private data; prints a warning) |
--path / --id |
show / stream / browse: file path or listing id |
--emit |
stream / browse --watch / ahp-stream: snapshot+delta (default), snapshot, or delta |
--follow |
stream: keep polling until process exit (not a daemon) |
--watch |
browse: after picking a session, follow it live (skip the action prompt) |
--url / --chat |
ahp-stream: host URL (fake:// in samples) and chat URI |
These CLIs are consumer processes, not Trajectory daemons. Stream follow ends
when the process exits; sample ahp-stream uses in-memory FakeAhpHost only
(wire your own WebSocket AhpTransport for live hosts).
# .NET — list Claude Code sessions, then show a fixture
dotnet run --project dotnet/samples/Trajectory.Cli -- list --source claude-code --limit 10
dotnet run --project dotnet/samples/Trajectory.Cli -- show \
--source pi \
--path conformance/cases/pi/tool-calls/input.jsonl
dotnet run --project dotnet/samples/Trajectory.Cli -- browse --source codex
# TypeScript
cd typescript && npm ci && npm run build
node packages/trajectory-cli/dist/cli.js list --source pi
node packages/trajectory-cli/dist/cli.js show \
--source pi \
--path ../conformance/cases/pi/tool-calls/input.jsonl \
--format hypabolic
node packages/trajectory-cli/dist/cli.js browse
# Rust
cargo run -p trajectory-cli --manifest-path rust/Cargo.toml -- list --source codex
cargo run -p trajectory-cli --manifest-path rust/Cargo.toml -- show \
--source hermes \
--path conformance/cases/hermes/tool-calls/input.json
cargo run -p trajectory-cli --manifest-path rust/Cargo.toml -- show \
--source ahp \
--path conformance/cases/ahp/tool-calls/input.json
# Python (unpublished sample)
# Prefer editable install so hypabolic_trajectory resolves without hand-rolled PYTHONPATH:
python -m pip install -e './python[dev]'
# (Alternatively: PYTHONPATH=python/src:python/samples …)
PYTHONPATH=python/samples python -m trajectory_cli list --source pi
PYTHONPATH=python/samples python -m trajectory_cli show \
--source pi \
--path conformance/cases/pi/tool-calls/input.jsonl
PYTHONPATH=python/samples python -m trajectory_cli browse
# Watch a live local session (pick from the store, then Watch live)
dotnet run --project dotnet/samples/Trajectory.Cli -- browse --source grok-build
# or skip the action prompt:
dotnet run --project dotnet/samples/Trajectory.Cli -- browse --source grok-build --watch --show-content
cargo run -p trajectory-cli --manifest-path rust/Cargo.toml -- browse --source grok-build --watch --show-content
# Stream a fixture once (all four CLIs; default emit snapshot+delta)
# After editable install above (or PYTHONPATH=python/src:python/samples):
PYTHONPATH=python/samples python -m trajectory_cli stream \
--source pi \
--path conformance/cases/pi/tool-calls/input.jsonl \
--max-updates 1Notes
- Empty or missing stores exit successfully with a clear message.
- Hermes listing in core returns empty (no SQLite dependency); export JSON and
show --path. - AHP listing is Phase 3; normalize Shape A snapshots with
show --path. - Live streaming sample commands compose optional file I/O / AHP client packages; core stays free of watchers, network, and SQLite. Not a background daemon.
- These CLIs are not published NuGet/npm/crates packages.
native source bytes
→ source decoder
→ shared normalization policy
→ private intermediate representation
→ versioned output adapters
Implementations are independent per language. Behaviour is locked by shared
contracts (contracts/) and executable cases (conformance/).
contracts/ versioned schemas and behavioural specifications
conformance/ shared fixtures, goldens, verify.py, private runners’ protocol
dotnet/ libraries, tests, AOT smoke, sample CLI
typescript/ npm packages, tests, sample CLI
rust/ crates, conformance binary, sample CLI
python/ PyPI package, tests, unpublished conformance runner
docs/ architecture, authoring, contributing, publishing
tools/ release, packaging, and npm bootstrap helpers
dotnet restore dotnet/Trajectory.sln
dotnet build dotnet/Trajectory.sln -c Release --no-restore
dotnet test dotnet/tests/Trajectory.Tests/Trajectory.Tests.csproj -c Release --no-buildcd typescript && npm ci && npm run typecheck && npm testcargo test --manifest-path rust/Cargo.toml --workspace --lockedpython -m pip install -e './python[dev]'
python -m pytest python/tests -qdotnet build dotnet/tests/Trajectory.Conformance/Trajectory.Conformance.csproj -c Release
python3 conformance/verify.py --repository-root . -- \
dotnet dotnet/tests/Trajectory.Conformance/bin/Release/net10.0/trajectory-conformance.dll
# Python tip suite (protocol v1 runner is monorepo-only, not a PyPI script):
python conformance/verify.py --repository-root . -- \
env PYTHONPATH=python/src:python/tools python -m trajectory_conformanceSee conformance/README.md for case authoring and all
runners. Python package docs (imports, filters, dual timestamps, formulas,
OTEL matrix, filtered argv): python/README.md.
We welcome issues and PRs that improve adapters, fixtures, docs, and packaging.
- Read Contributing for setup, PR checklist, and fixture privacy rules.
- For new agent sources or output formats, follow Authoring sources and outputs (multi-runtime) and the .NET adapter seams when on C#.
- Behaviour changes need shared conformance cases reviewed by hand—never auto-accept goldens in CI.
- Identity-bearing output bytes do not change under the same normalizer contract
version (
0.2.0today). - Diagnostics are typed and content-safe by contract.
- Capabilities are advertised only after shared cases pass.
- Pre-1.0 package versions stay synchronized across ecosystems.
| Doc | Contents |
|---|---|
| Architecture | Pipeline, packages, design principles |
| Adapter authoring | New sources and outputs (all runtimes) |
| Contributing | Setup, PR checklist, workflows |
| Hypabolic trajectory format | Provenance-rich output |
| OpenTelemetry GenAI | Span projection and privacy |
| Publishing | NuGet / npm / crates release |
| Release readiness | Privacy, packaging, 1.0 gates |
| Live session streaming | Library stream model, cursor, snapshot + delta |
| AHP source design | Agent Host Protocol ingest design |
| Normative specs | Identity, timestamps, diagnostics |
| Conformance | Shared cases and runners |
MIT — see LICENSE.