How do I verify Cursor actions with Provely?

Cursor connects to Provely through the MCP server, the CLI, the REST API. The agent does the action. Provely verifies the outcome and signs a receipt. Cursor never holds the verifier credentials.

Which surfaces does Cursor use?

Which guidance files does Cursor read?

Provely ships one Agent Skill for this host, so the agent knows to verify an outcome before it claims done. The renderer writes Cursor rules file from one source. A new agent needs a profile, not core code.

How is a false completion claim blocked?

Guidance asks. A hook and the CI gate enforce. A host with neither still receives the verdict, and a person reads it before the work ships.

How do I connect Cursor?

What else does the profile state?

• Verified 2026-09-12: project rules live in .cursor/rules as .mdc files. The frontmatter holds description, globs and alwaysApply. Source: https://cursor.com/docs/context/rules.
• Verified 2026-09-12: the rules page names .cursorrules nowhere. The earlier note called it legacy. Treat the file as gone, and write .cursor/rules/provely.mdc only.
• Verified 2026-09-12: Cursor reads AGENTS.md in the project root and in a subdirectory, and a nested file wins. This profile writes the .mdc rule, because a rule states when it applies. Source: https://cursor.com/docs/context/rules.
• Verified 2026-09-12: MCP servers live in .cursor/mcp.json or ~/.cursor/mcp.json, under mcpServers. Cursor serves stdio, SSE and streamable HTTP. Source: https://cursor.com/docs/context/mcp.
• Verified 2026-09-12: Cursor 1.7 added hooks. The release note states that a custom script observes, controls and extends the agent loop. Source: https://cursor.com/changelog/1-7.
• Verified 2026-09-12: the hooks page is https://cursor.com/docs/agent/hooks. The earlier notes named https://cursor.com/docs/hooks.
• Verified 2026-09-12: hooks live in .cursor/hooks.json of the project, or in ~/.cursor/hooks.json, under the key hooks with version 1. Source: https://cursor.com/docs/agent/hooks.
• Verified 2026-09-12: the host states 21 hook events, and this profile names all 21 in the order of the page. The earlier list named one. Source: https://cursor.com/docs/agent/hooks.
• Verified 2026-09-12: seven events deny an action: preToolUse, subagentStart, beforeShellExecution, beforeMCPExecution, beforeReadFile, beforeTabFileRead and beforeSubmitPrompt. The 14 other events observe. Source: https://cursor.com/docs/agent/hooks.
• Verified 2026-09-12: beforeShellExecution and beforeMCPExecution fail open by default. failClosed true reverses that. Source: https://cursor.com/docs/agent/hooks.
• Verified 2026-09-12: the stop hook cannot block a turn. It returns followup_message, and Cursor submits that text as the next user message. loop_limit caps the follow-ups, and the default is 5. Source: https://cursor.com/docs/agent/hooks.
• Verified 2026-09-12: sessionStart and sessionEnd do not fire in a cloud agent. A cloud run therefore registers no session. The CI gate covers that run. Source: https://cursor.com/docs/agent/hooks.
• This profile renders one hook: cursor_stop. The 20 other events are documented, and this repository drives none of them. Treat them as documented, and not as observed.
• Register the stop hook with the snippet in .provely/hooks/cursor-hooks.md. Cursor does not merge the file for us, and this profile never overwrites a hooks.json that you already keep.
• beforeMCPExecution and beforeShellExecution deny an action before it runs. Provely verifies an outcome after the action, so this profile ships no such hook.
• Verified 2026-09-12: the Cursor CLI installs the command agent, and the flag -p runs one prompt without a terminal session. Source: https://cursor.com/docs/cli/installation.
• Needs verification: no page states that the Cursor CLI reads .cursor/hooks.json. Check the installed CLI before a pipeline depends on the stop hook.
• The hook sees only operations that called begin. An action that never opened an operation is invisible to it. The scanner and the CI gate cover that case.
• The CI gate covers background and cloud agents. Verdicts land in pull request checks.

Cursor keeps its action credentials, and no surface returns the verifier credentials to it. Read the credential boundary. An operation outlives the session that opened it. Read the API reference.