Repository navigation
Conversation
- Emits nested run, turn, request, and tool facts from their low-level owners - Preserves disabled-telemetry behavior through the shared no-op context
- Propagates telemetry and exact harness snapshots across sessions and child agents - Records operations, retries, hooks, summaries, terminal work, artifacts, and subagent lifecycle facts - Covers successful, failed, retried, compacted, aborted, and child-agent runs in memory
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds optional in-memory telemetry across active agent and coding-agent execution, including provider requests, tools, retries, extension hooks, terminals, artifacts, and subagents.
Keeps telemetry disabled by default through the shared no-op context and does not add trace-file persistence or codecs.
Reasoning
Facts are emitted by the lowest-level runtime owner so ordering and outcomes reflect actual execution.
Stable invocation, request, operation, and child-agent identifiers plus explicit parent contexts preserve hierarchy without global mutable trace state.
Subagents inherit the exact activated harness snapshot from their parent.
Changes
Testing
npm run checknode ../../node_modules/vitest/dist/cli.js --run test/agent.test.ts test/harness/telemetry.test.tsfrompackages/agentnode ../../node_modules/vitest/dist/cli.js --run test/suite/runtime-telemetry.test.ts test/extensions-runner.test.ts test/subagent-controller.test.ts test/suite/subagent-services.test.ts test/suite/agent-session-retry-events.test.ts test/suite/agent-session-compaction.test.ts test/suite/regressions/6647-compaction-retries-transient-stream-drop.test.tsfrompackages/coding-agentnode ../../node_modules/vitest/dist/cli.js --run test/suite/agent-session-runtime.test.tsfrompackages/coding-agent