Edit agents through a tabbed settings layout - #87
Open
nicolomagnante-cmd wants to merge 1 commit into
Open
nicolomagnante-cmd wants to merge 1 commit into
nicolomagnante-cmd wants to merge 1 commit into
Conversation
Editing an existing agent reused the four-step create stepper, forcing users to click Continue through sections just to change one setting. Editing now renders the four sections (Input, Output, Agent context, Prompt) as a settings-style left rail, each directly selectable with no step gating. A per-section "Save changes" action persists the agent in place and shows a saved confirmation; invalid sections are flagged in the rail. Creating a new agent keeps the sequential stepper unchanged. Also adds a settings shortcut on each row of the agents list linking straight to the edit page.
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
1 participant
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.
Motivation
Editing an existing agent reused the four-step create stepper. Users editing an agent almost always want to change one specific setting, but the stepper forced them to click Continue through earlier sections to reach it.
What changes
Editing now presents the four configuration sections as a settings-style layout instead of a stepper:
Input · Output · Agent context · Prompt, each directly selectable. No step gating; jump straight to the section you need.PUT /api/agents/:id) and shows a "Changes saved." confirmation, instead of navigating away. Sections with validation problems are flagged in the rail, and saving from a valid section jumps to any blocking section.Also adds a settings shortcut (gear) to each row of the agents list linking straight to the edit page.
Implementation notes
agent-create.tsx) still serves both create and edit, keyed on theagentIdroute param. The sharedCreateDraftstate, validation helpers, andsaveAgent()are reused unchanged — only the navigation chrome differs between modes (isEditing).Files
apps/control-plane/src/pages/agent-create.tsx— conditional settings rail + footer for edit mode;submitsplit into a reusablepersistAgent().apps/control-plane/src/pages/agents.tsx— per-row settings shortcut.apps/control-plane/src/styles.css—.agentEditLayout/.agentEditNav*and list action styles.Checks
pnpm typecheck·pnpm lint·pnpm test(717 passed) ·vite build— all green. Rendered and clicked through all four sections with no runtime errors.