error-transport-context

To preserve error context across MCP and CLI, propagate originating command and session metadata into error envelopes. This ensures consistent diagnostics by attaching consistent fields like command and sessionId to all failures crossing these boundaries.

Context propagation for error diagnostics is the process of maintaining service request metadata, such as sessionId and command, across transport layers. It enables unified troubleshooting by mirroring shared fields in error output objects without altering core behavior.

You can add error logging metadata without breaking Core or COM behavior by applying lightweight, additive changes to transport and error objects. Mirror new shared fields in base output structures to maintain backward compatibility while capturing diagnostic context.

No, adding session metadata to error envelopes does not require modifying core commands. The approach ensures transport diagnostics are not introduced into core commands, relying solely on additive changes to error and transport objects for backward compatibility.

CLI error responses miss originating command information when error context propagation is not enabled across transport boundaries. Mirroring shared fields like command and sessionId in CLI error output objects ensures this metadata is consistently attached to failures.