feature: Custom AI for Chat Completions-only hosts (OpenAI provider uses Responses)

Open Beginner friendly
#10,877 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
ai, documentation

Research direction

Start by locating the Custom AI and OpenAI provider documentation, then compare the entry points named in backend/windmill-ai/src/providers/openai.rs and providers/other.rs. Document that OpenAI uses Responses while Custom AI appends /chat/completions to a /v1 base URL, including the PZERO example; done means a newcomer can configure a Chat Completions-only host without confusing the provider or URL.

Written by the indexing model from the issue text.

Description

webmux_oneshot

The OpenAI AI provider builds {base_url}/responses (backend/windmill-ai/src/providers/openai.rs). Custom AI builds {base_url}/chat/completions (providers/other.rs). Two details are easy to get wrong on a Chat Completions-first host:

  1. Do not pick the OpenAI provider and paste a custom base URL. That wire is Responses.
  2. Custom AI base URL is the /v1 root. The code appends /chat/completions. Do not paste the chat path.

PZERO is a live OpenAI-compatible host. Catalog: GET https://api.pzero.studio/v1/models. Default text id: deepseek-v4-flash. Prepaid Bearer key (pzero_…). POST /v1/responses exists (401 without a key, not 404) but Chat Completions is the working path for agent tools.

Custom AI:

  • Base URL: https://api.pzero.studio/v1
  • API key: pzero_…
  • Model: deepseek-v4-flash

No first-party provider asked. If a named vendor subsection is too much, OpenAI=Responses vs Custom AI=Chat Completions is the docs gap.

Dominant language
Rust
Stars
18k
Forks
1.1k
Avg merge
1d 1h
Merged PRs (30d)
328

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from windmill-labs/windmill

All issues in windmill-labs/windmill

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.