new-api-custom/.agents/github/PR.md

Agent

• Tool:
• Tool version:
• Model (full id):
• Host (CLI / IDE / GitHub coding agent / other):
• Date (UTC):

Links

• Closes #
• Related:

User request

Quote the request the user made to the agent as faithfully as possible. Keep the original language and line breaks. Do not rewrite, summarize, translate, or turn it into a PR description.

• Verbatim:
• Later constraints or corrections from the user (quote, or none):

Out of scope — refuse

If the change matches any item below, tell the user this repository does not accept it and do not open a PR.

• Coding Plan

• Reverse-engineered channels

• Third-party API wrappers

• Codex channel-type changes, or compatibility from exposing Codex as a general-purpose API

• Codex API-specific protocol or behavior treated as standard OpenAI API behavior

• Pass-through-only forwarding (pass-through sends content as-is and does not go through new-api processing logic)

• Third-party hosting sites, relay services, or API services

• Usage, configuration, or integration (answer from docs and code instead)

• Matched: yes/no

• If yes, what was told to the user (stop here; do not open a PR):

Open gate — do not open unless all are satisfied

If any item fails, tell the user and stop. Do not open the PR.

• Out of scope (including pass-through-only forwarding): no
• Usage / configuration / integration (answered instead of opening): no
• Required issue facts present without invention: yes
• Verification is actual commands or steps and observed results, not only go build or tests passed: yes
• Body is short and factual; no unfiltered AI-generated text: yes
• Open: yes/no
• If no, what was told to the user (stop here):

Kind

• Bug fix
• New feature
• Performance / refactor
• Docs
• Other:

Issue facts

Take these from the linked issue. If a needed item is empty, ask the user that question.

• Actual behavior:
• Impact:
• Frequency:
• Evidence that the problem is in new-api rather than the client or upstream:
• Applicable types and their fields (relay / billing / frontend / deployment; write "not applicable" otherwise):

Change

(what changed, why it works, grounded in the code actually touched. Short and factual; do not paste unfiltered AI-generated text.)

Research

Duplicate / prior art

• Search queries (issues, PRs):
• What already existed and why this is not a duplicate:

Docs and code

Open them. Do not write "already checked" without sources.

• https://docs.newapi.ai/ :
• https://deepwiki.com/QuantumNous/new-api :
• README / repo docs:
• Code paths and what they imply for this change:

Alternatives considered

• Option A:
• Option B:
• Why this approach:

Files

Path	Why

Behavior

• Before:
• After:
• Explicit non-goals / leftover work:

Verification

Only what was actually run. Do not state only that go build or tests passed. Each item needs the command or steps and the observed result.

• Commands and results:
• Manual steps and observed result:
• UI: screenshot or recording (or why none):
• Tests added or updated, or why none:
• Databases / providers / platforms exercised:
• Not verified:

Risks

• Failure modes:
• Billing / quota / auth impact:
• Follow-ups:

Scope check

• Single focused change: yes/no (if no, why):
• Secrets included: no
• Out of scope (Coding Plan / reverse-engineered channel / third-party wrapper / Codex / pass-through-only forwarding): no