Documentation Index
Fetch the complete documentation index at: https://docs.honeyhive.ai/llms.txt
Use this file to discover all available pages before exploring further.
honeyhive-bundled was a temporary distribution of the Python SDK with pre-release packaging. The stable v1 SDK is published as honeyhive.
Most imports stay the same because both packages expose the honeyhive Python module. The migration is mainly a dependency change plus cleanup of pre-release patterns.
Recent
honeyhive-bundled releases and honeyhive v1 share the same top-level import style: from honeyhive import HoneyHiveTracer, trace, evaluate.Use a coding agent to migrate
Use a coding agent to migrate
What changes
| Area | honeyhive-bundled | honeyhive>=1.0.0 |
|---|---|---|
| Package name | honeyhive-bundled | honeyhive |
| Release channel | Pre-release / bundled distribution | Stable package |
| Default API URL | https://api.honeyhive.ai | https://api.dp1.us.honeyhive.ai |
| Project routing | Older examples may pass project= | project= still accepted but emits a DeprecationWarning and will be removed in v2 |
honeyhive.config | Alias for the TracerConfig class (callable) | Submodule containing TracerConfig, SessionConfig, EvaluationConfig, etc. |
clear_baggage_context | Exported from honeyhive | Removed from the public API |
honeyhive CLI command | Registered as a console script | No console script registered |
| OpenTelemetry minimum | >=1.20.0 | >=1.41.0 |
1. Replace the dependency
honeyhive:
honeyhive>=1.0.0 keeps every OpenInference and Traceloop extra that honeyhive-bundled shipped and adds new ones: LangChain, LiteLLM, OpenAI Agents, Claude Agent SDK, AWS Strands, and the openinference-llm-providers / traceloop-llm-providers multi-provider bundles. Run pip check after upgrading if your environment pins OpenTelemetry packages, because honeyhive v1 requires OpenTelemetry >=1.41.0.
The Google AI extra is renamed under the hood: bundled installed
openinference-instrumentation-google-generativeai, but honeyhive[openinference-google-ai]>=1.0.0 installs openinference-instrumentation-google-genai instead. If you import the instrumentor directly, update the import path.honeyhive-bundled reports its internal honeyhive.__version__ as 1.0.0rc9.post2 even at PyPI version 1.1.1. After migrating, honeyhive.__version__ will report the published v1 version (for example 1.0.2).2. Update imports
A few symbols thathoneyhive-bundled exported are no longer part of the public API in v1. Update or remove these imports:
Import in honeyhive-bundled | Status in honeyhive>=1.0.0 | What to do |
|---|---|---|
from honeyhive import clear_baggage_context | Removed | Delete the call. Baggage is managed automatically by HoneyHiveTracer during init and session creation. |
honeyhive.config(...) (config alias for TracerConfig) | honeyhive.config is now a submodule, not a class | Import the class explicitly: from honeyhive.config import TracerConfig. |
honeyhive.__version_bundled__ | Removed | Read honeyhive.__version__ instead. |
The
honeyhive console-script that honeyhive-bundled registered is not published by honeyhive>=1.0.0, and the underlying honeyhive.cli module is deprecated. Replace those calls with the official HoneyHive CLI (@honeyhive/cli), which is a separate package that maps one-to-one to the HoneyHive REST API.3. Initialize instrumentors separately
HoneyHiveTracer.init() does not consume an instrumentors= argument in either honeyhive-bundled or honeyhive>=1.0.0. Bundled accepted it silently via **kwargs and never called instrumentor.instrument(), so spans were never produced from that list. Initialize provider instrumentors yourself after HoneyHiveTracer.init() and pass tracer.provider so they emit spans into the HoneyHive tracer.
evaluate() is different: it still accepts an instrumentors= keyword and uses the factories per datapoint. See section 6.4. Remove project routing from new code
v1 acceptsproject= for compatibility but emits a DeprecationWarning and will remove it in v2. Project context is inferred from the API key. honeyhive-bundled accepted project= silently, so after migrating, expect a warning on every initialization until you drop the argument.
project= after confirming your API keys are scoped to the intended project.
5. Prefer tracer instance methods for enrichment
Free helpers such asenrich_span() and enrich_session() are still exported and still work in v1, but tracer instance methods are the primary pattern because they are explicit and behave correctly when multiple tracers are in play.
6. Check evaluate() usage
The stable v1 experiment API expects datasets with ground_truth and functions that receive the full datapoint.
7. Validate the migration
Run:pip show honeyhive-bundledno longer finds an installed packagepip show honeyhiveshows version1.0.0or later- No
from honeyhive import clear_baggage_contextimports remain - Any
honeyhive.config(...)callers usefrom honeyhive.config import TracerConfig - No
HoneyHiveTracer.init(..., instrumentors=...)calls remain HH_API_URLis set if you rely on a non-default host- Traces appear in the expected project
- Provider spans appear after instrumentor initialization
- Experiments show
ground_truthand evaluator scores
Migration checklist
- Remove
honeyhive-bundledfrom dependency files - Add
honeyhive>=1.0.0with matching or newer integration extras - Confirm the default API host change is safe, or set
HH_API_URL - Remove
from honeyhive import clear_baggage_context - Replace
honeyhive.config(...)calls withfrom honeyhive.config import TracerConfig - Replace
honeyhiveconsole-script usage in CI or scripts with the official HoneyHive CLI (@honeyhive/cli) - Initialize instrumentors after
HoneyHiveTracer.init() - Remove
project=from new initialization code after confirming project-scoped API keys - Prefer
tracer.enrich_span()andtracer.enrich_session() - Confirm
evaluate()usesground_truthand datapoint-based functions - Run
pip checkand your app’s smoke tests
Related
Migrate to SDK v1
Upgrade older SDK code to stable v1 semantics.
Migrate from Logger to v1
Replace
honeyhive-logger calls with SDK v1 tracing.SDK Overview
Choose the right SDK and integration path.
Integrations
Install and initialize provider instrumentors.
Environment Variables
Configure SDK runtime behavior.

