Support OpenAI-compatible endpoints for AI summaries

Open
#157 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 6 days

@yashiels is already working on this.

Since Oct 31, 2026.

  • #159 by @yashiels — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
swift
Domain
api, backend

Research direction

Start with AISummarySettings.normalizedModel and the code that builds the request to https://api.openai.com/v1/responses, and find where the base URL and Keychain key are read. Also check the repobar settings CLI keys. Done means a configurable OpenAI-compatible base URL that blocks invalid URLs, refuses redirects, and omits reasoning, with the OpenAI path unchanged.

Written by the indexing model from the issue text.

Description

clawsweeper:linked-pr-open clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:auth-provider issue-rating: 🦞 diamond lobster P3

AI summaries always call https://api.openai.com/v1/responses, and AISummarySettings.normalizedModel replaces any model outside the three public OpenAI ids with gpt-5.5. That rules out self-hosted or gateway setups (LiteLLM, local servers) that expose the Responses API.

Proposal: an explicit "OpenAI-compatible" provider mode that keeps the current OpenAI path and its model list unchanged:

  • its own base URL (HTTPS, or HTTP only for loopback), model id and Keychain API key, so a stored OpenAI key is never sent to another host;
  • an invalid or missing base URL blocks the request instead of falling back to OpenAI;
  • redirects are refused, and the OpenAI-only reasoning parameter is omitted;
  • matching repobar settings keys in the CLI.
Dominant language
Swift
Stars
2.2k
Forks
137
Avg merge
3d 1h
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from steipete/RepoBar

All issues in steipete/RepoBar

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.