AltimateAI / AltimateAI/altimate-code

feat: allow configuring custom gateway endpoint and token from TUI settings

未關閉
#676 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
TypeScript
星號
811
分支
134
平均合併
3 天 2 小時
30 天內合併 PR
50

描述

## Problem

Setting up a custom LLM gateway (e.g. corporate Bedrock proxy) requires editing JSON config files and shell profiles outside of Altimate Code. There is no way to configure the gateway endpoint or bearer token from within the TUI itself.

## Proposal

Add a TUI settings flow (accessible from the provider/model configuration UI) that lets users:

1. **Set a custom gateway URL** for any provider — writes `provider..options.baseURL` to the global config file.
2. **Enter a bearer token** inline — stores it via the existing `Auth.set()` mechanism (same as `providers login` on the CLI).

This removes the need to manually create `~/.config/altimate-code/altimate-code.json` or set environment variables for first-time gateway setup.

## Relevant Code

- Provider handler: `packages/opencode/src/provider/provider.ts:301` (`"amazon-bedrock"` block)
- Config schema: `packages/opencode/src/config/config.ts:1008` (provider options)
- CLI login flow: `packages/opencode/src/cli/cmd/providers.ts:250` (`ProvidersLoginCommand`)
- Auth storage: `packages/opencode/src/auth/service.ts`
- Global config write: `packages/opencode/src/config/config.ts:1532` (`globalConfigFile()`)

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。