You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Description
Adds opt-in OpenTelemetry tracing for cloud-agent runs so we can inspect
end-to-end execution when debugging latency and failures.
When `WARP_CLOUD_AGENT_OTLP_ENDPOINT` is configured, the native app
installs an OTLP/HTTP trace exporter; otherwise tracing remains a no-op.
Cloud-agent spans are explicitly marked, and filtering at the exporter
boundary prevents unrelated application spans from being sent. This also
adds spans and events across the cloud-agent lifecycle, server APIs, and
driver setup, and propagates the current span through asynchronous tasks
and streams.
The tracing provider is retained through the standard application
shutdown path, with a best-effort active-span registry that ends
still-reachable spans before shutting down the provider so long-lived
asynchronous work is less likely to be lost.
## Linked Issue
None.
## Testing
- [x] Manually tested locally with `./script/run -- agent run --prompt
"hello world"`.
- [x] Ran `./script/format`.
- [x] Ran `cargo check -p warp --features gui`.
- [x] Ran `cargo doc -p warp --features gui --no-deps`.
No automated tests were added; this is opt-in observability plumbing
that was validated through the cloud-agent command path and focused
compilation/documentation checks.
> [!NOTE]
> note from dstern: i ended up working with an agent to do an end-to-end
test of the fully-authenticated flow with a local cloud agent running
via a self-hosted worker host; everything appears to work.
## Agent Mode
- [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode
CHANGELOG-NONE
Co-Authored-By: Oz <oz-agent@warp.dev>
"Warning: Terminal session is slow to bootstrap. See https://docs.warp.dev/support-and-community/troubleshooting-and-support/known-issues#shells to troubleshoot."
0 commit comments