feat(expert): structured plan card with active-plan pointer - #8469
Open
andypalmi wants to merge 6 commits into
Open
feat(expert): structured plan card with active-plan pointer#8469andypalmi wants to merge 6 commits into
andypalmi wants to merge 6 commits into
Conversation
added 3 commits
September 10, 2026 12:14
Render the plan card from the structured fields (name, description, status) carried alongside the markdown. While the plan awaits approval it is shown in full with its status pill and action buttons; afterwards it collapses to a single "Plan: <name>" row, expandable to re-read, and badged Active when it is the plan being worked on. An agent that sends only markdown content falls back to the previous layout, so older instances render unchanged.
Size the plan name like a top-level heading, give the Active badge a solid accent fill for legibility, drop the left accent rail, and space the description from the plan body.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feat/expert-task-list-ui #8469 +/- ##
===========================================================
Coverage ? 76.88%
===========================================================
Files ? 460
Lines ? 24741
Branches ? 6596
===========================================================
Hits ? 19022
Misses ? 5719
Partials ? 0
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Closes FlowFuse/engineering#345
Summary
Turns the plan reply into a structured card with a name, a description, and a collapsible body, and introduces an active-plan pointer so the chat always shows which plan is currently in effect.
When a plan is waiting for approval the card is expanded with its action buttons. Once approved it collapses to a single line, and the plan that owns the currently pinned task list is marked with an
Activepill. Approving another plan, or reactivating an earlier one, moves the pill and swaps the pinned task list to match.Changes
PlanCard.vue: structured layout with aPlan: <name>heading, a description line, and the plan body inside a collapsible section; anActivepill in the collapsed header; awaiting-approval vs approved states; heading sized like a top-level heading and the pill given a solid accent fill for legibility.AnswerWrapper.vue: passesname,description,active, andawaiting-approvalinto the card, derivingisActivePlanfrom the plan id and the active-plan pointer.product-expert.js: adds theactivePlanIdgetter, derived from the pinned task list'splanId, so the active plan and its task list stay in sync.Anatomy of the card
While a plan awaits approval the card is fully expanded. The heading is the plan name, followed by the plan description, then the plan content, with the action buttons at the bottom. The card also falls back gracefully: a plan without structured fields renders as before, so this is backward compatible.
Collapsed states
Once approved the card collapses to a single line. The active plan carries the
Activepill; other plans do not.Active:
Not active:
Active-plan pointer
Only one plan is active at a time. Approving a new plan makes the previous one no longer active, so the
Activepill moves to the newest approved plan.Reactivating an earlier plan
You can ask the Expert to reactivate a previous plan. Doing so moves the
Activepill back to that plan and swaps the pinned task list to that plan's tasks.Reactivating the first plan: the pinned task list at the bottom now shows the first plan's tasks.
Reactivating the second plan again: the pinned task list swaps to the second plan's tasks, matching the currently active plan.
Backward compatibility
The whole plan and task experience is gated behind the
supportsPlansAndTaskscapability flag, which is introduced in the stacked task list PR #8468. When the flag is absent the agent runs in its previous mode and does not emit the plan/task surface.A plan reply without the structured name/description fields also renders exactly as it did before, so older agent responses are unaffected.
Testing
Activepill.