Teknium 281a439ad4 fix(desktop): guard composer mutations when the composer core isn't bound (#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.		2026-06-23 23:47:45 -07:00
..
bootstrap-installer	fix(desktop/windows): stop in-app update from cascading into a backend restart loop (#50381)	2026-06-21 13:10:32 -07:00
desktop	fix(desktop): guard composer mutations when the composer core isn't bound (#51728)	2026-06-23 23:47:45 -07:00
shared	fix(desktop): move tsconfig to es2023	2026-06-15 12:07:17 -04:00