From bd4ca72cc349412cb6c6623a43f38d89b35391dc Mon Sep 17 00:00:00 2001 From: recursiveAF Date: Mon, 24 Nov 2025 18:38:52 +0000 Subject: [PATCH 1/3] Update Cursor installation rule with additional guidelines --- docs/remcp/installation/install-cursor.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/remcp/installation/install-cursor.mdx b/docs/remcp/installation/install-cursor.mdx index 9f365d6..be0c653 100644 --- a/docs/remcp/installation/install-cursor.mdx +++ b/docs/remcp/installation/install-cursor.mdx @@ -48,6 +48,7 @@ Use Recurse ML MCP to verify your work while completing tasks. Before making any 1. DON'T skip initialization - always call `init()` before starting work. 2. DON'T forget to call `check()` after completing changes. 3. DON'T ignore bug reports without investigating them first. +4. DON'T finish a task without receiving a complete analysis from REMCP, wait for 30 seconds and retry the check, communicating clearly that you are awaiting the complete analysis. ## MCP Usage @@ -67,6 +68,9 @@ The Recurse ML MCP provides the following tools: 2. **After completing changes**: Call `mcp_recurse_check()` with the project_id returned from init(). 3. **If bugs are found**: Review the bug reports, verify whether they are valid, and fix them. 4. **If analysis is pending**: Wait a moment and call `check()` again until the analysis completes. +5. **When making a code change**: Clearly state that the change is being made as a result of a bug found by REMCP and state what the bug is. + +End of rule: Verify Changes Using Recurse ML MCP ``` From ef472c1e2e7ab7ac8eaabfea56e8b91b238ba93f Mon Sep 17 00:00:00 2001 From: recursiveAF Date: Mon, 24 Nov 2025 19:22:16 +0000 Subject: [PATCH 2/3] Update rule note placement and wording --- docs/remcp/installation/install-cursor.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/remcp/installation/install-cursor.mdx b/docs/remcp/installation/install-cursor.mdx index be0c653..0a212b4 100644 --- a/docs/remcp/installation/install-cursor.mdx +++ b/docs/remcp/installation/install-cursor.mdx @@ -32,6 +32,8 @@ alwaysApply: true description: Use Recurse ML MCP to verify your work. Before making changes, call init() on the project if not already done. Once all changes are done, call check() to get bug reports. --- +> **Note:** Rules in this section are managed by Recurse ML. Any changes made will be overwritten when pulling new rule updates. + # Verify Changes Using Recurse ML MCP Use Recurse ML MCP to verify your work while completing tasks. Before making any changes, call `init()` on the project if not already done. Once all changes are done, call `check()` to get bug reports. @@ -70,7 +72,7 @@ The Recurse ML MCP provides the following tools: 4. **If analysis is pending**: Wait a moment and call `check()` again until the analysis completes. 5. **When making a code change**: Clearly state that the change is being made as a result of a bug found by REMCP and state what the bug is. -End of rule: Verify Changes Using Recurse ML MCP + ``` From 637000346c205c89916e1bd4e65c60cbea5388d8 Mon Sep 17 00:00:00 2001 From: recursiveAF Date: Mon, 24 Nov 2025 19:27:10 +0000 Subject: [PATCH 3/3] Update references from 'Recurse ML MCP' to 'REMCP' --- docs/remcp/installation/install-cursor.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/remcp/installation/install-cursor.mdx b/docs/remcp/installation/install-cursor.mdx index 0a212b4..fa69293 100644 --- a/docs/remcp/installation/install-cursor.mdx +++ b/docs/remcp/installation/install-cursor.mdx @@ -23,20 +23,20 @@ Add the following user rule in your Cursor settings: ```yaml --- -name: Verify Changes Using Recurse ML MCP +name: Verify Changes Using REMCP globs: "**/*.{js,ts,py,rs,go,java,rb,cs,tsx,jsx}" alwaysApply: true -description: Use Recurse ML MCP to verify your work. Before making changes, call init() on the project if not already done. Once all changes are done, call check() to get bug reports. +description: Use REMCP to verify your work. Before making changes, call init() on the project if not already done. Once all changes are done, call check() to get bug reports. --- > **Note:** Rules in this section are managed by Recurse ML. Any changes made will be overwritten when pulling new rule updates. # Verify Changes Using Recurse ML MCP -Use Recurse ML MCP to verify your work while completing tasks. Before making any changes, call `init()` on the project if not already done. Once all changes are done, call `check()` to get bug reports. +Use REMCP to verify your work while completing tasks. Before making any changes, call `init()` on the project if not already done. Once all changes are done, call `check()` to get bug reports. ## Do @@ -54,7 +54,7 @@ Use Recurse ML MCP to verify your work while completing tasks. Before making any ## MCP Usage -The Recurse ML MCP provides the following tools: +The REMCP provides the following tools: - `mcp_recurse_init(repo_path)`: Initialize a codebase for analysis. Sets up the project for continuous analysis by performing health checks, creating a project entry in the database, and starting the background worker (if not already running). @@ -72,7 +72,7 @@ The Recurse ML MCP provides the following tools: 4. **If analysis is pending**: Wait a moment and call `check()` again until the analysis completes. 5. **When making a code change**: Clearly state that the change is being made as a result of a bug found by REMCP and state what the bug is. - + ```