Skip to content

Conversation

@saurabhjain1592
Copy link
Member

@saurabhjain1592 saurabhjain1592 commented Jan 25, 2026

Summary

The proxyLLMCall method was not auto-populating clientId from config when not explicitly set in ClientRequest, unlike other SDKs:

SDK Auto-injects clientId Location
Go axonflow.go:562
Python client.py:706
TypeScript client.ts:612
Java MISSING -

This caused "client_id field is required" errors when using proxyLLMCall without explicitly setting clientId in the request, even though clientId was configured in AxonFlowConfig.

Fix

Apply the same pattern used in getPolicyApprovedContext: auto-populate clientId from config if not set in the request.

Tests Added

  • proxyLLMCallShouldAutoInjectClientId: verifies auto-injection works
  • proxyLLMCallShouldPreserveExplicitClientId: verifies explicit clientId is not overwritten

Test Plan

  • Unit tests pass (86 tests, 0 failures)
  • Compliance examples (eu-ai-act, rbi-sebi) pass with SDK fix
  • Examples work WITHOUT explicit .clientId() in ClientRequest.builder()

@saurabhjain1592 saurabhjain1592 force-pushed the fix/proxy-llm-call-client-id branch from a6003a2 to aac8a2e Compare January 25, 2026 20:31
…eScript SDKs

Auto-populate clientId from config when not explicitly set in ClientRequest.
Previously caused "client_id field is required" errors.

Added to v2.7.1 changelog entry.
@saurabhjain1592 saurabhjain1592 force-pushed the fix/proxy-llm-call-client-id branch from aac8a2e to dec46d9 Compare January 25, 2026 20:32
@saurabhjain1592 saurabhjain1592 merged commit 2f398d0 into main Jan 25, 2026
9 checks passed
@saurabhjain1592 saurabhjain1592 deleted the fix/proxy-llm-call-client-id branch January 27, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants