Skip to content

Opik 2.2.104–2.2.105 adds dataset history viewing and Cohere tracing

Updated Opik

Summary

Opik adds read-only access to older dataset and test-suite versions, a native Cohere SDK integration, and provider-aware usage pricing.

Tool
Opik
Category
Agent infra
Date
Pricing
Not stated in the sources we cited.

2.2.104 was published at 2026-10-19T11:43:29Z. 2.2.105 was published at 2026-10-19T14:30:39Z. This summary follows the maintainers’ release notes.

What changed

  • Version 2.2.104 adds a native Cohere SDK integration.
  • Span pricing now uses provider-native usage formats, with changes covering LiteLLM providers and cache-token usage shapes.
  • Diagnostics gains project guidance and a way to close a finding as not useful. Agent-graph nodes can open their corresponding spans.
  • Version 2.2.105 lets users view an older dataset or test-suite version without restoring it.

Before upgrading

Reported usage costs depend on the actual provider, model and recorded usage. This release is not a guarantee of billing accuracy for every integration. Version 2.2.104 also caps the SDK dependency below LiteLLM 1.106 because of its MCP package requirement.

Explore the opik hub and agent-infra category.

More from Opik

View all

Questions

What is Opik?

According to its docs, Opik is an open-source platform that helps you understand what your LLM application is doing, measure how well it works, and improve it.

Is Opik open source?

Yes. The docs say Opik is open source, and the GitHub API reports the repository license as Apache-2.0.

Does Opik have an MCP server?

The docs say you can install the Opik MCP server to drive your workspace from tools such as Claude Code, Cursor, VS Code Copilot, Codex or opencode.

Filed on Agent Radar. Claims in this note are limited to the sources above.