Skip to content

fix(cursor): count UpdateCurrentStep as a non-action in session scans - #13

Merged
kashyap-techsuite merged 1 commit into
mainfrom
fix/cursor-update-current-step
Oct 14, 2026
Merged

kashyap-techsuite merged 1 commit into
mainfrom
fix/cursor-update-current-step

Conversation

@kashyap-techsuite

Copy link
Copy Markdown
Contributor

Cursor 3.21.16's UpdateCurrentStep (a UI progress step) is now a non-action in session scans.

Cursor 3.21.16 session files record UpdateCurrentStep, a progress step shown in the UI with
current_step, completed_subtitle and final_summary inputs and no side effects. The session
reader reported it as an unrecognized tool. It is now in CURSOR_NOT_ACTIONS.

The committed session fixture gains two UpdateCurrentStep records in Cursor's shape, and the
on-disk and built-bundle scans expect them as non-actions. Regenerates guard-scan.mjs.

Co-Authored-By: Claude <noreply@anthropic.com>
@kashyap-techsuite
kashyap-techsuite force-pushed the fix/cursor-update-current-step branch from c2dece6 to 1f3b670 Compare October 14, 2026 06:32
@kashyap-techsuite
kashyap-techsuite merged commit 7a3e718 into main Oct 14, 2026
3 checks passed
@agenttrail-public-release

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 0.4.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants