Skip to content

[RFC] providers: add Zhipu BigModel for text, image, video, and speech generation #234

Open
1 of 4 issues completed

Description

@FayeSpica

Minimal support

A user with one Zhipu BigModel account and API key should be able to write a script, generate an image, create a video, and synthesize narration in one OpenDirector project. Provide at least one supported model per capability. Generated media can be saved, adopted, and edited in the project.

Sub-issues

  • Chat · GLM streaming chat and tool calling.
  • Image · Synchronous text-to-image generation with GLM-Image.
  • Video · CogVideoX-3 only. Support text-to-video, single-image-to-video, and first-and-last-frame generation. Persist the remote task ID for recovery and register completed media as a candidate.
  • TTS and voices · GLM-TTS with preset voices for the minimum workflow. Cover voice cloning, listing, selection, and deletion in the voice work.

Shared provider configuration

Reuse OpenDirector's connection and credential storage across the four model categories. Scope model edits and deletions to the selected category and keep credentials isolated across accounts. The canvas and Agent share model capabilities, validation, and generation workflows.

Acceptance criteria

  • With a fresh configuration and one Zhipu BigModel account and key, generate text, an image, a CogVideoX-3 video, and narration with a preset voice. Verify media adoption and reuse after reopening the project.
  • Verify the shared canvas and Agent validation and result handling.
  • Verify account isolation and category-scoped configuration changes.
  • Verify the setup and error messages in English and Chinese.

Zhipu BigModel image API · Zhipu BigModel video API

Pull request evidence

Include screenshots in the PR description showing the implemented workflow running in OpenDirector and its result so reviewers can see how it works.

Activity

  1. added
    type:featNew capability or behaviour
    area:providerModel providers and generation protocols
    modality:videoVideo generation, editing or rendering
    modality:audioSpeech, music or audio processing
    on Nov 9, 2026
  2. changed the title [-][RFC] providers: add Z.ai for text, image, video, and speech generation[/-] [+][RFC] providers: add Zhipu BigModel for text, image, video, and speech generation[/+] on Nov 9, 2026
  3. PCcoding666 commented on Nov 10, 2026

    @PCcoding666
    Contributor

    I'd like to take the shared-connection acceptance work for #235–#238. I checked the current chat (#245, 781d3556), image (#251, 5d9b9d20) and video (#254, 909dfbd1) presets. All three use the same mainland BigModel base URL. With one saved fixture account, I ran the settings form’s matchingConnections helper for all nine source/destination pairs. Each same-category pair offered the saved connection, while all six cross-category pairs returned no match. I haven’t made a live provider call for this check.

    Would you be happy for me to cover entering a key once across categories, checking that edits and deletions stay within the selected category, and keeping two accounts on the same endpoint separate? I can contribute the shared fix and regression tests once we agree on how it should fit with the individual PRs, and include speech once #238 has a branch to test.

  4. FayeSpica commented on Nov 10, 2026

    @FayeSpica
    CollaboratorAuthor

    Thanks for checking this, @PCcoding666! Please go ahead with the shared BigModel connection.

    Feel free to open a draft PR or a new issue, and let’s see how we can make it easy for users to set up one API key across model categories.

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

Metadata

Metadata

Assignees

Labels

area:providerModel providers and generation protocolsmodality:audioSpeech, music or audio processingmodality:imageImage generation or editingmodality:videoVideo generation, editing or renderingtype:featNew capability or behaviour

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions