Skip to main content
Trace capture records finalized coding-agent sessions locally and exports them as OpenTelemetry traces through the background daemon. The trace namespace delegates to the runtime command parser. Run the exact operation shown below; nested operations do not expose separate Cobra flag tables.

​
Commands

​
integration

Lists, checks, installs, or removes supported coding-agent integrations. Usage
<sources...> accepts supported coding-agent sources such as claude and codex. install adds only Atlan-managed hook entries; uninstall removes only those owned entries. doctor verifies the installed integration state.

​
session

Lists locally captured sessions for a selected time window. Usage
The optional window defaults to the runtime’s standard recent range.

​
import

Starts or manages a local session import. Usage
start can import discovered sessions from a source or selected session IDs. The returned import ID is used by status, cancel, and retry.

​
reconcile

Forces the daemon to rescan local content and redrive pending work. Usage
The rescan redrives skill upload, repository onboarding, and session backfill immediately.

​
config

Shows or changes local trace-content capture policy. Usage
The content setting controls whether supported message content is retained in captured trace data. Review the resolved policy before enabling it.

​
data

Shows local trace-storage state or removes reclaimable payload data. Usage
status reports the local journal and outbox. Treat purge as destructive.

​
outbox

Shows delivery state or moves compatible dead-letter items back into delivery. Usage

​
runtime

Shows runtime state or activates the previously retained runtime version. Usage
status also reports the last auto-update result. rollback does not delete the journal.

​
support

Writes an installation diagnostics bundle. Usage
The default path is chosen by the runtime when [path] is omitted.

​
Examples

​
Output and behavior

  • Trace commands operate on the local runtime, journal, integrations, and delivery state. Commands that export or retry work can contact the Gateway.
  • The active Registry context does not set trace attribution; capture resolves its own workspace and identity.
  • Integration changes preserve unrelated coding-agent configuration.
  • Purge changes local data, rollback changes the active runtime, and DLQ requeue changes delivery state. Inspect status first.
  • Review support bundles before sharing them outside your organization.