openclaw - ✅(Solved) Fix feat: Add YandexGPT (Yandex AI Studio) as native provider [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#59828Fetched 2026-04-08 02:40:00
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
cross-referenced ×2

Fix Action

Fixed

PR fix notes

PR #59768: feat: add YandexGPT as native provider via Yandex AI Studio

Description (problem / solution / changelog)

What

Add Yandex AI Studio as a bundled provider plugin, giving OpenClaw users native access to YandexGPT models through the OpenAI-compatible chat completions API.

Why

  • Large market — YandexGPT serves the Russian-speaking developer community (~300M speakers) and is one of the top LLM providers in the CIS region.
  • Data sovereignty — Yandex Cloud infrastructure is located in Russia, which matters for compliance-sensitive workloads.
  • Competitive pricing — YandexGPT Lite offers very low per-token costs for high-throughput use cases.
  • OpenAI-compatible API — Yandex AI Studio exposes a standard /v1/chat/completions endpoint, making integration straightforward via the existing openai-completions API type.

How

Follows the exact same extension pattern as DeepSeek, Together, and other defineSingleProviderPluginEntry-based providers:

New files (extensions/yandex/)

FilePurpose
index.tsPlugin entry — registers provider with auth, wizard, and catalog
models.tsModel catalog definitions (YandexGPT Pro, Pro RC, Lite)
provider-catalog.tsBuilds the ModelProviderConfig for discovery
onboard.tsConfig appliers using createModelCatalogPresetAppliers
api.tsRe-exports for the plugin-sdk facade
openclaw.plugin.jsonPlugin manifest
package.jsonExtension package
index.test.tsPlugin registration + catalog tests
README.mdExtension readme

Modified files

FileChange
package.jsonAdded ./plugin-sdk/yandex export
scripts/lib/plugin-sdk-facades.mjsAdded yandex facade entry
src/plugins/provider-auth-storage.tsAdded setYandexApiKey
docs/providers/yandex.mdProvider documentation
docs/providers/index.mdAdded Yandex to provider list
docs/docs.jsonAdded Yandex to docs navigation

Models

Model IDNameContextNotes
yandexgpt/latestYandexGPT Pro32KStable pro model
yandexgpt/rcYandexGPT Pro RC32KRelease candidate
yandexgpt-lite/latestYandexGPT Lite32KFast, low-cost

Auth

  • Env var: YANDEX_API_KEY
  • CLI: --yandex-api-key <key>
  • Wizard: openclaw onboard --auth-choice yandex-api-key

API keys are obtained from Yandex AI Studio.

Base URL

https://llm.api.cloud.yandex.net/v1 — the official OpenAI-compatible endpoint from Yandex Cloud, verified against the yandex-ai-studio-sdk source.

Testing

pnpm test:extension yandex

Tests verify:

  • Plugin registration and auth wizard metadata
  • Static model catalog (correct model IDs, base URL, API type)
  • All models marked as non-reasoning, text-only, openai-completions

Checklist

  • Follows existing code style and patterns exactly (mirrors DeepSeek/Together)
  • Tests included
  • Documentation updated (provider docs + navigation)
  • No new dependencies
  • Commit messages follow project convention
  • AI-assisted (OpenClaw agent) — code reviewed and understood

Changed files

  • docs/docs.json (modified, +1/-0)
  • docs/providers/index.md (modified, +1/-0)
  • docs/providers/yandex.md (added, +56/-0)
  • extensions/yandex/README.md (added, +24/-0)
  • extensions/yandex/api.ts (added, +7/-0)
  • extensions/yandex/index.test.ts (added, +75/-0)
  • extensions/yandex/index.ts (added, +38/-0)
  • extensions/yandex/models.ts (added, +73/-0)
  • extensions/yandex/onboard.ts (added, +26/-0)
  • extensions/yandex/openclaw.plugin.json (added, +28/-0)
  • extensions/yandex/package.json (added, +12/-0)
  • extensions/yandex/provider-catalog.ts (added, +10/-0)
  • package.json (modified, +4/-0)
  • scripts/lib/plugin-sdk-entrypoints.json (modified, +1/-0)
  • scripts/lib/plugin-sdk-facades.mjs (modified, +13/-0)
  • src/generated/plugin-sdk-facade-type-map.generated.ts (modified, +9/-0)
  • src/plugin-sdk/yandex.ts (added, +35/-0)
  • src/plugins/bundled-provider-auth-env-vars.generated.ts (modified, +1/-0)
  • src/plugins/provider-auth-storage.ts (modified, +3/-0)
RAW_BUFFERClick to expand / collapse

🚀 Feature Request: YandexGPT as Native Provider

Author & Initiator: @Bullwinkle — this idea, implementation, and PR are my initiative.

What

Add Yandex AI Studio (YandexGPT) as a first-class bundled provider in OpenClaw, alongside existing providers like OpenAI, Anthropic, DeepSeek, etc.

Why

  • Large market: YandexGPT serves millions of Russian-speaking developers and businesses
  • Competitive pricing: significantly cheaper than OpenAI for Russian-language tasks
  • Data sovereignty: important for users who need to keep data within Russian/CIS infrastructure
  • OpenAI-compatible API: Yandex AI Studio provides an OpenAI-compatible endpoint, making integration clean and maintainable
  • Growing ecosystem: Yandex is investing heavily in AI, with new models (YandexGPT Pro, Lite, 32K context) shipping regularly

Models

ModelContextUse Case
YandexGPT Pro32KBest quality, complex tasks
YandexGPT Pro RC32KRelease candidate, latest features
YandexGPT Lite32KFast, cost-effective

Implementation — ALREADY DONE ✅

I have a complete, working implementation ready as a PR:

👉 PR #59768 — feat: add YandexGPT as native provider via Yandex AI Studio

The PR includes:

  • ✅ Full provider plugin (extensions/yandex/) following defineSingleProviderPluginEntry pattern (same as DeepSeek, Together)
  • ✅ Model catalog (3 models)
  • ✅ Onboarding flow (openclaw onboard --auth-choice yandex-api-key)
  • ✅ Plugin SDK facade + exports
  • ✅ Unit tests
  • ✅ Documentation (docs/providers/yandex.md)
  • ✅ All automated review comments addressed (Greptile P0/P1/P2 fixes applied)
  • 44/45 CI checks pass (1 failing = pre-existing Windows flaky test, proven unrelated)

How to help

If you'd benefit from YandexGPT in OpenClaw, please:

  • 👍 React with thumbs up on this issue
  • 💬 Comment with your use case
  • 🔍 Review the PR #59768

Attribution

This feature was conceived, designed, implemented, and submitted by @Bullwinkle. The complete implementation is in PR #59768.


OpenClaw + YandexGPT = better AI access for millions of developers 🇷🇺🌍

extent analysis

TL;DR

Review and merge the existing PR #59768 to add YandexGPT as a native provider in OpenClaw.

Guidance

  • Review the PR #59768 and verify that it meets the project's standards and requirements.
  • Test the implementation to ensure it works as expected, especially for Russian-language tasks and data sovereignty use cases.
  • Check the automated review comments and Greptile P0/P1/P2 fixes to confirm they are properly addressed.
  • Investigate the failing Windows flaky test to confirm it is unrelated to the PR.

Example

No code snippet is provided as the issue does not require a code-level fix, but rather a review and merge of the existing PR.

Notes

The implementation is already complete, and the PR has passed 44 out of 45 CI checks. The failing test is reportedly unrelated to the PR.

Recommendation

Apply the workaround by reviewing and merging PR #59768, as it provides a complete implementation of YandexGPT as a native provider in OpenClaw, addressing the needs of Russian-speaking developers and businesses.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING