Install & Compatibility
Where this runs
tested against v0.1.5 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
py 3.9
✕ build_error
✕ build_error
28MB installed
● package 28MB
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
CUA_CLIENT_VERSION_HEADER
✓ from cua_core import CUA_CLIENT_VERSION_HEADER
✗ from cua_core.utils import get_library_version
cua_version_headers
✓ from cua_core import cua_version_headers
http
✓ from cua_core import http
Demonstrates a basic interaction with `cua-core` by retrieving its version, highlighting its utility-centric nature. It also provides a commented example for `TelemetryClient` with a reminder about its dependency role and GCP requirements.
from cua_core.utils import get_library_version
# Retrieve the version of the cua-core library itself.
# This function provides a simple, direct interaction with the library's utilities.
library_version = get_library_version()
print(f"Cua Core Library Version: {library_version}")
# Further utilities exist in cua_core.utils and cua_core.telemetry,
# but their direct usage is generally discouraged as cua-core is primarily a dependency.
# For example, to instantiate a TelemetryClient:
# from cua_core.telemetry import TelemetryClient
# tele_client = TelemetryClient(project_id=os.environ.get('GCP_PROJECT_ID', 'your-gcp-project-id'), service_name="my-app")
# However, this requires a valid GCP project ID and is usually handled by higher-level Cua libraries.
Debug
Known issues
breakingAs a `0.x.x` version library, `cua-core` may introduce breaking changes without prior deprecation warnings between minor or patch releases. Its API is not considered stable for external use.fixIf directly depending on `cua-core`, pin exact versions for stability (e.g., `cua-core==0.1.19`). Prefer relying on higher-level Cua libraries for stable interfaces, as they manage `cua-core` internally.
affects: All 0.x.x versions
gotcha`cua-core` is intended as an internal dependency for the Cua ecosystem and is explicitly "not intended for direct use" by end-user applications. Its public API may not be fully documented or user-friendly, and its design prioritizes internal consistency over external usability.fixPrefer using higher-level Cua libraries that encapsulate `cua-core`'s functionality and provide a stable, user-facing API. Only use `cua-core` directly if building another library within the Cua ecosystem or if fully understanding its internal mechanics.
affects: All versions
gotchaMany core functionalities, especially telemetry and logging, are tightly integrated with Google Cloud Platform (GCP) services (e.g., Google Cloud Logging, Monitoring, OpenTelemetry Exporter for GCP). Direct use of these features requires a properly configured GCP environment.fixEnsure your environment has appropriate GCP credentials (e.g., `GOOGLE_APPLICATION_CREDENTIALS` environment variable pointing to a service account key file) and necessary IAM permissions for Google Cloud Logging and Monitoring.
affects: All versions
Upgrade
Version history
0.3.1latest on PyPI · released Apr 15, 2026
Audit
Dependencies
pydantic-settingsrequiredConfiguration management for loading settings from various sources.
google-cloud-loggingrequiredIntegration with Google Cloud Logging services for structured logs.
google-cloud-monitoringrequiredIntegration with Google Cloud Monitoring for metrics and monitoring.
opentelemetry-sdkrequiredCore OpenTelemetry SDK for distributed tracing and metrics.
opentelemetry-exporter-google-cloudrequiredOpenTelemetry exporter for sending telemetry data to Google Cloud.
opentelemetry-instrumentation-loggingrequiredOpenTelemetry instrumentation for Python's logging module.
opentelemetry-instrumentation-requestsrequiredOpenTelemetry instrumentation for the 'requests' HTTP library.
opentelemetry-apirequiredOpenTelemetry API for creating and managing traces and metrics.
opentelemetry-semantic-conventionsrequiredOpenTelemetry semantic conventions for standardized attribute names.
opentelemetry-instrumentation-asynciorequiredOpenTelemetry instrumentation for asyncio applications.
requestsrequiredHTTP client library, instrumented by OpenTelemetry.
httpxrequiredAsynchronous HTTP client library, likely used internally.