[austinintelligence]

What changed

After an action, present.rs after_action polls the helper's screen generation (the cheap status query) every 40 ms and reads rows only when the generation moves. It replaces the 3 × 500 ms sleeps while a screen is empty or "Loading", keeping the same 1.5 s overall cap. A tap that left the generation unchanged now waits up to 600 ms for a late change before reporting.

Why

Fixed sleeps made every late-loading screen cost a full 500 ms step. Polling reports the screen as soon as it is ready, which aims at the 1.3.0 tap p50/p95 gate (600/1,500 ms) and at no misses on the three late-loading Settings tasks.

Tests in computer/src/agent_tests.rs:

• a_loading_screen_is_reported_when_it_finishes_not_after_a_fixed_sleep: a screen that finishes loading 120 ms after it is first read is reported in 120–450 ms. With a 500 ms poll it fails.
• a_tap_whose_change_lands_late_is_reported_as_changed: a tap whose change lands at 400 ms is reported as changed.

Known limits

• An action that changes nothing now costs up to 600 ms more (the specified late-change wait). The helper's own settle has already waited before that.
• The helper counts TYPE_VIEW_CLICKED as a change, so on a device a real tap usually moves the generation at once and the 600 ms wait rarely runs. The late-change test models a tap that does not move the generation. Whether it pays off needs an emulator run.

Safety and compatibility

• No device-specific serials, tokens, private paths, media, or signing material are included.
• No new way for an agent to run a shell, adb, or page JavaScript; command forms are unchanged.
• Destructive/privacy-sensitive behavior has explicit confirmation coverage. (Not touched.)
• Temporary files, processes, emulators, and device state have cleanup coverage. (Not touched.)

Verification

• cargo fmt --all -- --check
• cargo clippy --workspace --all-targets --all-features -- -D warnings
• cargo test --workspace --all-targets
• cargo xtask check and cargo xtask docs
• npm test and npm run lint (not run)

Gradle and device/emulator checks were not run: this container has no Android SDK and no device. The p50/p95 effect still needs an emulator run.

Release impact

• No breaking change.
• Breaking change documented in the changelog and migration guidance.

Base is claude/friendly-dirac-embe85 (A-01, PR #55); retarget to main once it merges.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VBuuDWN89yt1W59QT8aHLo

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7451af96-2a25-4366-9c4e-688818164823

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}