Repository navigation
feat(integrations): every integration identifies itself with its own User-Agent - #5466
Merged
Merged
Conversation
…y integration that calls the API
…d of replacing it
…t version Review finding: the public reqwest builder that the docs point integrations at still replaced the client token, so only client_with_user_agent kept it.
This was referenced Oct 12, 2026
This was referenced Oct 20, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Every integration that calls the Hindsight API now sends its own
User-Agent,hindsight-<name>/<version>. Before, these sent the client default (hindsight-client-python/x,hindsight-client-typescript/x) or the stdlib default (Python-urllib/x,node), so the server couldn't tell which integration a request came from. About 25 integrations already did this. This PR covers the rest.Client change: keep the client version
Before this PR, a caller's User-Agent replaced the client's own, so every integration that set one hid which client version it ran on. The Python and TypeScript wrappers, and Rust's
client_with_user_agent, now put the caller's value in front of their own:Integrations need no change for this, and they work with both old and new clients. On an old client they send
hindsight-ag2/1.2.0; on a new client they send both names. Nothing in the repo checks the exact header a real client sends, since integration tests check what the integration passes in. Go is unchanged: it has no wrapper option for this, only the rawcfg.UserAgent.Covered
Python: agentcore, composio, dify (client + credential health check), hermes (client +
/versionprobe), pipecat, smolagents, vapi, cursor (hook client + daemon health check), devin-desktop, meta-muse (preflight CLI session)TypeScript / JS: coding-agents (shared client + daemon health check), flowise, opencode, paperclip, eve, obsidian, n8n (credential-level header), zapier (middleware)
If a user passes their own client, we don't touch it, so their User-Agent is kept.
Version source, per integration
importlib.metadata/package.json, falling back to0.0.0(the same as ag2 and openclaw).plugin.yaml,manifest.yaml,.cursor-plugin/plugin.json).package.jsonbeside it.package.json.hindsight-zapier/<v> Zapier. The trailingZapierstays, because the platform uses it to spot its own requests and would otherwise log every request twice.Left out on purpose
Tests
Each integration got or extended one test that checks the header is sent, and each integration's suite passes locally.
./scripts/hooks/lint.shis clean.