Expand description
Structured execution telemetry events shared across VT Code crates.
This crate exposes the serialized schema for thread lifecycle updates,
command execution results, and other timeline artifacts emitted by the
automation runtime. Downstream applications can deserialize these
structures to drive dashboards, logging, or auditing pipelines without
depending on the full vtcode-core crate.
§Agent Trace Support
This crate implements the Agent Trace specification
for tracking AI-generated code attribution. See the trace module for details.
Re-exports§
pub use diagnostic::Diagnostic;pub use diagnostic::DiagnosticAction;pub use diagnostic::DiagnosticSeverity;pub use items::AgentMessageItem;pub use items::AppPreviewItem;pub use items::AppUiPosture;pub use items::CommandExecutionItem;pub use items::CommandExecutionStatus;pub use items::DecisionItem;pub use items::FileChangeItem;pub use items::FileUpdateChange;pub use items::McpToolCallItem;pub use items::McpToolCallStatus;pub use items::PatchApplyStatus;pub use items::PatchChangeKind;pub use items::PlanItem;pub use items::ReasoningItem;pub use items::ThreadItem;pub use items::ThreadItemDetails;pub use items::ToolCallStatus;pub use items::ToolInvocationItem;pub use items::ToolOutcome;pub use items::ToolOutputItem;pub use items::WebSearchItem;pub use items::tool_outcome_from_status;
Modules§
- atif
- Agent Trajectory Interchange Format (ATIF) types and builder.
- diagnostic
- Operational diagnostics shared by runtime events, agents, and human surfaces.
- items
- Timeline item payloads carried by thread item events.
- matrix
- Canonical durable contracts for local matrix execution.
- planning
- Persisted planning recovery state. Answers to recovery prompts never grant approval.
- schema
- trace
- Agent Trace specification types for AI code attribution.
Structs§
- AppSandbox
Denied Event - Context
Reset Event - Error
Item - Execution
Context - Optional recorded execution ancestry. Absent fields are historical gaps.
- Harness
Event Item - Interjected
Event - Item
Completed Event - Item
Context - Item identity, timing, and command semantics for explanation consumers.
- Item
Started Event - Item
Updated Event - LogEmitter
- Emits JSON serialized events to the
logfacade at the configured level. - Otel
Emitter - Emits
ThreadEvents as OpenTelemetry spans and span events. - Permission
Requested Event - Permission
Resolved Event - Plan
Approval Requested Event - Plan
Approval Resolved Event - Plan
Delta Event - Thread
Compact Boundary Event - Thread
Completed Event - Thread
Error Event - Thread
Started Event - Token
Breakdown - Per-request token-budget breakdown for the assembled first-request prefix.
- Tracing
Emitter - Emits structured events as
tracingevents at the specified level. - Turn
Blocked Event - Turn
Completed Event - Turn
Failed Event - Turn
Started Event - Usage
- Versioned
Thread Event - Wraps a
ThreadEventwith schema metadata so downstream consumers can negotiate compatibility before processing an event stream.
Enums§
- Command
Activity - Recorded shell classification, supplied by the runtime’s shared classifier.
- Compaction
Mode - Compaction
Trigger - Context
Reset Trigger - Harness
Event Kind - Input
Origin - Origin of a turn’s input; internal turns retain their parent task.
- Interjection
Source - Permission
Decision - Plan
Approval Decision - Redirect
Kind - Thread
Completion Subtype - Thread
Event - Structured events emitted during autonomous execution.
Constants§
- EVENT_
SCHEMA_ VERSION - Semantic version of the serialized event schema exported by this crate.
- MAX_
IN_ PROGRESS_ EXEC_ SESSIONS - Bound on exec session ids recorded in one turn’s
turn.completedevent. MirrorsSnapshotTurnDiagnostics::in_progress_exec_sessions(cap 4, newest first) soThreadEventand checkpoint diagnostics cannot drift.
Traits§
- Event
Emitter - Sink for processing
ThreadEventinstances.
Functions§
- deserialize_
null_ as_ default - Serde helper that accepts explicit
nullasT::default()for backward-compatible checkpoint/diagnostics payloads. Pair with#[serde(default, deserialize_with = "deserialize_null_as_default")]so both missing andnullfields degrade to the default instead of failing deserialization. Reused by downstream crates (e.g.vtcode-coresnapshots) so the null-tolerance rule cannot drift between copies.