[Idea]: Add SiliconFlow as a native provider

[UNHNQ]

What are you trying to do?

Hi! I’m with the SiliconFlow team. We’d like to contribute native SiliconFlow provider support to Open Notebook. Our upstream contribution has already been merged into Esperanto and released in v2.27.0: lfnovo/esperanto#235

What feels difficult or missing today?

SiliconFlow is supported in Esperanto but is not yet directly selectable as a provider in Open Notebook. Users still need to configure it through the generic OpenAI-compatible option.

What outcome would help?

Users could select SiliconFlow directly and configure it through the standard provider setup flow. Would this contribution be welcome? We’re happy to handle implementation, testing, and documentation, and provide any additional information needed to evaluate it.

How do you handle this today?

No response

Additional context, examples, or possible directions

No response

How would you like to participate?

• I can add use cases or join the product/design discussion.
• I can help explore the technical approach.
• I can help implement an approved work item.
• I can test or validate a proposed solution.

Before posting

• I searched existing Discussions and Issues for related proposals.

[lfnovo]

@UNHNQ yes, and thanks for doing the Esperanto side first; that's the order we want for providers.

I checked both sides. In Esperanto, siliconflow is an OpenAI-compatible profile that declares the language modality. Here, Open Notebook still locks esperanto 2.26.0, so the work is two steps:

1. Bump esperanto to 2.28, content-core to 2.2 and podcast-creator to 0.13 #1408: bump esperanto (and content-core) to their latest releases. I'm taking that one.
2. Add SiliconFlow as a selectable provider (esperanto profile) #1409: register SiliconFlow the same way DashScope and DeepSeek are registered, plus docs. It depends on Bump esperanto to 2.28, content-core to 2.2 and podcast-creator to 0.13 #1408. Comment there and I'll assign it to you.

One thing to settle in the PR: the profile is language-only today. If SiliconFlow's embedding (or speech) endpoints are OpenAI-compatible, extending the Esperanto profile first would make SiliconFlow usable for more than chat; that's an upstream PR, then a bump here. Not required for #1409.

Status: accepted → graduated to #1409 (after #1408).

[UNHNQ]

@lfnovo Thanks for adding SiliconFlow support! We tested both the mainland China (api.siliconflow.cn) and global (api.siliconflow.com) endpoints with real credentials. Credential setup, connection testing, and model discovery all passed. Two-turn chat with Qwen/Qwen2.5-7B-Instruct also worked on both, including context recall and persisted messages. No blocking issues were found in the tested language-model chat flows.

[lfnovo]

@UNHNQ thanks for testing both endpoints with real credentials. SiliconFlow shipped as a selectable provider in #1409 (after the dependency bump in #1408), so I'm closing this as done.

If you extend the Esperanto profile to SiliconFlow's embedding or speech endpoints later, open a Discussion or Issue for the follow-up registration here.

Status: graduated (shipped in #1409)