fix(cua-driver)(#1651): install.ps1 updates current shell's PATH for immediate cua-driver resolution

[f-trycua]

Summary

After `irm install.ps1 | iex`, the user's next `cua-driver --version` fails with "not recognized" because PowerShell's `$env:Path` was cached at process start and doesn't see the User PATH registry update. install.ps1 runs in the caller's shell via `iex`, so it CAN mutate `$env:Path` directly. This PR makes `Add-UserPathEntry` do that too.

Fix

Two-line change in `Add-UserPathEntry`:
```powershell
if (-not (($env:Path -split ';') -contains $dir)) {
$env:Path = "$dir;$env:Path"
}
```

Plus hint-message update: "resolves immediately in THIS shell and in any new shell."

Verification

Before:
```
PS> irm install.ps1 | iex
... cua-driver-rs 0.2.16 installed.
PS> cua-driver --version
cua-driver : The term 'cua-driver' is not recognized ...
```

After (v0.2.17):
```
PS> irm install.ps1 | iex
... cua-driver-rs 0.2.17 installed.
PS> cua-driver --version
cua-driver 0.2.17
```

Closes #1651.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes
  • The installer now updates your current shell session's PATH immediately after installation, allowing you to use cua-driver without restarting your terminal.
  • Updated installer messaging to clarify that cua-driver is available immediately in the current session.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Ignored	Preview	May 21, 2026 8:58pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 85a2366d-88e3-433e-97f7-2f180f3f383a

📥 Commits

Reviewing files that changed from the base of the PR and between 4797fe0 and 11772b6.

📒 Files selected for processing (1)

• libs/cua-driver/scripts/install.ps1

---

📝 Walkthrough

Walkthrough

The installer updates the current PowerShell session's $env:Path immediately after adding the install directory to the User PATH, allowing cua-driver to resolve without reopening the shell. Post-install messaging is adjusted to reflect immediate availability.

Changes

Install Session PATH Availability

Layer / File(s)	Summary
In-process PATH update libs/cua-driver/scripts/install.ps1	Add-UserPathEntry now prepends the install bin directory to the caller's current process $env:Path immediately after updating the persistent User PATH, if not already present.
Post-install messaging libs/cua-driver/scripts/install.ps1	Manual PATH instructions and success confirmation messages are updated to indicate cua-driver is available immediately in the current shell rather than only in new shells.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• trycua/cua#1576: Both PRs modify libs/cua-driver/scripts/install.ps1's PATH-update behavior—fix(cua-driver/install.ps1): auto-add bin dir to User PATH #1576 adds/idempotently updates the User PATH (with -NoPathUpdate fallback) and this PR further ensures $env:Path in the current PowerShell session is updated immediately after the User PATH change.

• trycua/cua#1628: Both PRs modify libs/cua-driver/scripts/install.ps1's post-install PATH/hint messaging (e.g., cua-driver resolution guidance for the current session and related text), though only this PR additionally updates $env:Path in the running shell.

Poem

🐰 A PATH that springs to life right here,
No waiting for a shell new-spun!
The rabbit hops through install with cheer—
cua-driver runs when setup's done.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/install-current-shell-path-update

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}