Implement tabbed form generator and interactive key-value editors#1791
Merged
fderuiter merged 1 commit intoJul 23, 2026
Conversation
…test data editors
fderuiter
deleted the
jules/feat/tabbed-form-kv-editor-js1-cd491aa1-bf77-4e6d-9aa3-b5fd4b5bbec5
branch
July 23, 2026 14:47
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.
Description
This PR addresses usability and validation challenges in the current form generator by introducing declarative tabbed layouts and visual, interactive editors.
Previously, configuring complex fields—such as tools and output schemas—forced users to write raw JSON schemas or scroll through a cluttered, single-page vertical form. This led to frequent validation errors and manual UI bypasses.
By transitioning to structured editors and a dynamic layout engine, we eliminate raw JSON editing, restrict user inputs to valid configurations, and organize settings into logical visual tabs.
Why these changes were made
What was accomplished
1. Dynamic Layouts & Tabbed Sections
render_schema_forminstudio/helpers.pyto accept alayout_configdictionary and alayout_typeparameter.2. MCP-Compliant Tools Editor
3. Output Schema Key-Value Editor
type: objectJSON Schema, with a read-only live output preview block.4. Workflow Test Data Editor
5. State Reconciliation & Dynamic Validation
PromptSchemaandWorkflowSchemamodels.6. Testing & Coverage
tests/test_studio.pytargeting MCP tools compilation, output schema generation, and workflow test cases to prevent future regressions.