Roster: prompt measure, edit form shape, board-only controls - #272
Merged
Conversation
…the tab bar Three things that only showed up once there was real data in the view. ## The prompt looked cropped The Instructions card spanned both columns (~1050px) while the prose inside was capped at max-w-prose (~65ch), so the text stopped well short of the card edge and read as truncated. The cap was right, the card was wrong. Now the card sits in one column, which is ~530px ≈ 75ch on its own — the right measure — so the cap comes off and the text fills its container. ## The edit form was a very tall single column max-w-lg with twelve stacked controls. Widened to max-w-3xl and laid out as a two-column grid with group headings, so it reads as three short groups instead of one long scroll: Identity Name | What it does, Runtime | Model, Portrait Behaviour System prompt Tools MCP config path, Allowed tools, Skills Model was lifted out of the Behaviour group to sit beside Runtime — they're the same decision, and it was otherwise alone in a half-width column with dead space next to it. Textareas, lists and the (long) MCP path take the full row; short inputs pair up. Script agents leave Runtime unpaired, which is honest — there is nothing to put beside it. ## Board-only controls removed from the Roster New workspace, checklist, archived tasks and spend are all board/workspace concerns. On a global agent roster they did nothing, so they now render only on the board. Settings stays, since it's app-wide. Verified: tsc, eslint, IPC check 209, vitest 429, production build clean, and both editor variants plus the dossier walked in Chrome.
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.
Three things you spotted, all of which only showed up once there was real data in the view.
The prompt looked cropped
The Instructions card spanned both columns (~1050px) while the prose inside was capped at
max-w-prose(~65ch) — so the text stopped well short of the card edge and read as truncated. The cap was right; the card was wrong.The card now sits in one column, which is ~530px ≈ 75ch on its own. That's the correct measure, so the cap comes off and the text fills its container.
The edit form was a very tall single column
max-w-lgwith twelve stacked controls. Widened tomax-w-3xland laid out as a two-column grid with group headings, so it reads as three short groups instead of one long scroll:Modelwas lifted out of Behaviour to sit besideRuntime— they're the same decision ("which engine"), and it was otherwise alone in a half-width column with dead space beside it. Textareas, lists and the long MCP path take the full row; short inputs pair up.Script agents leave
Runtimeunpaired. That's honest — there's genuinely nothing to put next to it, and padding it out would be worse.Board-only controls removed from the Roster
New workspace, checklist, archived tasks and spend are all board/workspace concerns. On a global agent roster they did nothing, so they now render only on the board. Settings stays, since it's app-wide.
Verification
tsc,eslint, IPC check (209),vitest run→ 429, production build clean. Both editor variants (LLM and script) and the dossier walked in Chrome with the seeded agents.