Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

bug(agents): built-in agents cannot inherit an OAuth-backed host LLM

オープン
#809 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
68/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
ai, authentication

調査の方向性

Start in raven/config/product_render.py at inherit_llm, then trace the main runtime's provider-readiness or credential-resolution logic referenced by the issue. Add coverage for an OpenAI Codex OAuth host with no provider apiKey, while preserving own-key and API-key inheritance behavior. Done means all four built-in products inherit the host provider and resolve its OAuth credentials.

索引モデルが issue の本文から書いたものです。

説明

Summary

The four shipped agent products fail to launch when the host Raven uses an OAuth-backed provider such as OpenAI Codex, even though the host model is authenticated and works.

The products are documented to use either their own key or the host Raven LLM. The host-inheritance branch currently treats only a provider block containing an apiKey as usable, so an authenticated OAuth provider is rejected before the child runtime starts.

Environment

  • Raven: 0.2.2
  • Platform: macOS
  • Host provider: openai_codex
  • Host model: an account-catalog Codex model
  • Installation: published Raven tool/wheel

Reproduction

  1. Sign in with raven provider login openai-codex.
  2. Select an OpenAI Codex model as the main Raven model.
  3. Verify that raven doctor --probe succeeds.
  4. Open Agent Connector and re-test Raven-Code, Raven-Design, Raven-Oncall, or Raven-Research.
  5. Observe that each product starts and immediately exits.

The launchers report:

Raven-Code: CODE_API_KEY is not set and the host config has no provider key to inherit from
Raven-Design: configure a model provider in the host Raven settings before starting Design
Raven-Oncall: ONCALL_API_KEY is not set and the host config has no provider key to inherit from
Raven-Research: RESEARCH_API_KEY is not set and the host config has no provider key to inherit from

At the same time:

raven provider list
openai_codex  OpenAI Codex  OAuth  configured

raven doctor --probe
LLM Probe: success

Root cause

raven/config/product_render.py::inherit_llm currently gates inheritance on an API key stored inside a provider block:

providers = host.get("providers") or {}
if not any(isinstance(p, dict) and p.get("apiKey") for p in providers.values()):
    return ""

OAuth credentials are intentionally stored outside the provider block, so a working OAuth provider has no apiKey there. The function therefore returns an empty result before copying the host provider, routing, and model configuration.

This affects all four visible shipped products because their no-own-key paths call inherit_llm directly or depend on the same result.

Expected behavior

A host provider that is authenticated and usable through OAuth should be eligible for built-in-agent inheritance, just like an API-key provider. The child should receive the host provider/model binding and resolve the same OAuth credential store.

Actual behavior

The main Raven can answer through OpenAI Codex OAuth, but every built-in professional agent fails its handshake and cannot be dispatched.

Suggested fix scope

  • Replace the apiKey-presence gate with the same provider-readiness or credential-resolution logic used by the main runtime.
  • Ensure the rendered child process resolves the host OAuth credential store.
  • Add coverage for a host using OpenAI Codex OAuth with no provider apiKey.
  • Keep existing own-key and API-key inheritance behavior unchanged.

Privacy

This report contains no credential values, account identifiers, private paths, or private conversation data.

主要言語
Python
スター
4.1k
フォーク
94
平均マージ
10時間 2分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

EverMind-AI/Raven のほかの issue

EverMind-AI/Raven の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。