Add Teapot Router as a provider (Anthropic + OpenAI dual-protocol gateway)

未关闭 适合新手
#13,486 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 8 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
67/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

首先阅读现有的 provider 条目、默认配置块和 provider 文档,了解 Continue 如何表示同时支持 OpenAI 和 Anthropic 协议的网关。使用提供的 API 基础地址和 Bearer 身份验证添加 Teapot Router,然后编写该 provider 及其默认配置的文档。当用户能够针对任一协议选择并配置该 provider 时,任务即告完成;请参照现有的 provider 检查和文档惯例进行验证。

由索引模型根据 Issue 内容生成。

描述

Problem

A number of Continue users arrive from the CLI agent world (Claude Code, Codex CLI) already holding a gateway API key, and the natural next question is "can the same key power Continue in my IDE?" Today the answer is "yes, but hand-write the provider block." A listed provider would remove that friction.

Request

Please consider Teapot Router as a listed provider option. It's a hosted gateway serving both API shapes from one key, pay-as-you-go:

  • OpenAI-compatible base: https://api.teapotrouter.com/v1 — /chat/completions and /responses both implemented
  • Anthropic Messages base: https://api.teapotrouter.com — so Claude models can run in their native protocol (incl. autocomplete/chat split by model)
  • Auth: Authorization: Bearer <key>
  • GET /v1/models returns the live model catalog (useful for model-name hints in the picker)
  • Machine-readable catalog JSON, public, same source as the website: https://teapotrouter.com/api/pricing
  • Keys are created at https://teapotrouter.com
Offer

If maintainers are open to it, I'll submit the implementation under your normal contribution process — provider entry, default config block, and docs snippet. If you'd rather not add vendor entries, closing this is completely fine; the manual config path works today.

Disclosure: I operate Teapot Router (independent project — no affiliate or rev-share implied). Happy to answer questions here or at [email protected].

主要语言
TypeScript
星标
36.5k
派生
5.6k
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

continuedev/continue 的其他 Issue

查看 continuedev/continue 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。