Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Releases: paperfoot/nanaban-cli

v4.2.1

23 Apr 12:13
@github-actions github-actions

Choose a tag to compare

Assets 9
Loading

v4.2.0

23 Apr 02:45
@github-actions github-actions

Choose a tag to compare

Full Changelog: v4.1.0...v4.2.0

Loading

v4.1.0 — OpenRouter-first routing with automatic fallback

19 Apr 23:06
@longevityboris longevityboris

Choose a tag to compare

What changed

OpenRouter is now the default transport. One key reaches every model (Nano Banana + GPT-5 Image), separate rate bucket, no free-tier quota surprises.

Automatic fallback on transient failures. When the preferred transport hits RATE_LIMITED, NETWORK_ERROR, AUTH_INVALID, or AUTH_EXPIRED, nanaban silently retries on the next available transport. Success envelope gains a fallbacks audit trail. --via <t> still pins a single route when you want it.

Error envelopes now include hint — every error code carries an actionable recovery suggestion, so agents can self-correct instead of bailing out.

Why

Agents were dying on Gemini 429s even when a valid OpenRouter key was configured, because the router only tried one transport. Agents don't read intent from stack traces — they act on exit codes and envelopes. The whole point of configuring both keys is resilience; now you actually get it.

Upgrade

npm install -g nanaban@4.1.0

Agents

Set OPENROUTER_API_KEY as primary; optionally also GEMINI_API_KEY for local failover. Run nanaban agent-info for the machine-readable manifest — fallback policy, retry codes, envelope shapes are all there.

Loading

AltStyle によって変換されたページ (->オリジナル) /