# New ai docked composer **URL:** \ **Category:** Bug\ **Tags:** composer, ai\ **Created:** [April 30, 2026, 7:58pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961 "2026-04-30T19:58:09Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![keegan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/keegan/32/383395_2.png) [@keegan](https://meta.discourse.org/u/keegan)\ **Post date:** [May 1, 2026, 10:13pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/5 "2026-05-01T22:13:29Z")
Thanks Lilly! I made some fixes earlier this morning: > > > Previously, the AI bot docked composer showed the formatting toolbar by default,… had no visual affordance for scrolling to new content during streaming, and incorrectly reported a streaming-in-progress state after page refresh when the stream had already completed (caused by replaying a stale message bus chunk on subscribe). > > This change hides the toolbar behind an animated toggle button, adds a scroll indicator above the composer (animated dots when streaming, chevron-down otherwise), moves the resize handle inside the editor box, suppresses the scroll fade gradient when already at the bottom of the page, and fixes the stale streaming state by detecting when a replayed message bus chunk refers to a post already rendered without a .streaming class. > > https://github.com/user-attachments/assets/bae788d1-2105-4c47-93c1-08bb58dfd850 and I got a PR ready with a few fixes and improvements based on what you’ve outlined here: > > > Previously, the AI bot docked composer had several mobile issues — the keyboard …covered the input, the timeline widget floated awkwardly, the layout had a misaligned left margin, and the edit pencil was completely broken because \`#reply-control\` was hidden unconditionally. > > This change fixes keyboard handling by tracking visualViewport to position the composer above the software keyboard, hides the timeline/progress widget on mobile, removes the desktop content offset on small screens, allows the floating composer to appear for post edits, and adds left padding to prevent text from overlapping the toolbar toggle button. > > | Before | After | > | ------ | ----- | > | https://github.com/user-attachments/assets/521768fb-7dbd-4dad-9c86-78f4a86db815 | https://github.com/user-attachments/assets/cf008970-03b6-4b70-adac-67a7d3746101 | Once that’s merged that should fix the inability to edit as well as those mobile bugs. Regarding this: > [@Lilly](#): > > can’t switch to markdown composer - ~~it is stuck in RTE mode and the button does nothing~~ it’s the preview screen that isn’t there and no button to show it. This was ultimately a design decision. RTE is intended to be the primary way to use this docked composer, however, if you prefer markdown, it’s available but due to lack of space we’re not including the preview. When I first implemented it, I had a button to toggle on/off the preview but since this was essentially the same as the RTE toggle, I removed it. Also regarding these: > [@Lilly](#): > > - when i try to quote the bot it seems to break the sidebar somewhat > - on meta - it inserts a giant gap and sometimes disappears; on my forum, the sidebar always disappears > - a few times, quoting also locked me into the bot convo so that the return to forum button was broken > - quotes also sometimes disappear in the composer as soon as i start typing Unfortunately I wasn’t able to reproduce these. If you could still repro after all these changes could you let me know. Thanks! 🙂 --- _[View the full topic](https://meta.discourse.org/t/new-ai-docked-composer/401961)._