Skip to content

fix(chat-swarm-runtime): use native ChatGPT composer editing - #181

Merged
James3014 merged 1 commit into
mainfrom
issue-117-wave3-composer-repair
Sep 16, 2026
Merged

James3014 merged 1 commit into
mainfrom
issue-117-wave3-composer-repair

Conversation

@James3014

Copy link
Copy Markdown
Owner

Fixes the native Wave 3 blocker from Issue #117. On the exact installed macOS build, assigning contenteditable.textContent plus a synthetic InputEvent visibly changed the DOM but did not enter ChatGPT's real ProseMirror/React composer state, so no send button appeared and runtime_ensure(3) stalled waiting for a conversation URL.

The repair keeps the existing transport and lifecycle unchanged. For the contenteditable composer it selects the current draft and uses the browser-native insertText editing path that was live-proven to create an enabled ChatGPT send button; failure to acquire a selection or insert text fails closed. The textarea fallback, exact-conversation guard, authenticated peer authority, no-blind-resend rule, and no transport fallback remain unchanged.

Candidate 93d0cf6068feb91d23e933b99a6e8a4e8ebb3d93 is based directly on main@03841ac7ab8abda1b54b9235f2fffe9d18404047 and changes only src/chat-swarm-runtime.ts and src/chat-swarm-runtime.test.ts. Local git diff --check passes; exact-head CI is required before merge.

@James3014
James3014 merged commit 0890f77 into main Sep 16, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant