feat(desktop): pop the composer out into a draggable floating window - #49488
Merged
Conversation
Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release.
Contributor
🔎 Lint report:
|
…ip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
Ari4ka
approved these changes
Jun 20, 2026
This was referenced Jun 21, 2026
teknium1
added a commit
that referenced
this pull request
Jun 24, 2026
…ound (#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
pai-scaffolde
pushed a commit
to pai-scaffolde/hermes-agent
that referenced
this pull request
Jun 28, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
1 task
waefrebeorn
pushed a commit
to waefrebeorn/slermes
that referenced
this pull request
Jul 2, 2026
…ousResearch#49488) * feat(desktop): pop the composer out into a draggable floating window Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release. * fix(desktop): keep floating composer radius consistent with docked * fix(desktop): composer popout polish — peel-off placement, panels, chip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
waefrebeorn
pushed a commit
to waefrebeorn/slermes
that referenced
this pull request
Jul 2, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
habarmc1223-sudo
pushed a commit
to habarmc1223-sudo/hermes-agent-fluxmem
that referenced
this pull request
Jul 8, 2026
…ousResearch#49488) * feat(desktop): pop the composer out into a draggable floating window Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release. * fix(desktop): keep floating composer radius consistent with docked * fix(desktop): composer popout polish — peel-off placement, panels, chip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
habarmc1223-sudo
pushed a commit
to habarmc1223-sudo/hermes-agent-fluxmem
that referenced
this pull request
Jul 8, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
santhreal
pushed a commit
to santhreal/hermes-agent
that referenced
this pull request
Jul 13, 2026
…ousResearch#49488) * feat(desktop): pop the composer out into a draggable floating window Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release. * fix(desktop): keep floating composer radius consistent with docked * fix(desktop): composer popout polish — peel-off placement, panels, chip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
santhreal
pushed a commit
to santhreal/hermes-agent
that referenced
this pull request
Jul 13, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
…ousResearch#49488) * feat(desktop): pop the composer out into a draggable floating window Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release. * fix(desktop): keep floating composer radius consistent with docked * fix(desktop): composer popout polish — peel-off placement, panels, chip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
Gravezzz
pushed a commit
to Gravezzz/hermes-agent
that referenced
this pull request
Jul 21, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
leewenjie
pushed a commit
to leewenjie/hermes-agent
that referenced
this pull request
Aug 7, 2026
…ousResearch#49488) * feat(desktop): pop the composer out into a draggable floating window Gesture-driven: drag the docked composer up to peel it out, drag it back to the bottom-center dock zone (radial glow ramps with proximity) to redock, and double-click the grab area to toggle. Floating composer is compact, grows upward as it wraps, and can be moved by its 5px transparent grab platform (diagonal hatch on hover). Position + popped state persist; secondary windows always start docked. rAF-coalesced drag, persisted only on release. * fix(desktop): keep floating composer radius consistent with docked * fix(desktop): composer popout polish — peel-off placement, panels, chip editing - Peel-off undock drops the floating composer under the cursor (centered horizontally, preserving the vertical grab offset) instead of snapping to the docked corner. - Unify the / · @ · ? completion drawer and the attach (+) menu onto one shared glassy panel primitive (composerPanelCard): smallest theme font, hairline border, nous shadow; floats off the composer, inset from the left. - Directive chips: Backspace removes the chip + its auto-inserted trailing space atomically (no orphaned space), and a phantom trailing block left by contenteditable no longer falsely expands the composer to two rows. - Model picker: scroll area capped at max(150px, 30dvh); footer rows aligned (matching icons, dropped a redundant margin). - Composer focus shifts the border ~15% toward foreground (no fill change); input is cursor-text; trimmed control icon/button sizes.
leewenjie
pushed a commit
to leewenjie/hermes-agent
that referenced
this pull request
Aug 7, 2026
…ound (NousResearch#51728) The desktop composer threw an uncaught "Composer is not available" at startup and the input went unresponsive (NousResearch#49903). assistant-ui's composer mutators (setText/send/…) throw when the thread's composer core isn't bound yet; the read path is null-safe but the writes are not. ChatBar pushes draft text via aui.composer().setText() from mount-time effects (draft restore, clearDraft, external inserts), and the v0.17.0 popout refactor (NousResearch#49488) widened the unbound window by moving the composer out of the contain wrapper into a sibling of the thread — so the throw surfaced as an uncaught error that wedged the input. Wrap every composer mutation in a setComposerText helper that swallows the unbound-core throw. The contentEditable DOM + draftRef already hold the text and the draft-editor sync re-applies it once the core attaches, so the draft is never lost — only the premature state push is skipped.
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.
Summary
Lets you pop the desktop composer out of its docked slot into a compact, draggable floating window — entirely gesture-driven, no chrome/buttons.
cursor-grab, diagonal/////hatch on hover). The docked composer gets the same transparent grab margin (width compensated so the surface doesn't shift).cursor-text.Implementation notes
store/composer-popout.ts(persisted atoms + clamped position) andcomposer/hooks/use-popout-drag.ts(the gesture state machine).Test plan
+aligns to first line; model pill is chevron-only.