[hawkff]

• Recognize gemini-4-argon-high and its supported route prefixes using Pi's canonical Gemini metadata.
• Preserve proxy request IDs and existing alias precedence.
• Update Pi development dependencies to 1.3.0 and document CLIProxyAPI 8.0.30 compatibility.
• Set the package version and installation references to 0.2.0.

Summary by CodeRabbit

• New Features

  • Added metadata fallback support for Gemini Argon high IDs, including bare IDs and recognized route prefixes.
  • Gemini Argon high IDs retain their advertised IDs and use the Gemini streaming endpoint with high thinking enabled.

• Updates

  • Updated installation guidance and package version to 0.2.0, with development tooling aligned to the 1.3.0 release.

Confidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Adds gemini-4-argon-high discovery through Pi’s google/gemini-4-argon metadata, including supported route prefixes.

• Gemini 4 Argon high IDs use Pi’s canonical Gemini metadata.
• The package and its setup guide target Pi 1.3.0 and release 0.2.0.

No actionable issues were found. Tests were not run because dependencies are not installed.

_{Reviews (1) · Last reviewed commit: "Update Pi compatibility for 0.2.0" · Reviewed by Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: cf16ddfd-171a-4c54-bdc8-d2db596cc3d0

📥 Commits

Reviewing files that changed from the base of the PR and between fbec8c5 and 8b4df4c.

⛔ Files ignored due to path filters: 1

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing: 4

• README.md
• package.json
• src/catalog.ts
• test/provider.test.ts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The package version and development dependency ranges change. The README updates installation requirements and documents the Gemini Argon metadata fallback. The catalog adds that fallback, and provider tests cover Gemini Argon high IDs across recognized prefixes.

Changes: Gemini Argon support and release updates

Layer / File(s)	Summary
Gemini Argon metadata and provider coverage src/catalog.ts, test/provider.test.ts, README.md	The catalog maps gemini-4-argon-high to google/gemini-4-argon metadata. Tests cover Claude and Gemini catalog metadata, Gemini Argon high IDs with bare and recognized prefixed forms, streaming, and the HIGH thinking level without a token budget. The README documents the fallback.
Package and installation versions package.json, README.md	The package version changes to 0.2.0, and the Pi development dependency ranges change to ^1.3.0. README installation examples use package version 0.2.0 and require CLIProxyAPI 8.0.30.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~12 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 8b4df

No actionable merge-blocking issue is established; the update is ready for normal checks.

Pre-merge checks: 4 · 1

Failed checks: 1 warning

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (2 skipped: 2 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks: 4 passed

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating Pi compatibility for package version 0.2.0.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (2 skipped: 2 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches: 💡 1

📝 Generate docstrings: 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[hawkff]

The docstring-coverage warning does not warrant a code change here. The runtime change adds one entry to the existing fallback map and introduces no new function or control flow. The README documents the mapping and alias precedence.