Skip to content

feat: add Lilac as an OpenAI-compatible provider#1426

Closed
Luew2 wants to merge 8 commits intodifferent-ai:devfrom
Luew2:feat/add-lilac-provider
Closed

feat: add Lilac as an OpenAI-compatible provider#1426
Luew2 wants to merge 8 commits intodifferent-ai:devfrom
Luew2:feat/add-lilac-provider

Conversation

@Luew2
Copy link
Copy Markdown

@Luew2 Luew2 commented Apr 10, 2026

Summary

Add Lilac as a provider in OpenWork with documentation and a friendly display label.

⚠️ Blocked by models.dev PR #1416 — That PR adds Lilac to the upstream provider catalog (models.dev), which is what makes Lilac appear as a built-in, selectable provider in OpenWork's model picker. This OpenWork PR is supplementary: it adds the friendly label and documentation.

Changes

  • apps/app/src/app/utils/index.ts — Add lilac: "Lilac" to FRIENDLY_PROVIDER_LABELS so the provider displays as "Lilac" instead of the raw ID
  • packages/docs/how-to-connect-lilac.mdx — New doc page with three setup paths:
    • Quick setup (built-in, once models.dev merges)
    • Manual setup (desktop .opencode.json fallback)
    • OpenWork Cloud setup (for teams)
  • packages/docs/docs.json — Add nav entry under Tutorials

Models

Model Model ID Context Vision Reasoning Tool calling Input price Output price
GLM 5.1 z-ai/glm-5.1 202,800 No Yes Yes $0.90/M tokens $3.00/M tokens
Kimi K2.5 moonshotai/kimi-k2.5 262,144 Yes Yes Yes $0.40/M tokens $2.00/M tokens

Related

- Add how-to-connect-lilac.mdx documentation covering desktop and Cloud setup
- Add Lilac friendly provider label in FRIENDLY_PROVIDER_LABELS
- Add Lilac doc page to docs.json navigation

Lilac (getlilac.com) provides an OpenAI-compatible API at api.getlilac.com/v1
with models including zai-org/glm-5.1 and moonshotai/kimi-k2.5.
@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openwork-landing Ready Ready Preview, Comment, Open in v0 Apr 10, 2026 8:49pm

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Apr 10, 2026

@Luew2 is attempting to deploy a commit to the Different AI Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown
Contributor

The following comment was made by an LLM, it may be inaccurate:

Luew2 added 2 commits April 10, 2026 13:18
… docs links

- Add vision/image support and reasoning flags based on Lilac's OpenAI compatibility page
- Link to Lilac's own docs (models, openai-compatibility, local-tools, pricing)
- Reference Lilac's API key guide and console
- Add introductory paragraph mentioning Lilac's supported features
- Set attachment: false and remove image from modalities for GLM 5.1
- Clarify intro paragraph: vision is model-dependent
Luew2 added 2 commits April 10, 2026 13:22
…ts from Lilac docs

- Fix model ID: zai-org/glm-5.1 -> z-ai/glm-5.1 (per Lilac's models page)
- Update GLM 5.1 context: 202,800 tokens, output 131,072
- Update Kimi K2.5 context: 262,144 tokens
- GLM 5.1 is open_weights: true (MIT licensed)
- Add model details table with pricing
- Add pricing column from Lilac's models page
@src-opn
Copy link
Copy Markdown
Collaborator

src-opn commented Apr 10, 2026

Thanks for the PR. We’re trying to keep provider-specific documentation limited to the major providers with broad user demand. Since there are many OpenAI-compatible providers, we use the generic custom provider docs for the long tail rather than maintaining a dedicated page for each one.

Given that policy, we’re not going to merge a Lilac-specific docs page, so I’m closing this out. Thanks again for taking the time to contribute.

@src-opn src-opn closed this Apr 10, 2026
@Luew2
Copy link
Copy Markdown
Author

Luew2 commented Apr 11, 2026

Thanks for the PR. We’re trying to keep provider-specific documentation limited to the major providers with broad user demand. Since there are many OpenAI-compatible providers, we use the generic custom provider docs for the long tail rather than maintaining a dedicated page for each one.

Given that policy, we’re not going to merge a Lilac-specific docs page, so I’m closing this out. Thanks again for taking the time to contribute.

No worries -- we're trying to get merged into models.dev so we at least are easier to have out api key added: anomalyco/models.dev#1416 hopefully a maintainer can help us there soon :)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants