Deleting a skill breaks the dialog layout

[shangxinyu1]

Summary

The dialog/layout becomes broken or messy when deleting a skill.

Current behavior

During the skill deletion flow, the conversation area layout becomes disordered.

Visible problems include:

• chips/tags wrap awkwardly at the bottom of the chat area
• form fields and content blocks appear misaligned
• the overall dialog composition looks unstable after the deletion-related state change

Expected behavior

When deleting a skill, the dialog and conversation layout should remain stable and properly aligned.

This includes:

• consistent spacing between chips, fields, and messages
• no broken wrapping or overflow in the bottom input area
• no unexpected layout shifts in the left chat panel

Steps to reproduce

1. Open a workflow that includes skills in the conversation context.
2. Trigger the delete/remove skill flow.
3. Observe the dialog/chat layout after the skill state changes.
4. Notice that the layout becomes messy or misaligned.

Notes

• The screenshots show layout instability in the left conversation panel.
• The issue appears around skill chips, related attachments/context pills, and the input/form area after deletion.
• This looks like a UI state/update problem rather than a content issue.

Why this matters

Deleting a skill is a routine management action. If the dialog breaks during that flow, the product feels unreliable and users may lose confidence in whether the deletion actually succeeded or whether the session state is still correct.

[lefarcen]

This is open for community help.

If you'd like to work on it, comment /claim below. The first /claim after the latest release gets it. Any comment, linked PR, or progress note keeps the claim active.

[lefarcen]

Hey @shangxinyu1, thanks for the detailed repro and screenshots — the failure mode around the skill/context chips and bottom input area is clear.

I’ve tagged this as bug and help wanted. My current read is that this sits in the web composer/context UI path rather than the delete API itself: SkillsSection refreshes the registry after deleting a user skill, while ChatComposer / PluginsSection / ContextChipStrip own the staged skill chips, active plugin context chips, and inline form area that can shift in the left conversation panel.

Working hypothesis: after a skill is removed, one of those composer-side rows keeps stale or newly-wrapped context state, so the active chip/form stack changes height/alignment unexpectedly. The next useful step is to reproduce this with an active skill/plugin context, then add a regression around the composer/plugin section clearing or stabilizing when the skill disappears from the registry.

[T-sanjay-ram]

/claim

I’ll reproduce the skill-deletion flow and prepare a focused regression fix after #6920 completes manual QA, since the composer/context state paths overlap.

[lefarcen]

Hey @T-sanjay-ram — thanks for picking this up. Since you’re waiting on #6920 QA first, roughly what timeline are you expecting once you start: a few hours, 1–3 days, about a week, or longer?

[T-sanjay-ram]

I expect 1–3 days after #6920 clears manual QA. I’ll start by reproducing the current behavior and post a progress update; if the current implementation no longer reproduces the reported layout break, I’ll report that rather than force a PR.

[lefarcen]

Sounds good, @T-sanjay-ram — 1–3 days noted once #6920 clears QA. Starting with a fresh repro and reporting back if the layout break no longer shows up is exactly the right call.

[lefarcen]

Hey @T-sanjay-ram, gentle check — still on this one? Anything blocking?

[T-sanjay-ram]

Yes, still on it. The only dependency is that #6920 remains open and its required manual QA has not completed, so I have not started potentially overlapping composer changes yet. No other technical blocker—I’ll begin the fresh repro as soon as that clears and post an update within a day.

[lefarcen]

Understood, @T-sanjay-ram — waiting until #6920 clears manual QA before touching overlapping composer paths makes sense. Thanks for calling out that there isn’t another blocker; once that clears, a fresh repro plus an update within a day sounds like the right next step.

[T-sanjay-ram]

yehhh!!
sure..