Skip to content

fix(ui): expose both decisions playground endpoints - #45817

Merged
kerry-berri merged 4 commits into
mainfrom
litellm_playground_systemone_route
Oct 10, 2026
Merged

kerry-berri merged 4 commits into
mainfrom
litellm_playground_systemone_route

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Let users QA /v1/decisions and /v1/systemone in the Decisions Playground, with Form and JSON views for both requests and responses

TLDR

Problem this solves:

  • Playground cannot demonstrate the /v1/decisions API shape
  • Endpoint labels mix product names and route paths

How it solves it:

  • Offer both routes with literal labels and route-specific forms
  • Match response presentation to the selected Form or JSON view
  • Preserve independent drafts and cancel requests when switching endpoints

Intentional product change: the TypeSafe-specific endpoint option is removed, but configured TypeSafe models and backend routes remain available. Both endpoints offer Form and JSON editing. Form shows answer cards; JSON shows the actual response JSON. Switching views reuses the existing response without another request. Examples omit model until discovery or explicit selection, preserving proxy-default routing

User Flow

Before, users cannot explore the OpenAI Decisions request and response shapes

  1. Open Playground and select Decisions
  2. Choose between Decisions · /v1/systemone and TypeSafe · /typesafe/v1/systemone
  3. Send a request using state and a questions object
  4. Responses stay as answer cards even when editing JSON

After, users can QA both APIs and inspect their actual shapes

  1. Open Playground and select Decisions
  2. Choose /v1/decisions or /v1/systemone, then choose a configured model
  3. Edit input and array questions for Decisions, or state and keyed questions for System One
  4. Send in Form to see answer cards, or switch to JSON to inspect the full request and response
  5. Switch endpoints without losing either draft

Validation

182 focused tests pass across ten Playground test files. Coverage includes both request and response formats, Form/JSON switching without resending, predicate/choice/score/refusal cards, boolean choices, adding/removing form items, metadata and message preservation, independent drafts, reset, validation, cancellation, late responses and model discovery

npm run typecheck and make check pass. ESLint reports one existing component-complexity warning and no errors

Automated browser testing and live provider calls have not been run by this session

Caveats

Low

  • Message-array and image input remain editable in JSON; form edits preserve them

Pre-Submission checklist

  • I have added meaningful tests
  • The handful of test files covering my change pass locally
  • My PR passes all required CI/CD checks
  • My PR's scope is as isolated as possible
  • I have received a Greptile Confidence Score of at least 4/5

Type

Bug Fix

Final Attestation

  • The tests check the right things, including the edge cases, and regressions in the respective real-world customer use-cases are not possible after this PR

Link to Devin session: https://app.devin.ai/sessions/9b4fbfc9194c4fb78d3fb268908344c4
Open in Devin Desktop: https://app.devin.ai/desktop/session/9b4fbfc9194c4fb78d3fb268908344c4?variant=devin
Requested by: @kerry-berri


Note

Devin errored when opening this Pull Request as kerry-berri.
As a fallback, Devin opened this PR as itself.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


kerry seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration devin-ai-integration Bot changed the title fix(ui): simplify playground decision endpoint fix(ui): expose both decisions playground endpoints Oct 10, 2026
@greptile-apps

greptile-apps Bot commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 4/5

[Medium impact] Removes endpoint selection from the playground decision feature.

Fix the placeholder-model send path before merging.

Findings

  1. P1 Send uses a placeholder ▶

Summary

The Playground now shows a fixed /v1/systemone endpoint and keeps the model picker visible.

  • The Decisions Playground sends every request to /v1/systemone.

Intentional change acknowledged by devin-ai-integration[bot]: users can no longer choose /typesafe/v1/systemone in the Playground. The PR description explicitly identifies this as a product change; the backend route remains unchanged.

Reviews (1) · Last reviewed commit: "fix(ui): simplify playground decision en..." · Reviewed by Greptile

litellm-stampbot and others added 2 commits October 10, 2026 17:15
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@kerry-berri
kerry-berri merged commit 33b9d84 into main Oct 10, 2026
82 checks passed
@kerry-berri
kerry-berri deleted the litellm_playground_systemone_route branch October 10, 2026 18:23
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.

3 participants