Docs target current release v0.5.0.v0.6.0 is in development

tine import

tine import materializes a foreign trace as an ordinary opentine run. It uses the same importers as the Python API and writes a portable v2.tine artifact, advances a ref in an existing v3 repository, or does both in one invocation.

Terminal
# Complete OTLP/JSON document -> portable v2 artifact
tine import trace.otlp.json --format otel-json --save run.tine

# GenAI spans from stdin -> existing v3 repository
tine import - --format otel-spans --repo . --ref heads/imported

# A serialized framework log -> both destinations
tine import agent.log --format langchain --save run.tine --repo .

# Replace only the --save destination
tine import trace.jsonl --format jsonl --save run.tine --force

Accepted formats

  • otel-json: a complete OTLP/JSON document, a{"spans": [...]} wrapper, or one OpenTelemetry span object.
  • otel-spans: a JSON array of OpenTelemetry GenAI spans or one span object per line.
  • jsonl: OpenTine TraceEvent objects, one per line.
  • langchain, llamaindex, autogen,crewai, and openai-agents: serialized framework records as a JSON array or JSONL.

Framework formats are best-effort because upstream log shapes can change. CrewAI is a post-hoc import path in v0.5; opentine does not provide a live CrewAI adapter.

Destination rules

  • Pass at least one of --save PATH or --repo PATH.
  • --save writes a portable v2 artifact and refuses an existing file unless --force is present.
  • --repo opens an existing v3 repository. Initialize it first withtine init.
  • --ref applies only with --repo and defaults toheads/main.
  • Use - as the source to read from standard input.

Provenance boundary

Import does not capture the importing machine's code or environment. Those details belong to the system that produced the trace, not the machine converting it. Imported content remains untrusted input and may include prompts, outputs, or tool results that require review before sharing.

The command prints the resulting run ID in the normal human rendering. It does not accept --json. For a machine-readable result after import, use one of the documented read commands such as tine show run.tine --json.

See OpenTelemetry interoperability for supported message shapes and export behavior, or live LangChain and LangGraph capture.