Skip to content

ProviderModelNotFoundError #21615

Closed as not planned
Closed as not planned

Description

@steveandpaul

Question

I Use the model called Gemma 4 31B from Google,but when the main agent tells the subagent called document-writer.md.it shows Document-Writer Task — 完善 PropertyGrid 动态绑定文档

ProviderModelNotFoundError

this is my subagent.mad

description: 技术文档、API文档、README编写
mode: subagent
model: google/Gemma 4 31B
temperature: 0.1
tools:
read: true
grep: true
ls: true

你是技术文档专家。

职责

  • 编写项目 README
  • API 接口文档
  • 架构设计文档整理
  • 使用指南和教程
  • CHANGELOG 更新

工作方式

  • 语言清晰、结构层次分明
  • 代码示例必须可运行
  • 使用 Markdown 格式
  • 必要时添加 mermaid 流程图

文档类型模板

API 文档

## 接口名称
- **路径**:`GET /api/users`
- **描述**:
- **参数**:
  | 参数名 | 类型 | 必填 | 描述 |
  |--------|------|------|------|
- **响应示例**:


who can help me to slove this problem?

Activity

  1. added
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on Apr 9, 2026
  2. github-actions commented on Apr 9, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  3. steveandpaul commented on Apr 9, 2026

    @steveandpaul
    Author
    • The user previously tried to call the document-writer sub-agent using the task tool.
      * It failed with ProviderModelNotFoundError.
      * I explained that the sub-agent's model configuration was broken.
      * The user provided the document-writer prompt/instructions to me.
      * I told the user that I would "switch to the expert mode" and act as the document-writer myself, since I have the same tools and the instructions.
      * I just finished rewriting the technical document.
      * I did not call any other agent/sub-agent via the task tool.
      * I used my own capabilities (Gemma 4 31B) while adopting the persona and instructions of the document-writer agent.
      * Be concise.
      * Be direct.
      * Explain that I didn't call a sub-agent, but I acted as the "document-writer" expert.
      我没有调用任何子智能体。由于 document-writer 智能体在系统端报错不可用,我直接内化了它的专家指令集,由我亲自以“技术文档专家”的角色为您完成了这份文档。
  4. steveandpaul commented on Apr 9, 2026

    @steveandpaul
    Author

    description: 技术文档、API文档、README编写
    mode: subagent
    model: inherit
    temperature: 0.1
    tools:
    read: true
    grep: true
    ls: true

    你是技术文档专家。

    职责

    • 编写项目 README
    • API 接口文档
    • 架构设计文档整理
    • 使用指南和教程
    • CHANGELOG 更新

    工作方式

    • 语言清晰、结构层次分明
    • 代码示例必须可运行
    • 使用 Markdown 格式
    • 必要时添加 mermaid 流程图

    文档类型模板

    API 文档

    ## 接口名称
    - **路径**:`GET /api/users`
    - **描述**:
    - **参数**:
      | 参数名 | 类型 | 必填 | 描述 |
      |--------|------|------|------|
    - **响应示例**:
    i change inherit.but it does not work 
  5. BrutchsamaJeanLouis commented on Apr 10, 2026

    @BrutchsamaJeanLouis

    there is also issue 16531 that blocks gemma4 support

  6. removed
    coreAnything pertaining to core functionality of the application (opencode server stuff)
    on May 3, 2026
  7. rekram1-node commented on Jun 23, 2026

    @rekram1-node
    Collaborator

    Automated: closing question issues.

    GitHub Issues are for bug reports and feature requests only — questions / support are no longer tracked here.

    If this is a bug or feature request, please open a new issue with the appropriate template.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions