feat: Auto Claude's MCP Contribution, RDR let Claude and Auto-Claude finish your tasks in your absence, use MCP to create batches of tasks #1855
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,27 @@ | ||||||||||||||||||||||||||||
| @echo off | ||||||||||||||||||||||||||||
| REM ============================================================ | ||||||||||||||||||||||||||||
| REM Auto-Claude-MCP Launcher with External Watchdog | ||||||||||||||||||||||||||||
| REM ============================================================ | ||||||||||||||||||||||||||||
| REM This launches Auto-Claude via the watchdog process, which | ||||||||||||||||||||||||||||
| REM monitors for crashes and can auto-restart the app. | ||||||||||||||||||||||||||||
| REM | ||||||||||||||||||||||||||||
| REM SETUP: Replace the path below with your actual install path. | ||||||||||||||||||||||||||||
| REM Example: C:\Users\YourName\source\repos\Auto-Claude-MCP | ||||||||||||||||||||||||||||
| REM ============================================================ | ||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| set AUTO_CLAUDE_DIR=C:\Users\USER\path\to\Auto-Claude-MCP | ||||||||||||||||||||||||||||
|
Contributor
There was a problem hiding this comment. Unquoted Trailing whitespace or special characters in the value can cause subtle bugs. Use the quoted form: Proposed fix-set AUTO_CLAUDE_DIR=C:\Users\USER\path\to\Auto-Claude-MCP
+set "AUTO_CLAUDE_DIR=C:\Users\USER\path\to\Auto-Claude-MCP"📝 Committable suggestion
Suggested change
🧰 Tools🪛 Blinter (1.0.112)[warning] 12-12: Errorlevel handling difference between .bat/.cmd. Explanation: Commands like APPEND, DPATH, FTYPE, SET, PATH, ASSOC handle errorlevel differently in .bat vs .cmd files. Recommendation: Use .cmd extension for consistent errorlevel behavior with these commands. Context: Command 'set' handles errorlevel differently in .bat vs .cmd files (W028) [error] 12-12: Unsafe SET command usage. Explanation: SET commands without proper validation or quoting can cause security issues. Recommendation: Always quote SET values and validate input: SET "var=safe value". Context: SET command value should be quoted for safety (SEC002) 🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| cd /d "%AUTO_CLAUDE_DIR%\apps\frontend" | ||||||||||||||||||||||||||||
|
Contributor
There was a problem hiding this comment.
If 🛡️ Proposed fix-cd /d "%AUTO_CLAUDE_DIR%\apps\frontend"
+cd /d "%AUTO_CLAUDE_DIR%\apps\frontend" || (echo ERROR: Directory not found: %AUTO_CLAUDE_DIR%\apps\frontend && exit /b 1)📝 Committable suggestion
Suggested change
🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||
| echo Starting Auto-Claude with crash recovery watchdog... | ||||||||||||||||||||||||||||
| echo. | ||||||||||||||||||||||||||||
| call npx tsx src/main/watchdog/launcher.ts ..\..\node_modules\.bin\electron out/main/index.js | ||||||||||||||||||||||||||||
| set EXIT_CODE=%errorlevel% | ||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||
| REM Only pause on error/crash (non-zero exit code) | ||||||||||||||||||||||||||||
| REM Normal exit (code 0) = user closed the app = close terminal immediately | ||||||||||||||||||||||||||||
| if %EXIT_CODE% neq 0 ( | ||||||||||||||||||||||||||||
| echo. | ||||||||||||||||||||||||||||
| echo Launcher exited with code: %EXIT_CODE% | ||||||||||||||||||||||||||||
| echo Press any key to close... | ||||||||||||||||||||||||||||
| pause >nul | ||||||||||||||||||||||||||||
| ) | ||||||||||||||||||||||||||||
|
Comment on lines
+1
to
+27
Contributor
There was a problem hiding this comment. Batch file uses Unix (LF) line endings — can cause parsing failures on Windows. The Windows batch parser has known issues with LF-only line endings, including label parsing failures at 512-byte boundaries. This file must use CRLF line endings. Configure 🧰 Tools🪛 Blinter (1.0.112)[error] 1-1: Unix line endings detected. Explanation: Batch file uses Unix line endings (LF-only) which can cause GOTO/CALL label parsing failures and script malfunction due to Windows batch parser 512-byte boundary bugs. Recommendation: Convert file to Windows line endings (CRLF). Use tools like dos2unix, notepad++, or configure git with 'git config core.autocrlf true'. Context: File uses Unix line endings (LF-only) - 27 LF sequences found (E018) [warning] 26-26: Missing exit code. Explanation: Script doesn't set appropriate exit codes to indicate success or failure. Recommendation: Add EXIT /b 0 for success or EXIT /b 1 for errors at script end. Context: Script can reach end of file without explicit EXIT statement (W001) [warning] 12-12: Errorlevel handling difference between .bat/.cmd. Explanation: Commands like APPEND, DPATH, FTYPE, SET, PATH, ASSOC handle errorlevel differently in .bat vs .cmd files. Recommendation: Use .cmd extension for consistent errorlevel behavior with these commands. Context: Command 'set' handles errorlevel differently in .bat vs .cmd files (W028) [warning] 17-17: Command execution may be ambiguous. Explanation: Multiple files with same name but different extensions may cause ambiguous execution. Recommendation: Use explicit file extensions in CALL statements and verify PATHEXT order. Context: CALL 'npx' without extension may be ambiguous with PATHEXT (W033) [error] 12-12: Unsafe SET command usage. Explanation: SET commands without proper validation or quoting can cause security issues. Recommendation: Always quote SET values and validate input: SET "var=safe value". Context: SET command value should be quoted for safety (SEC002) 🤖 Prompt for AI Agents
Comment on lines
+22
to
+27
Contributor
There was a problem hiding this comment. Missing explicit exit code on the success path. When Proposed fix if %EXIT_CODE% neq 0 (
echo.
echo Launcher exited with code: %EXIT_CODE%
echo Press any key to close...
pause >nul
)
+exit /b %EXIT_CODE%📝 Committable suggestion
Suggested change
🧰 Tools🪛 Blinter (1.0.112)[warning] 26-26: Missing exit code. Explanation: Script doesn't set appropriate exit codes to indicate success or failure. Recommendation: Add EXIT /b 0 for success or EXIT /b 1 for errors at script end. Context: Script can reach end of file without explicit EXIT statement (W001) 🤖 Prompt for AI Agents |
||||||||||||||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Blocking semver-major suppresses major-version security releases.
version-update:semver-majorignore rules prevent Dependabot from opening PRs for any major bump, including those that carry CVE fixes. If an upstream package ships a breaking-change major release that is also a security patch (e.g., moving from a vulnerable 1.x to a patched 2.0), Dependabot will silently skip it. Consider pairing this with GitHub's Dependabot security-updates feature (which bypassesignorerules for known advisories) or periodically auditing suppressed updates.Also applies to: 30-33
🤖 Prompt for AI Agents