agenticreplay 0.1.0 → 0.1.2

package/examples/traces/README.md

@@ -1,50 +0,0 @@
-# Example traces
-
-Real-shaped traces, checked into the repo on purpose. They do four jobs at once:
-
-1. **Documentation.** The fastest way to understand the format is to read one.
-2. **Contributor fixtures.** Everything here works against these on day one, no recording needed.
-3. **Conformance input.** `scripts/conformance.mjs` validates each against the normative schema in
-   CI — that is what makes v0 a format others can target rather than whatever our writer emits.
-   The same job also validates a trace the writer produces on the spot, so "the format" and "our
-   implementation of it" are checked separately rather than one standing in for the other.
-4. **Evaluation.** Anyone can inspect the project without installing it.
-
-**These are hand-written**, and that is the point of job 1 and job 3 — a fixture our own writer
-produced could not demonstrate that someone else's implementation is possible. Treat them as what
-the format allows, not as a transcript of what `agenticreplay record` produces today.
-
-That licence has one limit, and this fixture used to break it: it carried a recorded `checkpoint`
-event. Spec §3 says a checkpoint is *derived* at read time and never recorded, so shipping one
-taught every implementer reading the example to emit the one event the format says not to. It is
-gone. `error` and a populated `manifest.git` stay — the recorder produces both now.
-
-The conformance run prints which declared event types no shipped trace exercises, so any drift
-between the format and the recorder stays visible rather than becoming folklore.
-
-## `run_9f2c14a03b71`
-
-A coding agent chasing a failing auth test. It reads `src/auth.ts`, greps for `JWT`, makes a
-correct-looking edit at turn 3, runs the tests, and fails — then repeats the same edit for two more
-turns without changing the tree, which the `note` event at seq 24 flags as a loop.
-
-The interesting part is seq 13: the `fs.snapshot` after that first edit. Everything up to it is
-identical no matter which model you hand the rest of the run to, which is what makes
-`agenticreplay replay --from 13 --model <other>` a controlled experiment rather than an anecdote — and a
-checkpoint is exactly that snapshot plus a complete conversation prefix, worked out by the reader
-rather than written down by the recorder.
-
-Poke at it with nothing but `jq`:
-
-```console
-# what did each turn do?
-jq -r '"\(.seq)\t\(.type)\t\(.attrs.path // .attrs.name // .attrs.model // "")"' events.jsonl
-
-# where did it go wrong?
-jq 'select(.type == "error")' events.jsonl
-
-# what did the whole thing cost in tokens?
-jq -s 'map(.attrs.input_tokens // 0) | add' events.jsonl
-```
-
-That those questions are answerable without any AgenticReplay code is the point of the format.

package/examples/traces/run_9f2c14a03b71/blobs/1b/1b694f32b8c582ace6b35ad64050e532fb3ee3ecc1a2763a82cf42ad0f2a3dd0

@@ -1,10 +0,0 @@
-{
-  "model": "claude-opus-5",
-  "max_tokens": 8192,
-  "messages": [
-    {
-      "role": "user",
-      "content": "the auth refresh test is failing, fix it"
-    }
-  ]
-}

package/examples/traces/run_9f2c14a03b71/blobs/51/517b5b8ec6c3b13121dbaec61784e2a024247c7c4efd9ba068b582ee57bd2764

@@ -1,4 +0,0 @@
-src/auth.ts:14  import { verify } from "jsonwebtoken"
-src/auth.ts:88  // JWT exp is seconds since epoch
-src/auth.ts:91  if (payload.exp < Date.now()) {
-src/session.ts:22  const JWT_TTL = 900

package/examples/traces/run_9f2c14a03b71/blobs/5b/5bba1bd069013d86363f69c00c1ae77c84c4e113aeeb7431c8141af4fed76860

@@ -1,7 +0,0 @@
-export function isExpired(payload: JwtPayload): boolean {
-  // JWT exp is seconds since epoch
-  if (payload.exp < Date.now()) {
-    return true;
-  }
-  return false;
-}

package/examples/traces/run_9f2c14a03b71/blobs/84/84247e7b385fd5f99a6728a509838e52ef963af92f44ef6eccbed6910de1438d

@@ -1,10 +0,0 @@
-FAIL  test/auth.test.ts
-  ● refreshes a token that expired during the request
-
-    expect(refreshed).toBe(true)
-
-    Received: false
-
-      at test/auth.test.ts:41:24
-
-Tests:  1 failed, 13 passed, 14 total

package/examples/traces/run_9f2c14a03b71/blobs/ac/ac9b4be9bdf7fe63c7b5135e2d14c4c0745a48771e733804869790590455f8e8

@@ -1,7 +0,0 @@
-@@ -88,7 +88,9 @@ export function isExpired(payload: JwtPayload): boolean {
-   // JWT exp is seconds since epoch
--  if (payload.exp < Date.now()) {
-+  const now = Math.floor(Date.now() / 1000);
-+  if (payload.exp < now) {
-     return true;
-   }

package/examples/traces/run_9f2c14a03b71/events.jsonl

@@ -1,31 +0,0 @@
-{"seq":0,"ts":"2026-08-29T10:13:39.400Z","mono_us":1400000,"turn":0,"type":"run.start","actor":"agenticreplay","attrs":{"adapter":"claude-code","cwd":"/home/dev/api"}}
-{"seq":1,"ts":"2026-08-29T10:13:40.800Z","mono_us":2800000,"turn":0,"type":"fs.snapshot","actor":"agenticreplay","attrs":{"tree":"3ab77f19c4e2a58d0b6f1e93c72d4a80b5e6f712","files":214}}
-{"seq":2,"ts":"2026-08-29T10:13:42.200Z","mono_us":4200000,"turn":1,"type":"model.request","actor":"agent","attrs":{"model":"claude-opus-5","messages":9,"tools":9},"payload":{"$blob":"sha256:1b694f32b8c582ace6b35ad64050e532fb3ee3ecc1a2763a82cf42ad0f2a3dd0","bytes":167,"media_type":"application/json"}}
-{"seq":3,"ts":"2026-08-29T10:13:43.600Z","mono_us":5600000,"turn":1,"type":"model.response","actor":"model","causes":[2],"attrs":{"stop_reason":"tool_use","input_tokens":6120,"output_tokens":188}}
-{"seq":4,"ts":"2026-08-29T10:13:45.000Z","mono_us":7000000,"turn":1,"type":"tool.call","actor":"model","causes":[3],"attrs":{"name":"read_file","path":"src/auth.ts"}}
-{"seq":5,"ts":"2026-08-29T10:13:46.400Z","mono_us":8400000,"turn":2,"type":"tool.result","actor":"harness","causes":[4],"attrs":{"name":"read_file","bytes":167},"payload":{"$blob":"sha256:5bba1bd069013d86363f69c00c1ae77c84c4e113aeeb7431c8141af4fed76860","bytes":167,"media_type":"text/x-typescript"}}
-{"seq":6,"ts":"2026-08-29T10:13:47.800Z","mono_us":9800000,"turn":2,"type":"model.request","actor":"agent","causes":[5],"attrs":{"model":"claude-opus-5","messages":11,"tools":9}}
-{"seq":7,"ts":"2026-08-29T10:13:49.200Z","mono_us":11200000,"turn":2,"type":"model.response","actor":"model","causes":[6],"attrs":{"stop_reason":"tool_use","input_tokens":7204,"output_tokens":141}}
-{"seq":8,"ts":"2026-08-29T10:13:50.600Z","mono_us":12600000,"turn":2,"type":"tool.call","actor":"model","causes":[7],"attrs":{"name":"grep","pattern":"JWT","glob":"src/**"}}
-{"seq":9,"ts":"2026-08-29T10:13:52.000Z","mono_us":14000000,"turn":3,"type":"tool.result","actor":"harness","causes":[8],"attrs":{"name":"grep","hits":11},"payload":{"$blob":"sha256:517b5b8ec6c3b13121dbaec61784e2a024247c7c4efd9ba068b582ee57bd2764","bytes":191,"media_type":"text/plain"}}
-{"seq":10,"ts":"2026-08-29T10:13:53.400Z","mono_us":15400000,"turn":3,"type":"model.request","actor":"agent","causes":[9],"attrs":{"model":"claude-opus-5","messages":13,"tools":9}}
-{"seq":11,"ts":"2026-08-29T10:13:54.800Z","mono_us":16800000,"turn":3,"type":"model.response","actor":"model","causes":[10],"attrs":{"stop_reason":"tool_use","input_tokens":8412,"output_tokens":214}}
-{"seq":12,"ts":"2026-08-29T10:13:56.200Z","mono_us":18200000,"turn":3,"type":"tool.call","actor":"model","causes":[11],"attrs":{"name":"edit_file","path":"src/auth.ts"}}
-{"seq":13,"ts":"2026-08-29T10:13:57.600Z","mono_us":19600000,"turn":3,"type":"fs.snapshot","actor":"agenticreplay","attrs":{"tree":"9c1e4bd7f0a3821e5c94b6d2087fa31c4e5b9d63","files":214}}
-{"seq":14,"ts":"2026-08-29T10:13:59.000Z","mono_us":21000000,"turn":3,"type":"fs.change","actor":"agenticreplay","causes":[13],"attrs":{"path":"src/auth.ts","status":"modified","insertions":18,"deletions":4},"payload":{"$blob":"sha256:ac9b4be9bdf7fe63c7b5135e2d14c4c0745a48771e733804869790590455f8e8","bytes":245,"media_type":"text/x-diff"}}
-{"seq":15,"ts":"2026-08-29T10:14:00.400Z","mono_us":22400000,"turn":3,"type":"shell.exec","actor":"harness","causes":[12],"attrs":{"argv":["npm","test","--","auth"],"cwd":"/home/dev/api"}}
-{"seq":16,"ts":"2026-08-29T10:14:01.800Z","mono_us":23800000,"turn":3,"type":"shell.result","actor":"harness","causes":[15],"attrs":{"exit_code":1,"duration_ms":8412,"stdout_bytes":206},"payload":{"$blob":"sha256:84247e7b385fd5f99a6728a509838e52ef963af92f44ef6eccbed6910de1438d","bytes":208,"media_type":"text/plain"}}
-{"seq":17,"ts":"2026-08-29T10:14:03.200Z","mono_us":25200000,"turn":3,"type":"error","actor":"agenticreplay","causes":[16],"attrs":{"kind":"test_failure","failed":1,"passed":13,"total":14,"suite":"test/auth.test.ts"}}
-{"seq":18,"ts":"2026-08-29T10:14:06.000Z","mono_us":28000000,"turn":4,"type":"model.request","actor":"agent","causes":[17],"attrs":{"model":"claude-opus-5","messages":15,"tools":9}}
-{"seq":19,"ts":"2026-08-29T10:14:07.400Z","mono_us":29400000,"turn":4,"type":"model.response","actor":"model","causes":[18],"attrs":{"stop_reason":"tool_use","input_tokens":9004,"output_tokens":188}}
-{"seq":20,"ts":"2026-08-29T10:14:08.800Z","mono_us":30800000,"turn":4,"type":"fs.snapshot","actor":"agenticreplay","attrs":{"tree":"9c1e4bd7f0a3821e5c94b6d2087fa31c4e5b9d63","files":214}}
-{"seq":21,"ts":"2026-08-29T10:14:10.200Z","mono_us":32200000,"turn":5,"type":"model.request","actor":"agent","causes":[19],"attrs":{"model":"claude-opus-5","messages":17,"tools":9}}
-{"seq":22,"ts":"2026-08-29T10:14:11.600Z","mono_us":33600000,"turn":5,"type":"model.response","actor":"model","causes":[21],"attrs":{"stop_reason":"tool_use","input_tokens":9610,"output_tokens":203}}
-{"seq":23,"ts":"2026-08-29T10:14:13.000Z","mono_us":35000000,"turn":5,"type":"fs.snapshot","actor":"agenticreplay","attrs":{"tree":"9c1e4bd7f0a3821e5c94b6d2087fa31c4e5b9d63","files":214}}
-{"seq":24,"ts":"2026-08-29T10:14:14.400Z","mono_us":36400000,"turn":5,"type":"note","actor":"agenticreplay","attrs":{"rule":"identical_tree_across_turns","turns":[3,4,5],"wasted_tokens":27026}}
-{"seq":25,"ts":"2026-08-29T10:14:14.680Z","mono_us":36680000,"turn":5,"type":"agent.start","actor":"harness","attrs":{"name":"Triage","handoffs":"Billing Specialist","tools":0,"output_type":"str"}}
-{"seq":26,"ts":"2026-08-29T10:14:14.960Z","mono_us":36960000,"turn":5,"type":"agent.guardrail","actor":"harness","attrs":{"name":"not_empty","triggered":false}}
-{"seq":27,"ts":"2026-08-29T10:14:15.240Z","mono_us":37240000,"turn":5,"type":"agent.handoff","actor":"harness","attrs":{"from":"Triage","to":"Billing Specialist"}}
-{"seq":28,"ts":"2026-08-29T10:14:15.430Z","mono_us":37430000,"turn":5,"type":"graph.node.start","actor":"harness","attrs":{"node":"summarise_invoice","step":1,"run_id":"3f6a1c8e-0b2d-4f51-9c77-1a5be2d40c93","parent_run_id":"9d4c7b12-5e83-4a06-b1f2-77c0ae35d918","started_at":"2026-08-29T10:14:15.430Z"}}
-{"seq":29,"ts":"2026-08-29T10:14:15.610Z","mono_us":37610000,"turn":5,"type":"graph.node.end","actor":"harness","attrs":{"node":"summarise_invoice","step":1,"run_id":"3f6a1c8e-0b2d-4f51-9c77-1a5be2d40c93","ended_at":"2026-08-29T10:14:15.610Z"}}
-{"seq":30,"ts":"2026-08-29T10:14:15.800Z","mono_us":37800000,"turn":5,"type":"run.end","actor":"agenticreplay","attrs":{"exit_code":1}}

package/examples/traces/run_9f2c14a03b71/manifest.json

@@ -1,46 +0,0 @@
-{
-  "schema_version": "0.4.0",
-  "run_id": "run_9f2c14a03b71",
-  "created_at": "2026-08-29T10:13:38.000Z",
-  "ended_at": "2026-08-29T10:18:29.000Z",
-  "agenticreplay_version": "0.1.0",
-  "adapter": {
-    "id": "claude-code",
-    "version": "0.1.0",
-    "harness_version": "2.1.4"
-  },
-  "argv": [
-    "claude"
-  ],
-  "cwd": "/home/dev/api",
-  "env_allowlisted": {
-    "TERM": "xterm-256color",
-    "LANG": "en_US.UTF-8"
-  },
-  "git": {
-    "head": "4f1a9c02e7b8d3516a0c9e4f27b8d150a3c6e9f2",
-    "branch": "fix/auth-refresh",
-    "dirty": true
-  },
-  "platform": {
-    "os": "linux",
-    "arch": "x64",
-    "node": "v22.22.2"
-  },
-  "counts": {
-    "events": 31,
-    "blobs": 5
-  },
-  "redaction": {
-    "policy_version": 1,
-    "rules_fired": {
-      "auth_header": 12,
-      "high_entropy": 1
-    }
-  },
-  "exit_code": 1,
-  "integrity": {
-    "events_sha256": "521e28d9e4662248759797a0e05224170879bd1e64232cf6d2ee8217d6ff038e",
-    "blob_count": 5
-  }
-}

package/examples/traces/run_9f2c14a03b71/redactions.json

@@ -1,17 +0,0 @@
-{
-  "policy_version": 1,
-  "records": [
-    {
-      "rule": "auth_header",
-      "identifier": "header.x-api-key",
-      "placeholder": "<secret:api_key:8f3ad91c>",
-      "count": 12
-    },
-    {
-      "rule": "high_entropy",
-      "identifier": "shell.env.DEPLOY_TOKEN",
-      "placeholder": "<secret:high_entropy:2b7c40de>",
-      "count": 1
-    }
-  ]
-}

package/llms.txt

@@ -1,26 +0,0 @@
-# AgenticReplay
-
-> Records a coding-agent run below the harness and replays it offline from the recorded bytes, with no model called. A run can also be forked at any step onto a different model, so the model is the only variable in a comparison.
-
-One npm package named `agenticreplay` puts one command named `agenticreplay` on the PATH. Nothing is installed into the agent, and the agent runs unmodified: `agenticreplay record claude` captures the request and response bytes exchanged with the model through a base-URL proxy, alongside shell, MCP and filesystem capture layers. `agenticreplay replay last` re-runs that session against the recording with no network and no tokens spent. `agenticreplay replay last --from 4 --model <other>` re-runs it from a chosen step on a different model with the conversation prefix held fixed.
-
-Apache-2.0 for the code, CC BY 4.0 for the trace-format spec. Requires Node 24.0.0+. Works with Claude Code, Codex, the OpenAI Agents SDK, the Vercel AI SDK, and agents that read no base-URL variable at all.
-
-## Docs
-
-- [README](https://github.com/askdkc/AgenticReplay/blob/main/README.md): Install, the three commands, the capture-layer diagram, and a per-capability status table.
-- [Architecture](https://github.com/askdkc/AgenticReplay/blob/main/docs/architecture.md): Why a stateless model API means one interception point yields a near-complete execution graph, the five capture layers with their confidence levels and fallbacks, and the two limits the approach cannot escape.
-- [Trace format v0 spec](https://github.com/askdkc/AgenticReplay/blob/main/spec/agenticreplay-trace-v0.md): The on-disk recording format — manifest, events and blobs — licensed CC BY 4.0 so other tools can read and write it.
-- [Integrations](https://github.com/askdkc/AgenticReplay/blob/main/docs/integrations.md): Per-harness notes on what is captured and how each agent is pointed at the proxy.
-- [Plugins](https://github.com/askdkc/AgenticReplay/blob/main/docs/plugins.md): The plugin API and its neutrality guarantees.
-- [Fidelity](https://github.com/askdkc/AgenticReplay/blob/main/docs/fidelity.md): What "byte-for-byte" does and does not cover on replay.
-- [Validation](https://github.com/askdkc/AgenticReplay/blob/main/docs/validation.md): The trace-format conformance check and how to run it against your own traces.
-
-## MCP
-
-- [server.json](https://github.com/askdkc/AgenticReplay/blob/main/server.json): MCP server manifest. `agenticreplay mcp` serves the trace store over stdio as six tools, so an agent can list, read, diff and replay its own past runs.
-
-## Optional
-
-- [Good first issues](https://github.com/askdkc/AgenticReplay/blob/main/docs/good-first-issues.md): Scoped starting points for contributors.
-- [Repository](https://github.com/askdkc/AgenticReplay): Source, issues and releases.

package/packages/adapters/fixtures/harness/claude-code.json

@@ -1,12 +0,0 @@
-{
-  "adapter": "claude-code",
-  "harness_versions": ">=1.0.0",
-  "verified_at": "2026-09-07",
-  "command": "claude",
-  "env_vars": ["ANTHROPIC_BASE_URL"],
-  "base_urls": {
-    "ANTHROPIC_BASE_URL": ""
-  },
-  "optional_env_vars": ["ANTHROPIC_API_KEY", "ANTHROPIC_AUTH_TOKEN"],
-  "note": "Claude Code appends its own /v1 paths, so the origin goes in bare. It carries its own credential store, so ANTHROPIC_API_KEY is passed through when set and never invented: a subscription login has none, and supplying the placeholder stops the launch on an interactive 'detected a custom API key' prompt and then authenticates with a key that is not real. With no key set, Claude Code sends its own authorization header and the proxy relays it. Rechecked with Claude Code 2.1.220 through the built agenticreplay record CLI: API key, ANTHROPIC_AUTH_TOKEN, and CLAUDE_CODE_OAUTH_TOKEN with fake credentials and a local upstream. Model events and streaming replies were captured; OAuth authorization and anthropic-beta were forwarded."
-}

package/packages/adapters/fixtures/harness/codex.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "codex",
-  "harness_versions": null,
-  "verified_at": "2026-08-31",
-  "command": "codex",
-  "env_vars": ["OPENAI_BASE_URL"],
-  "base_urls": { "OPENAI_BASE_URL": "/v1" },
-  "optional_env_vars": ["OPENAI_API_KEY"],
-  "note": "OPENAI_BASE_URL alone does not capture a Codex that has a config.toml: it resolves its origin from model_providers.<name>.base_url, so the adapter also passes -c model_providers.<selected>.base_url=<proxy>/v1, reading the provider name from config.toml (CODEX_HOME honoured). No placeholder key — Codex authenticates from its own auth.json. A Codex signed in with a ChatGPT subscription talks to its own backend, which base-url redirection does not capture."
-}

package/packages/adapters/fixtures/harness/cursor.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "cursor",
-  "harness_versions": null,
-  "verified_at": "2026-09-04",
-  "command": "cursor-agent",
-  "env_vars": [],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Empty by design, and the emptiness is the contract: Cursor's agent stream goes to hosts of its own over HTTP/2 in Connect-over-protobuf with the endpoint compiled in, so there is no origin to move and no credential to pass — the redirect happens underneath, at the socket, when the run is given --tls-intercept. Verified against build 2026.09.02-c22c1a3; harness_versions stays null because Cursor ships date-stamped builds rather than semver, and a range in a vocabulary the harness does not use would say nothing. Two things the operator supplies because this adapter cannot: --tls-hosts '+*.cursor.sh' (a recorded run reached api2.cursor.sh, repo42.cursor.sh and agentn.global.api5.cursor.sh, and the shard numbers vary per account, so it needs the wildcard — which is kept out of DEFAULT_TLS_HOSTS because a wildcard over a vendor's whole domain would decrypt its sign-in origins too), and --trust, which the agent requires to run non-interactively and which is a permission grant no adapter should make on someone's behalf."
-}

package/packages/adapters/fixtures/harness/exec.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "exec",
-  "harness_versions": null,
-  "verified_at": "2026-09-01",
-  "command": "my-agent",
-  "env_vars": [],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Captures at the transport, so it sets nothing at all: no origin and no credential. The empty env_vars list is the assertion — an agent recorded through --tls-intercept must not be silently repointed at a provider it never asked for, and this fixture fails the moment something starts injecting one. The command is the first user arg, so my-agent here is the test's argv rather than a fixed binary."
-}

package/packages/adapters/fixtures/harness/generic-openai.json

@@ -1,14 +0,0 @@
-{
-  "adapter": "generic-openai",
-  "harness_versions": null,
-  "verified_at": "2026-08-29",
-  "command": "my-agent",
-  "env_vars": ["ANTHROPIC_BASE_URL", "OPENAI_API_BASE", "OPENAI_API_KEY", "OPENAI_BASE_URL"],
-  "base_urls": {
-    "OPENAI_BASE_URL": "/v1",
-    "OPENAI_API_BASE": "/v1",
-    "ANTHROPIC_BASE_URL": ""
-  },
-  "optional_env_vars": ["ANTHROPIC_API_KEY"],
-  "note": "The escape hatch: the command is the first user arg, so 'my-agent' here is the test's argv rather than a fixed binary. OPENAI_API_BASE is set alongside OPENAI_BASE_URL for pre-1.0 SDKs and ports."
-}

package/packages/adapters/fixtures/harness/goose.json

@@ -1,14 +0,0 @@
-{
-  "adapter": "goose",
-  "harness_versions": ">=1.49.0",
-  "verified_at": "2026-09-08",
-  "command": "goose",
-  "env_vars": ["ANTHROPIC_HOST", "OPENAI_API_KEY", "OPENAI_BASE_URL", "OPENAI_HOST"],
-  "base_urls": {
-    "OPENAI_HOST": "",
-    "OPENAI_BASE_URL": "/v1",
-    "ANTHROPIC_HOST": ""
-  },
-  "optional_env_vars": ["ANTHROPIC_API_KEY", "GOOSE_MODEL", "GOOSE_PROVIDER", "OPENAI_BASE_PATH"],
-  "note": "Verified against goose 1.49.0 (x86_64-pc-windows-msvc) by pointing it at a sink server and reading the request line back, not by reading its docs. Three things that verification settled, each of which would silently empty a trace if it changed. (1) OPENAI_HOST outranks OPENAI_BASE_URL: openai_def.rs resolves the origin in the order OPENAI_HOST env, OPENAI_BASE_URL, OPENAI_HOST from config, default -- so with only OPENAI_BASE_URL set, a user who already had OPENAI_HOST exported kept it, and the run went to their origin while agenticreplay reported a clean recording over an empty trace. Both are set, at the same proxy, so neither the priority order nor a stale value can route around it. (2) goose does not read ANTHROPIC_BASE_URL or ANTHROPIC_API_BASE at all; its Anthropic provider reads ANTHROPIC_HOST (anthropic_def.rs), and a sink addressed by ANTHROPIC_BASE_URL alone received nothing. This is why generic-openai is not enough for goose -- it sets the variable the rest of the ecosystem reads, which here is the one that does nothing. (3) The traffic is the Responses API: with either variable set goose issues POST /v1/responses plus one GET /v1/models on start-up, and the proxy's openai-responses dialect claims it unchanged. Per-process redirection works at all because Config::get_param reads the environment before the config file (config/base.rs), so a persisted ~/.config/goose/config.yaml cannot win. Not captured: goose runs its shell without going through agenticreplay's PATH shim, so shell tool calls appear with their output but without the real exit code, duration or stdout/stderr split -- record with --no-shell to claim nothing rather than that."
-}

package/packages/adapters/fixtures/harness/grok.json

@@ -1,18 +0,0 @@
-{
-  "adapter": "grok",
-  "harness_versions": null,
-  "verified_at": "2026-08-30",
-  "command": "grok",
-  "env_vars": [
-    "AGENTICREPLAY_INSTRUMENT_HOSTS",
-    "AGENTICREPLAY_PROXY_URL",
-    "BUN_OPTIONS",
-    "GROK_BASE_URL",
-    "NODE_OPTIONS"
-  ],
-  "base_urls": {
-    "GROK_BASE_URL": "/v1"
-  },
-  "optional_env_vars": ["GROK_API_KEY"],
-  "note": "grok-cli documents GROK_BASE_URL (default https://api.x.ai/v1), so the /v1 is part of the value. The fetch hook goes in as well because grok-cli runs on Bun with sub-agents on by default, and api.x.ai is not one of the hook default hosts — hence AGENTICREPLAY_INSTRUMENT_HOSTS. BUN_OPTIONS carries --preload because Bun ignores --require inside NODE_OPTIONS. Its Telegram remote control is the same process reading the same variable. harness_versions is null: the adapter is written from the published README, not pinned to a release."
-}

package/packages/adapters/fixtures/harness/hermes.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "hermes",
-  "harness_versions": ">=0.21.0",
-  "verified_at": "2026-09-07",
-  "command": "hermes",
-  "env_vars": [],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Empty because Hermes has no base-URL variable to move, which was established against a listener rather than assumed: with config model.base_url pointed at a dead port and OPENAI_BASE_URL at a live one, the run dies on the dead port and the listener records nothing -- --provider custom included. The variable is read in exactly one place in the shipped source, an advisory warning that fires when it is set and the provider is not 'custom'. config.yaml's model.base_url is the only origin lever, and agenticreplay does not touch a user's global config. Interception is the route, and Hermes honours HTTPS_PROXY all the way down: through a proxy logging CONNECT targets, one question sends two of them to the model origin, the model-catalogue read and the completion. The trust store needs nothing added, which is worth recording because it looks as though it would. Hermes makes those two calls with two different HTTP libraries -- requests for the catalogue and httpx under the OpenAI SDK for the completion -- and httpx pins certifi. But Hermes resolves that client's CA itself, and the chain in agent/ssl_verify.py reads HERMES_CA_BUNDLE, then SSL_CERT_FILE, then REQUESTS_CA_BUNDLE, then CURL_CA_BUNDLE; agenticreplay already sets the second. Confirmed by removing a vendor-specific variable that had been added for this and recording again: same single model exchange, status 200, 10,615 input tokens. Verified against Hermes Agent v0.21.0 (2026.8.31), installed from git, by running it: `agenticreplay record hermes --tls-intercept --tls-hosts '+opencode.ai' -- --provider opencode-free -m nemotron-3.5-lightning-free -z 'Compute 212000 plus 8 and reply with only the number.'` recorded one model.request/model.response pair -- 48,729 bytes, 19 tools, a 14,058-character system prompt beginning 'You are Hermes Agent, built by Nous Research. Be direct: match the length of your reply to the weight of the ask', answered streamed with status 200 for 1,244 input and 188 output tokens -- plus one abandoned probe as net traffic, and `agenticreplay replay` reused 1/1. Input tokens vary run to run on this tier because the provider caches the prefix; the prompt itself does not. -z is the non-interactive flag; without it Hermes opens a session and waits. inference-api.nousresearch.com is in DEFAULT_TLS_HOSTS so Hermes on Nous' own models needs no extra --tls-hosts; portal.nousresearch.com is deliberately not, being where the API key is issued. The opencode-free tier used above is served anonymously, so no credential was in the recording; its origin needs an explicit +opencode.ai because opencode.ai is a website as much as a gateway. Three measured facts about reading a Hermes recording, from multi-round end-to-end testing on 2026-09-07: (1) Hermes chdirs to the cwd in its session metadata rather than the one agenticreplay launched it in, so filesystem diffs read 0 changed on a run that did write files -- the absolute path is still visible in the write_file tool call, and TERMINAL_CWD is the lever the adapter deliberately leaves to the operator, since forcing it would move where a recorded run writes. (2) How much of a multi-turn run replays depends on the recording. Hermes makes a one-message background call and abandons it; landing after the turns, a three-exchange recording replays reused=3/3 exact=3 divergences=0, and landing between them strict replay stops at reused=1/3 while --loose reaches the same answer. Four recordings of one task gave two of each, and each replays the same way every time -- deterministic per recording, roughly even across them. An earlier revision of this fixture called it 3/3 outright, generalised from replaying a single recording twice. (3) About 6,300 characters of the prompt is an <available_skills> block listing the 51 skills hermes skills list calls builtin, so it is Hermes' own content. A split install hides it -- HERMES_HOME is a persisted user variable, and a shell whose environment predates the install falls back to a home with no skills directory, where the prompt comes out 7,742 characters and the same multi-turn task replays 1/3 instead of 3/3. An earlier revision of this fixture recorded those degraded numbers as the norm; they are what a broken install looks like. Check hermes skills list first."
-}

package/packages/adapters/fixtures/harness/indexrag.json

@@ -1,21 +0,0 @@
-{
-  "adapter": "indexrag",
-  "harness_versions": ">=0.1.0 <0.2",
-  "verified_at": "2026-09-11",
-  "command": "my-agent",
-  "env_vars": ["OPENAI_API_BASE", "OPENAI_API_KEY", "OPENAI_BASE_URL"],
-  "base_urls": {
-    "OPENAI_BASE_URL": "/v1",
-    "OPENAI_API_BASE": "/v1"
-  },
-  "optional_env_vars": [
-    "INDEXRAG_EMBEDDING_API_KEY",
-    "INDEXRAG_EMBEDDING_MODEL",
-    "INDEXRAG_EMBEDDING_PROVIDER",
-    "INDEXRAG_LLM_MODEL"
-  ],
-  "redirected_env_vars": {
-    "INDEXRAG_EMBEDDING_BASE_URL": "/forward/https%3A%2F%2Fembeddings.example%2Fv1"
-  },
-  "note": "A pipeline, not a conversational agent, and the first adapter with two model origins in one run. Chat reads OPENAI_BASE_URL (three openai.OpenAI() call sites) and OPENAI_API_BASE (langchain's default embedding path). The embedding half reads INDEXRAG_EMBEDDING_BASE_URL and may point at a different provider entirely, so it is redirected through /forward/ rather than to a bare /v1 — an upstream map keyed by wire dialect cannot express two origins of the same dialect. No ANTHROPIC_*: every stage speaks OpenAI. 'command' here is the test's argv; a bare `agenticreplay record indexrag -- --data-dir …` launches python against a driver written into ctx.runDir instead."
-}

package/packages/adapters/fixtures/harness/kilo.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "kilo",
-  "harness_versions": ">=7.5.9",
-  "verified_at": "2026-09-04",
-  "command": "kilo",
-  "env_vars": [],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Empty for the reason the whole OpenCode family shares, which Kilo inherits as a fork: the provider origin lives in the harness's own config rather than in an environment variable, so OPENAI_BASE_URL leaves the run talking past the proxy. Interception is the route and api.kilo.ai is in DEFAULT_TLS_HOSTS, so the built-in kilo/* models need no extra --tls-hosts. Verified against kilo 7.5.9 by running it: `agenticreplay record exec --tls-intercept --tls-hosts '+api.kilo.ai' -- kilo run --model kilo/kilo-auto/free` recorded two model.request/model.response pairs, one request carrying 44,973 characters beginning 'You are Kilo, a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.' Kilo checks entitlement locally before opening a connection, so a model the account cannot use fails with 'You need to sign in to use this model' and sends nothing at all -- kilo/kilo-auto/free is reachable without a paid plan, which is what makes this capturable. Kilo also posts to us.i.posthog.com; not a model API, so it stays tunnelled and unread."
-}

package/packages/adapters/fixtures/harness/mcode.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "mcode",
-  "harness_versions": ">=0.4.12",
-  "verified_at": "2026-09-20",
-  "command": "mcode",
-  "env_vars": ["MAVIS_DATA_DIR", "MINIMAX_DATA_DIR"],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Both spellings of the data directory, always, even here where the fixture's empty home leaves nothing to redirect -- and every other MAVIS_*/MINIMAX_* variable in the parent environment emptied, which is why this list does not name them: MCode reads about ninety, among them three more data directories and four credentials, and overriding one spelling at a time is how MAVIS_DATA_DIR survived into the child in the first place. The data directory moves whether or not a config is written into it, because `agenticreplay replay` calls the same `prepare` with the operator's current environment: a fallback that launched MCode untouched ran it on the real ~/.minimax, against the real gateway with the real credential, while the replay saw nothing reach the proxy and reported success. An empty directory of agenticreplay's own stops that -- measured, MCode answers `Sign in to MiniMax to use Agent features` and makes no call. Given a config with a custom provider it can prove it rewrote, the adapter also writes a redirected copy into that directory; that path is checked in test/mcode.test.ts, where the file can be read. MCode keeps its origin in that config and uses Node's fetch, which consults neither HTTP_PROXY nor HTTPS_PROXY, so the base-URL route has no variable to set and --tls-intercept sees nothing at all. Verified against @minimax-ai/code 0.4.12 by running it: `agenticreplay record mcode -- exec --prompt-mode coding --permission off --max-steps 1 'Reply with exactly: ADAPTER-OK'` recorded 14 events and 6 exchanges, and the request carries a 16,162-character system prompt beginning 'You run inside MiniMax Code, a workspace developed by MiniMax'. The gateway answered 401 -- which is the point: every key agenticreplay writes into the generated config is a placeholder, because the file lands inside the run directory and a credential is never written there, and the prompt is captured anyway since it travels in the request. Each custom provider's origin is carried through /forward/ so the call still names the host the operator configured; the run logged upstream=http://155.103.159.98:8317, theirs. Only custom providers can be captured: on that same run MCode rewrote the built-in minimax_api provider's baseURL and apiKey on startup, restoring its own values -- the apiKey as the literal sk-xxx from its bundle, not the operator's, measured against a config whose every key had been replaced by a distinct canary."
-}

package/packages/adapters/fixtures/harness/mimo.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "mimo",
-  "harness_versions": ">=0.1.14",
-  "verified_at": "2026-09-04",
-  "command": "mimo",
-  "env_vars": [],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "Empty for the same reason OpenCode's redirect does not work, which MiMo inherits by being a fork: the provider origin lives in ~/.config/mimocode/mimocode.jsonc, not in an environment variable, so OPENAI_BASE_URL leaves the run talking past the proxy. Interception is the route, and api.xiaomimimo.com is in DEFAULT_TLS_HOSTS so the built-in xiaomi/* and mimo/* models need no extra --tls-hosts. Verified against @mimo-ai/cli 0.1.14 by running it: `agenticreplay record exec --tls-intercept -- mimo run --model xiaomi/mimo-v2.5` recorded a model exchange whose request carries 122,002 characters beginning 'You are MiMoCode, an interactive CLI tool that helps users with software engineering tasks'. The account had no valid key and the server answered 'Invalid API Key' -- which is the point: MiMo sends the request and lets the server reject it, and the prompt is in the request, so no credential is needed to capture it. Being an OpenCode fork does not mean inheriting an OpenCode installation: the two read parallel config directories, so a machine with OpenCode set up still starts MiMo on Xiaomi's provider. A provider of your own on a plain-HTTP gateway is captured by neither route, since agenticreplay sets HTTPS_PROXY and not HTTP_PROXY."
-}

package/packages/adapters/fixtures/harness/node.json

@@ -1,22 +0,0 @@
-{
-  "adapter": "node",
-  "harness_versions": null,
-  "verified_at": "2026-08-30",
-  "command": "my-agent",
-  "env_vars": [
-    "AGENTICREPLAY_PROXY_URL",
-    "ANTHROPIC_BASE_URL",
-    "BUN_OPTIONS",
-    "NODE_OPTIONS",
-    "OPENAI_API_BASE",
-    "OPENAI_API_KEY",
-    "OPENAI_BASE_URL"
-  ],
-  "base_urls": {
-    "OPENAI_BASE_URL": "/v1",
-    "OPENAI_API_BASE": "/v1",
-    "ANTHROPIC_BASE_URL": ""
-  },
-  "optional_env_vars": ["ANTHROPIC_API_KEY", "AGENTICREPLAY_INSTRUMENT_HOSTS"],
-  "note": "Not a harness but a runtime: the command is the first user arg, as with generic-openai. NODE_OPTIONS carries --require of the fetch hook written into ctx.runDir, and BUN_OPTIONS carries --preload of the same file because Bun ignores --require inside NODE_OPTIONS (checked against a real bun); which is the only reason this adapter exists — an agent on the Vercel AI SDK reads none of the base-url variables. They are set anyway because one agent may use an SDK default client for one provider and a hardcoded origin for another. harness_versions is null because the thing being pinned would be Node itself, and the hook uses nothing newer than the CLI's own floor."
-}

package/packages/adapters/fixtures/harness/openclaw.json

@@ -1,21 +0,0 @@
-{
-  "adapter": "openclaw",
-  "harness_versions": null,
-  "verified_at": "2026-08-30",
-  "command": "openclaw",
-  "env_vars": [
-    "AGENTICREPLAY_PROXY_URL",
-    "ANTHROPIC_BASE_URL",
-    "BUN_OPTIONS",
-    "NODE_OPTIONS",
-    "OPENAI_API_BASE",
-    "OPENAI_BASE_URL"
-  ],
-  "base_urls": {
-    "ANTHROPIC_BASE_URL": "",
-    "OPENAI_BASE_URL": "/v1",
-    "OPENAI_API_BASE": "/v1"
-  },
-  "optional_env_vars": ["ANTHROPIC_API_KEY", "OPENAI_API_KEY", "AGENTICREPLAY_INSTRUMENT_HOSTS"],
-  "note": "OpenClaw is a gateway, not a coding agent: it launches Claude Code, Codex or opencode as child processes. The fetch hook catches the gateway own calls, which read no documented base-URL variable; ANTHROPIC_BASE_URL and OPENAI_BASE_URL are set for the agents it spawns, which inherit this environment and do read them. harness_versions is null: written from the published package and README, not pinned to a release."
-}

package/packages/adapters/fixtures/harness/opencode.json

@@ -1,20 +0,0 @@
-{
-  "adapter": "opencode",
-  "harness_versions": null,
-  "verified_at": "2026-09-07",
-  "command": "opencode",
-  "env_vars": [
-    "ANTHROPIC_API_KEY",
-    "ANTHROPIC_BASE_URL",
-    "OPENAI_API_KEY",
-    "OPENAI_BASE_URL",
-    "OPENCODE_CONFIG_CONTENT",
-    "SHELL"
-  ],
-  "base_urls": {
-    "OPENAI_BASE_URL": "/v1",
-    "ANTHROPIC_BASE_URL": "/v1"
-  },
-  "optional_env_vars": [],
-  "note": "Verified with OpenCode 1.18.29 using isolated fake OAuth/API-key credentials and a local upstream stub. ChatGPT OAuth rewrites the URL after OPENAI_BASE_URL is applied; a run-local plugin captures the final fetch to chatgpt.com/backend-api/codex/responses or the public OpenAI model endpoints. OPENCODE_CONFIG_CONTENT retains existing settings and plugins while appending the capture plugin. The first-party provider overlay and SHELL shim routing remain in place. The fixture keys describe the no-auth placeholder branch. See docs/opencode-capture.md for reproduction and transport limits. The Anthropic base includes /v1 because OpenCode appends /messages, unlike Claude Code. Verified through the built agenticreplay record CLI with an Anthropic API-key fixture."
-}

package/packages/adapters/fixtures/harness/qwen.json

@@ -1,20 +0,0 @@
-{
-  "adapter": "qwen",
-  "harness_versions": ">=0.22.3",
-  "verified_at": "2026-09-04",
-  "command": "qwen",
-  "env_vars": ["ANTHROPIC_API_KEY", "ANTHROPIC_BASE_URL", "OPENAI_API_KEY", "OPENAI_BASE_URL"],
-  "base_urls": {
-    "OPENAI_BASE_URL": "/v1",
-    "ANTHROPIC_BASE_URL": ""
-  },
-  "optional_env_vars": [
-    "ANTHROPIC_AUTH_TOKEN",
-    "DASHSCOPE_API_KEY",
-    "GEMINI_API_KEY",
-    "GOOGLE_API_KEY",
-    "OPENAI_MODEL",
-    "QWEN_CODE_MODEL"
-  ],
-  "note": "Two origins of the four Qwen Code reads, and the boundary is about what agenticreplay can put on the other end rather than about the harness. Taken off the installed bundle of @qwen-code/qwen-code 0.22.3: it also reads DASHSCOPE_PROXY_BASE_URL (overriding https://dashscope.aliyuncs.com/compatible-mode/v1, the path Qwen's own models take) and GEMINI_NEXT_GEN_API_BASE_URL (overriding https://generativelanguage.googleapis.com). Both are deliberately left pointing at their real APIs. The proxy resolves a live upstream by wire dialect, not by provider, and resolveUpstream can only name anthropic/openai origins -- so a redirected DashScope call arrives as POST /v1/chat/completions, is claimed by the openai dialect and forwarded to api.openai.com with the user's DashScope key on it, while a Gemini call hits /v1beta/models/... which no dialect claims and passthroughOrigin, which recognises only Anthropic headers, sends to api.openai.com too. Recording Qwen against those providers needs interception rather than redirection: --tls-intercept --tls-hosts '+dashscope.aliyuncs.com'. WEB_SEARCH_BASE_URL is a documented gap for a different reason -- it is the web-search tool's endpoint, keyed separately and off unless ENABLE_WEB_SEARCH is set. The two placeholder keys appear only when the environment carries no key and ~/.qwen/oauth_creds.json is absent, so recording never makes a provider look configured that is not, and never shadows a sign-in the harness made for itself."
-}

package/packages/adapters/fixtures/harness/zcode.json

@@ -1,10 +0,0 @@
-{
-  "adapter": "zcode",
-  "harness_versions": ">=3.14.1",
-  "verified_at": "2026-09-21",
-  "command": "zcode",
-  "env_vars": ["ZCODE_PERSONAL_PROVIDER_CONFIG_FILE"],
-  "base_urls": {},
-  "optional_env_vars": [],
-  "note": "ZCODE_PERSONAL_PROVIDER_CONFIG_FILE names the provider file, and the adapter always sets it -- here too, where the fixture's empty home leaves nothing to carry into it. Replay calls the same prepare with the operator's current environment, so an adapter that redirected nothing there would let a replay run live on their real providers and still report success because nothing reached the proxy. Given a config it can read, the adapter writes a redirected copy instead; that path is checked in test/zcode.test.ts. ZCode's file is JSON, so the rewrite parses a tree and walks every node rather than matching text. An earlier version of this note said that settled the completeness question MiniMax Code's YAML rewrite kept answering wrongly; it does not, and review found the gap. Parsing locates values and says nothing about which are secret: isSecret knew apiKey and api_key and not APIKEY, Authorization or jwt, and isOrigin knew baseUrl and not endpoint, host or url -- so a credential under an unanticipated name was copied into the run directory, and from there into trace/. Fixed the way MiniMax Code arrived at: the rewrite stays an allowlist because it must produce correct output, origins are now recognised by value rather than key name, and a value-shaped net over the result refuses anything it cannot account for. The net's opaque-token alphabet keeps - and _ as MiniMax Code's does, and excludes only /. An earlier version took the separators out, because ZCode's shipped provider.example.json has \"type\": \"zhipu-coding-plan-api-key\" -- 25 characters of exactly those, an enum value -- and removing them was how that file stopped being refused. Review measured the compensating claim and it was false: abc123-abc123-abc123-abc123 has entropy about 2.8 bits per character against a 4.0 threshold and deadbeef-deadbeef-deadbeef has no digit, so the redactor declines both, and with the separators out the shape net never saw them either. Measured in a real recording: three such values under api.headers -- which PROVIDER_CONFIG.md documents as an arbitrary string map, and where a gateway's signed header lives -- landed verbatim in the run directory. The separators are back, and the false positive went through two wrong answers before the right one. Exempting the four field names whose values are identifiers (type, modelId, personalModelIds, modelOrder) left only the redactor between a credential filed under one of those names and the run directory -- the same redactor this note already says misses hex and low-entropy shapes. A name is something a credential can be filed under. So the exemption is now a set of exact values: PROVIDER_CONFIG.md defines six (api-key, zhipu-coding-plan-api-key, zhipu-account for access.type; anthropic-messages, openai-chat-completions, openai-responses for api.type) and only zhipu-coding-plan-api-key reaches 24 characters. A credential cannot be filed as that string; it has to be it. The cost is that model ids are not a closed set, so a config naming one of 24 characters or more (anthropic/claude-3-5-sonnet-20241022 is 26 after the / that ends the run) is refused and the run falls back to agenticreplay's own provider -- measured: ZCode's shipped example, a plain api-key gateway and short model ids all still carry. The launch overlay also blanks ZCode's whole environment namespace before naming the file. Measured: the bundle names 200 ZCODE_* variables and reads them through minified constants (Hee=\"ZCODE_PERSONAL_PROVIDER_CONFIG_FILE\", read as process.env[Hee]), so which are live cannot be established by grep -- among them ZCODE_BASE_URL, ZCODE_ENDPOINT_ORIGIN and three more origins, ZCODE_CREDENTIAL_SECRET and two more credentials, plus ZAI_*, BIGMODEL_*, GLM_* and OPENAI_/ANTHROPIC_ base-url and key pairs the bundle also names. With all of them blanked ZCode still boots and captures in full, measured. Verified against zcode-runtime 0.16.9 (zcode-app-cli 3.14.1-27, a wrapper whose zcode-runtime.lock.json records the official ZCode-3.14.1-linux-x64.deb and its sha512) by running it: `agenticreplay record zcode -- --prompt '...' --mode yolo` recorded a request carrying a 9,084-character system prompt beginning 'You are ZCode, an interactive coding agent' and 27 tools, and `agenticreplay replay` reproduced it offline with reused=1/1, exact=1, divergences=0, unmatched=0, egress=blocked -- the replayed error carrying the recording's own requestId. Four things measured rather than assumed. ZCODE_HOME does NOT relocate ~/.zcode, so the adapter cannot isolate the way MiniMax Code's does. An empty ZCODE_BUILTIN_PROVIDER_CONFIG_FILE makes ZCode refuse to start, so the eight account-backed built-in providers are not redirected and a run on one of them is not captured; the sweep blanks that variable instead, which leaves ZCode reading its own bundled file. A model id agenticreplay invented ends the run at `Model creation failed` before a request exists, which is why the fallback config names glm-4.6 -- and --model is not a flag this harness has at all (`Unknown option '--model'`), so the model is chosen in the config and `capture.mjs zcode` takes none. Finally, the prompt embeds three facts about the directory it runs in rather than the harness -- the git branch, the git status output, and its per-project memory directory name, which is <basename>-<16 hex of the absolute path>. capture.mjs scrubs all three to placeholders, so the artifact no longer depends on where it was captured: measured, the same capture taken inside this repository on a dirty feature branch and in an empty repository on master produce byte-identical files. The as-sent length still differs with the directory, because the branch and status text is part of what was sent: 9,084 characters in an empty repository, and more inside a checkout by however much its branch name and dirty list come to. The capture README's column records the empty-repository figure."
-}

package/packages/adapters/package.json

@@ -1,29 +0,0 @@
-{
-  "name": "@agenticreplay/adapters",
-  "version": "0.5.0",
-  "type": "module",
-  "license": "Apache-2.0",
-  "repository": {
-    "type": "git",
-    "url": "https://github.com/askdkc/AgenticReplay.git",
-    "directory": "packages/adapters"
-  },
-  "main": "./dist/index.js",
-  "types": "./dist/index.d.ts",
-  "exports": {
-    ".": "./dist/index.js"
-  },
-  "files": [
-    "dist"
-  ],
-  "dependencies": {
-    "@agenticreplay/core": "0.5.0",
-    "@agenticreplay/node-instrument": "0.5.0",
-    "@agenticreplay/plugin-api": "0.5.0",
-    "@agenticreplay/proxy": "0.5.0",
-    "@agenticreplay/shell-shim": "0.5.0"
-  },
-  "engines": {
-    "node": ">=24.0.0"
-  }
-}