Conversation
dairyqiu
force-pushed
the
fix/pi-oss-model-discovery
branch
from
September 16, 2026 20:02
c8f45cb to
655d075
Compare
Author
|
@rohita5l, could you review this PR as the approver? It adds Pi OSS discovery and MLflow chat-completions routing, with live one-turn inference passing for all seven discovered DeepSeek, GLM, and Kimi models. The branch is rebased on current main, and the focused suite and static checks pass. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Pi only configured Claude, OpenAI Responses, and Gemini providers. Workspace model discovery already identifies Kimi, GLM, and DeepSeek services, but Pi did not consume that OSS family or have a provider that could route it.
OpenCode works because it already maps OSS models to the AI Gateway MLflow chat-completions route. This is a Pi integration gap, not a Databricks AI Gateway limitation.
Fix
databricks-ossprovider using Piopenai-completionsagainst/ai-gateway/mlflow/v1.!ug auth-token.storeand strict-mode fields for the MLflow route.databricks-kimiprovider written by the earlier implementation.This revisits #227 on current
main. The earlier PR stopped at config-shape validation; this version validates live discovery and inference with the installed Pi client.Verification
uv run ruff check .uv run ruff format --check src/ tests/databricks-osswhile the developer state and real Pi config remained unchanged./ai-gateway/mlflow/v1/chat/completions.Residual risk
The live checks cover one-turn inference for every discovered OSS model. A multi-turn OSS tool-call loop is not yet covered.