Custom API endpoint #52

Activity

1. mldangelo-oai

   added

   enhancementNew feature or requestNew feature or request

   on Aug 3, 2026
2. mldangelo-oai commented on Aug 3, 2026

   

   mldangelo-oai

   on Aug 3, 2026

   Collaborator

   More actions

   Maintainer cross-reference for the two provider approaches: #125 proposes a relatively small generic OpenAI-compatible endpoint, while #139 implements Azure-specific provider support and credential isolation across a much larger change. Both currently conflict with main, and neither should be selected until HTTPS requirements, credential isolation, supported providers, and cost semantics are defined consistently. Prefer the smallest implementation that satisfies that shared policy; Azure support and a generic custom endpoint are related, not automatically equivalent.
3. mldangelo-oai

   added

   area:authLogin, credentials, account access, and authentication recovery.Login, credentials, account access, and authentication recovery.

   area:cliCommand-line help, arguments, terminal UI, and user interaction.Command-line help, arguments, terminal UI, and user interaction.

   priority:p2Significant defect or product gap with narrower impact or a workaroundSignificant defect or product gap with narrower impact or a workaround

   on Aug 15, 2026
4. mldangelo-oai

   marked Feature request: Support custom OpenAI-compatible providers (e.g. Z.AI GLM) #417 as a duplicate of this issue on Aug 15, 2026
5. tan-yong-sheng commented on Sep 21, 2026

   

   tan-yong-sheng

   on Sep 21, 2026

   More actions

   Hope that would be supported in future, currently using Bex Security as a temporary alternative to OpenAI Codex Security. It keeps the same workflow for finding, validating, and fixing security vulnerabilities, while moving toward an open agent system based on ACP (Agent Client Protocol): https://github.com/bex-co/bex-security
6. mldangelo-oai commented on Oct 8, 2026

   

   mldangelo-oai

   on Oct 8, 2026

   Collaborator

   More actions

   This may now be covered through native Codex provider settings. Merged #1281 preserves per-scan provider configuration, and #1326 carries endpoint overrides into fresh and resumed Deep workers. Could you check whether that works for your Responses-compatible endpoint?
7. mldangelo-oai

   added

   area:configProject configuration, profiles, schemas, and effective scan settings.Project configuration, profiles, schemas, and effective scan settings.

   area:providersModel providers, custom endpoints, model selection, and provider-specific settings.Model providers, custom endpoints, model selection, and provider-specific settings.

   and removed

   area:authLogin, credentials, account access, and authentication recovery.Login, credentials, account access, and authentication recovery.

   area:cliCommand-line help, arguments, terminal UI, and user interaction.Command-line help, arguments, terminal UI, and user interaction.

   on Oct 8, 2026