Skip to content

chore(healing): remove EOL AI self-healing integration - #184

Open
yash-atwal wants to merge 2 commits into
mainfrom
chore/remove-eol-selfheal
Open

chore(healing): remove EOL AI self-healing integration#184
yash-atwal wants to merge 2 commits into
mainfrom
chore/remove-eol-selfheal

Conversation

@yash-atwal

Copy link
Copy Markdown
Collaborator

Removes the AI self-healing feature from @wdio/browserstack-service. It relied on @browserstack/ai-sdk-node's healing helpers, which have
been removed upstream, and the integration is end-of-life. Removes src/ai-handler.ts, the public selfHeal option (breaking — see changeset),
healing-only constants/perf-events/instrumentation, the dependency, and the ai-handler tests. Out of scope: the proto/gRPC AISelfHeal* generated types.
Validated: install/lint/build/tsc clean; tests pass (full suite green with --no-file-parallelism).

Removes the AI self-healing feature from the service. It relied on the
@browserstack/ai-sdk-node BrowserstackHealing helpers, which have been removed
upstream, and the integration is end-of-life. Self-heal is therefore removed
rather than maintained.

Removed:
- src/ai-handler.ts (the whole AiHandler: init/setToken/initializeCapabilities,
  firefox extension install, findElement healing wrap, selfHeal/setup entry
  points) and the @browserstack/ai-sdk-node dependency.
- The public `selfHeal` option (BrowserstackOptions / BrowserstackConfig) — see
  the changeset; this is the breaking change.
- Healing-only constants, the AI perf events, isValidCapsForHealing, and the
  healing-instrumentation funnel subsystem (kept fireFunnelTestEvent /
  sendStart / sendFinish). Removed the ai-handler tests and the healing block
  in the funnel-instrumentation tests.

Out of scope (left intact): the proto/gRPC AISelfHeal* generated types.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: d2fc8609-10ab-4887-b8a4-6b52e8fb1d77

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

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.

2 participants