Skip to content

fix(twitter): use the dedicated composer for replies#860

Merged
jackwener merged 1 commit intojackwener:mainfrom
hiSandog:fix/twitter-reply-composer-20260407171435-d85681e
Apr 7, 2026
Merged

fix(twitter): use the dedicated composer for replies#860
jackwener merged 1 commit intojackwener:mainfrom
hiSandog:fix/twitter-reply-composer-20260407171435-d85681e

Conversation

@hiSandog
Copy link
Copy Markdown
Contributor

@hiSandog hiSandog commented Apr 7, 2026

Summary

  • use the dedicated X reply composer for text-only replies as well as image replies
  • wait for the actual reply textarea instead of the broader primaryColumn container
  • update the adapter test to cover the composer-based text-only flow

Testing

  • npx vitest run --project adapter clis/twitter/reply.test.ts

Fixes #848.

@jackwener jackwener merged commit 4ea8f7e into jackwener:main Apr 7, 2026
jackwener added a commit that referenced this pull request Apr 7, 2026
…ipeline

1. Rebase on main picks up #860/#862 (all replies use dedicated composer),
   so dry-run no longer regresses the text-reply fix.

2. Switch incident mode metric from pass_count (higher) to
   regression_count (lower). eval-cli.ts now outputs REGRESSIONS=N
   alongside SCORE=X/Y. fix.ts incident mode greps for REGRESSIONS=
   so infra/precondition failures don't pollute the metric.

3. Add pre-flight check in incident mode: detects infra/precondition
   failures and bails early with a clear message instead of entering
   the engine loop.

4. Pass prompt via stdin (not shell-escaped string) in incident mode
   modify callback, matching the convention from main.
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.

twitter reply fails with: 'Could not find the reply text area'

2 participants