>
> 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! 🙂
---
### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [May 1, 2026, 10:46pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/6 "2026-05-01T22:46:24Z")
> [@keegan](#):
>
> 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.
ok that’s fine, i just wasn’t sure if lack of previewer was intended behaviour. as long as i have my markdown it’s fine, i don’t need the previewer of course (can just toggle it like you say)
great work. i’ll mess around with it more a bit over the next few days. thanks again! have a good weekend! 😃
---
### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [May 3, 2026, 7:12pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/7 "2026-05-03T19:12:00Z")
well it is much less buggy, but uploading files appears to be broken after the first post.
---
### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [May 3, 2026, 11:49pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/8 "2026-05-03T23:49:08Z")
so far the only bugs i am finding are:
1. quoting doesn’t do anything - (but copy quote and paste works)
2. file uploads after first post fail.
the sidebar issues appear to be gone for me now and i’m not getting lockups at all.
i really like the docked composer tho, and love that i can use it and resize it while the bot is doing it’s thing too. i went to use the bot this afternoon on another instance i have that doesn’t have it yet and i immediately looked for it and realized i missed it. excellent work Keegan / ai-team 👏
i think my biggest complaint is that i don’t like having to shift + enter to go to next line. i still keep hitting enter quite a lot and having to hit pause. 😬 🤦🏻♀️ the behavior change from regular composer still feels inconsistent. (fwiw it gets me on chat-gpt every time too 😛)
---
### Author:  [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [May 4, 2026, 8:57am UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/9 "2026-05-04T08:57:33Z")
after i did a rebuild today, the quoting is fixed! 😃
only remaining bug i have is not being able to upload after the first post, but i have only been using in desktop mode this weekend.
---
### Author:  [@keegan](https://meta.discourse.org/u/keegan)
#### Post date: [May 4, 2026, 6:11pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/10 "2026-05-04T18:11:21Z")
Thanks Lilly!
I’ve gated the Docked Composer behind an upcoming changes:
>
>
> Previously, the docked chat-style composer for AI bot PMs was always enabled wit…h no way for admins to disable it while the feature is still being refined.
>
> This change adds an \`ai\_bot\_enable\_docked\_composer\` upcoming change flag at alpha status, allowing admins to opt in via the upcoming changes page. When disabled (the default), AI bot PMs fall back to the standard floating composer.
>
> \
as we work through polishing things up more.
> [@Lilly](#):
>
> i think my biggest complaint is that i don’t like having to shift + enter to go to next line. i still keep hitting enter quite a lot and having to hit pause. 😬 🤦🏻♀️ the behavior change from regular composer still feels inconsistent. (fwiw it gets me on chat-gpt every time too 😛)
This has gotten me once or twice. I want to let it sit for a while to see if it’s just something that needs to be gotten used to, but will revisit if it seems to be more frequent of an issue.
> [@Lilly](#):
>
> only remaining bug i have is not being able to upload after the first post, but i have only been using in desktop mode this weekend.
I’ve also pushed a fix for the uploads bug:
>
>
> Previously, uploads in the AI bot docked composer were completely
> non-functional… due to two issues: a Glimmer modifier ordering race
> condition where the file input's \`didInsert\` fired before the parent
> container's \`didInsert\` (so \`UppyUpload\` was never bound to the file
> input), and the submit service rejected upload-only submissions because
> it early-returned on empty \`raw\` before considering attached uploads.
>
> This change fixes the initialization order by calling
> \`uppyUpload.setup()\` in \`setupContainer\` when the file input is already
> available, restructures the submit validation to allow upload-only posts
> and skip the min-length check when uploads are present, and adds
> vertical padding to the uploads container for better visual spacing.
>
> \![Screenshot 2026-05-04 at 10 14 43]()
src="https://github.com/user-attachments/assets/7a0b8e38-f29e-40f7-bac7-361ab549474c"
> /\>
Please let me know how that goes! Thanks so much for your testing and feedback 🙂
---
### Author:  [@keegan](https://meta.discourse.org/u/keegan)
#### Post date: [May 9, 2026, 3:00pm UTC](https://meta.discourse.org/t/new-ai-docked-composer/401961/12 "2026-05-09T15:00:32Z")
This topic was automatically closed after 3 days. New replies are no longer allowed.