## Problem Currently we are passing organization_id to AI gateway in the headers, but we are still missing the organization_id in the duo workflow service. ## Desired Outcome We are able to retrieve organization_id from Duo workflow service. <!--The desired state of the affected system after this issue has been completed--> ## Potential Solution These areas are identified places where we still need to add organization_id: **Missing — Duo Workflow / Agentic Chat:**\  - ee/lib/api/ai/duo_workflows/workflows.rb:528 — cloud_connector_headers (websocket /ws endpoint) \  - ee/lib/api/ai/duo_workflows/workflows.rb:445 — Client.headers (direct access endpoint) \  - ee/lib/api/helpers/duo_workflow_helpers.rb:11 — push_ai_gateway_headers \ \  **Missing — Code Suggestions:**\  - ee/lib/api/code_suggestions.rb:53 — ai_gateway_headers \  - ee/lib/api/code_suggestions.rb:67 — ai_gateway_public_headers \  - ee/lib/api/code_suggestions.rb:348 — public_headers \  - ee/lib/gitlab/llm/ai_gateway/code_suggestions_client.rb:114 — ai_gateway_headers \ \  **Missing — Chat / LLM Clients:**\  - ee/lib/gitlab/llm/ai_gateway/client.rb:108 — perform_completion_request \  - ee/lib/gitlab/llm/ai_gateway/docs_client.rb:37 — perform_search_request \  - ee/lib/gitlab/duo/chat/step_executor.rb:84 — perform_agent_request \ \  **Missing — Other AI Proxies:**\  - ee/lib/gitlab/llm/anthropic/client.rb:164 — request_headers \  - ee/lib/gitlab/llm/vertex_ai/configuration.rb:38 — headers \  - ee/lib/gitlab/llm/q_ai/client.rb:107 — request_headers \  - ee/lib/gitlab/llm/embeddings/client.rb:50 — headers \  - ee/lib/api/internal/ai/x_ray/scan.rb:31 — model_gateway_headers \  - ee/app/services/ai/model_selection/fetch_model_definitions_service.rb:58 — call_endpoint Note: these areas were identified with AI and need to be verified. <!--An outline of potential solutions to get to the desired outcome. These solution(s) can still be adjusted throughout the implementation as long as the desired outcome is achieved.--> ### Documentation Update Needed <!--Does this change require the documentation to be updated? check the appropriate option--> - [ ] Yes - [ ] No ## How to verify <!--How can we verify that the desired outcome has been achieved? The instructions from this section should be used to move the issue from ~“worfklow::verification”.--> ## Further actions needed <!--Any further tasks that need to be completed after the main work of the issue is done, such as announcing the changes.--> <!--This section is optional.--> <!--Make sure to add one of the type labels (as per https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification):--> <!--/label ~"type::bug" ~"type::feature" ~"type::tooling" ~"type::maintenance"-->