Skip to content

feat: support custom Responses providers - #33

Merged
code-yeongyu merged 3 commits into
code-yeongyu:mainfrom
zidou-kiyn:feat/custom-responses-provider-support
Jul 30, 2026
Merged

code-yeongyu merged 3 commits into
code-yeongyu:mainfrom
zidou-kiyn:feat/custom-responses-provider-support

Conversation

@zidou-kiyn

@zidou-kiyn zidou-kiyn commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Enable apply_patch for GPT models exposed through custom provider names when the model API is openai-responses or openai-codex-responses.
  • Preserve the existing provider allowlist behavior and continue requiring model ids to start with gpt-.
  • Document custom provider activation and grammar-tool fallback behavior, with tests covering both Responses API variants.

Verification

  • npm run check (typecheck + biome)
  • npm test (55 tests passed)
  • npm pack --dry-run (release sanity)
  • pi -e ./src/index.ts smoke-tested locally with a custom openai-responses provider

apply_patch impact

  • Tool schema / grammar behavior is documented in README
  • Workspace path safety remains covered by tests
  • CHANGELOG entry added under [Unreleased]

Related issues

No existing issue directly tracks custom Responses provider activation.

Review in cubic

@zidou-kiyn
zidou-kiyn requested a review from code-yeongyu as a code owner July 29, 2026 17:48
@code-yeongyu
code-yeongyu merged commit cb48b56 into code-yeongyu:main Jul 30, 2026
2 checks passed
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.

2 participants