Repository navigation
Conversation
Signed-off-by: Peter Jausovec <peter.jausovec@solo.io>
| valid_until_unix: u64, | ||
| /// The credential's own expiry (the controller JWT `exp`), on both clocks: | ||
| /// a tunnel opened with the credential runs until then, not until the | ||
| /// cache stops reusing it. |
There was a problem hiding this comment.
nothing we removed here, but moved into separate files under "llm_proxy" folder
| Complete organization sign-in in the browser. The local Dex account is | ||
| `admin@example.com` with password `password`. Codex must also be signed in to | ||
| ChatGPT using its normal `codex login` flow. Run Codex in another terminal after | ||
| the daemon applies the configuration. |
There was a problem hiding this comment.
Why do we do it this way rather than the way claude works? where the user logs into claude/codex via the agentdesktop oauth flow
There was a problem hiding this comment.
yep, I can do it that way; this was simpler
| transformations: | ||
| request: | ||
| set: | ||
| authorization: '"Bearer " + request.headers["x-llm-token"]' |
There was a problem hiding this comment.
use policies.backendAuth.key.expression request.headers["x-llm-token"].
Using generic transformation is not ideal since it runs too early + doesn't do proper redaction
There was a problem hiding this comment.
hmm although then it may not remove x-llm-token 🤔
| gateway: | ||
| port: 4002 | ||
|
|
||
| routes: |
There was a problem hiding this comment.
This is not really a great example since everyone running an agw for LLM is going to be using the llm config not routes. This won't give any LLM features at all actually
Signed-off-by: Peter Jausovec <peter.jausovec@solo.io>
Signed-off-by: Peter Jausovec <peter.jausovec@solo.io>
This branch has not been deployed
2 participants
Adds
programs.codex.auth: subscriptionso Codex can retain its ChatGPTlogin while authenticating separately to the organization’s gateway.
Agentdesktop generates the Codex provider and pairing header automatically.
The local proxy forwards the ChatGPT token separately from gateway identity; the gateway validates identity before restoring the provider credential.
llmGateway.proxyUrl.