Skip to content

Enable configuring base URL for Anthropic provider#107

Open
windoze wants to merge 4 commits intograniet:mainfrom
windoze:main
Open

Enable configuring base URL for Anthropic provider#107
windoze wants to merge 4 commits intograniet:mainfrom
windoze:main

Conversation

@windoze
Copy link
Copy Markdown
Contributor

@windoze windoze commented Jan 29, 2026

  1. Enable configuring base URL for Anthropic provider
  2. Add a new onboarding step to configure base URL in TUI app.
  3. Add backend field in config.toml after onboarding so newly configured provider can be other than OpenAI
  4. Filter empty messages before sending in TUI, which causes Anthropic API error.
  5. Fix tool use in TUI with Anthropic provider. Previously the tool result messages were sent with wrong role and got rejected.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8076f42356

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

This commit fixes two issues that prevented the Anthropic provider from
working correctly in the TUI:

1. Onboarding now sets backend field in provider config
   - Previously, providers configured through TUI onboarding defaulted to
     OpenAI backend because the `backend` field wasn't being set
   - Now automatically sets `backend` field based on selected provider
   - Added Display impl for LLMBackend to enable string conversion

2. Filter out empty placeholder messages before sending to API
   - TUI creates empty assistant messages as placeholders before streaming
   - These empty messages were being sent to Anthropic API, causing
     "text content blocks must be non-empty" errors
   - Now skips empty messages when converting to ChatMessage format

Fixes issues where:
- CLI worked but TUI failed with Anthropic provider
- Custom base URLs didn't use correct backend
- Empty placeholder messages caused API errors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant