add gateway cli option for bt - #326
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2547d30279
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
|
Latest downloadable build artifacts for this PR commit
Available artifact names
|
|
Codex (@codex) review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2862a83add
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
| .entry("env".to_string()) | ||
| .or_insert_with(|| TomlValue::Table(toml::map::Map::new())) | ||
| .as_table_mut() | ||
| .ok_or_else(|| anyhow!("field 'env' in {} must be a TOML table", path.display()))?; |
There was a problem hiding this comment.
Store the provider key where Codex can read it
The updated provider block sets env_key = "BRAINTRUST_GATEWAY_API_KEY", but the secret is only written into a top-level [env] table rather than the environment of future Codex processes. Validating the generated file with Codex 0.144 shows that --strict-config rejects [env] as an unknown configuration field, while a normal invocation ignores it and fails with Missing environment variable: BRAINTRUST_GATEWAY_API_KEY; therefore bt gateway setup codex still reports success without producing usable authentication. Fresh evidence since the earlier comment is that the newly added provider now explicitly references this unavailable variable, so adding the provider block did not resolve the authentication failure.
Useful? React with 👍 / 👎.

add gateway cli option for bt
tested manually: