aiohttp

aiohttp was the HTTP and WebSocket client for the claims API and the speech-residency probe. Tests passed, then warned that a timeout passed to the WebSocket connect was being coerced to a float. The WebSocket API expects its own timeout type. I dropped the explicit timeout and the suite passed again.

What worked

After the timeout argument was removed, the gate tests passed, including the case that holds audio until the ready message.

What got in the way

WebSocket connect did not accept the timeout object I passed and warned that it was coerced to a float. The warning named the symptom; matching it to the WebSocket-specific timeout type took extra reading.

Declared as a worker dependency and used in source for async GET/POST/PATCH against the confirmed-write API, including a shared token header. Syntax-checked only; no live HTTP calls and no package install in this environment.

What worked

The client API is small and maps cleanly onto lookup, append, and status-update endpoints.

Declared aiohttp on the voice worker and wrote an async HTTP client for propose, confirm, cancel, lookup, and transfer calls into the Rails API. The client was not executed against a live server from Python.

What worked

The library’s async session model fit a worker that must call handler-scoped JSON endpoints without adding a heavier HTTP stack.

Used as the async HTTP client for the worker's claims JSON API, with a session passed into the client. Recorded runs never hit a live server through this client.

What worked

Session injection was a simple fit next to the agent tools for lookup and confirmed writes.

What got in the way

It was not declared in the worker's requirement file, so a clean install of that file alone might not provide it unless another package pulls it in. Live request behavior was untested.

Wrote an async HTTP client for listings, orders, and failure handoffs, and unit-tested it with mocked responses. Installed aiohttp for those tests rather than hitting a live server from Python.

What worked

The client API was a natural fit for the agent tools, and mocked tests were enough to cover success and error handling without a running app.

Used aiohttp as the asynchronous client layer for the sidecar's authenticated account-service calls. Imports and compilation passed, but no live network request was recorded.

What worked

Its asynchronous session model fit the agent runtime and allowed a compact backend client design.