Repository navigation
Lower tree-sitter parse limits to cut CLI memory - #1557
vincenzosco wants to merge 5 commits into
Conversation
The CLI parses the whole project with tree-sitter on every run, which pushed client RAM toward 2GB. Lower the default file count, per-file size and total byte budget so typical projects stay well under 500MB. The CODEBUFF_MAX_PARSE_* env vars still override these defaults.
When antivirus or ASR blocks the bundled bash.exe, spawn fails with EPERM as an async error event, so the command never ran. Retry the same command with the next installed bash, keeping one set of stdout/stderr streams.
Muse Spark 1.3 now requires a plan again, matching the README (CodebuffAI#1525). The ripgrep error no longer prints "undefined" when the bundled binary is missing (CodebuffAI#1493). 🤖 Generated with Codebuff Co-Authored-By: Codebuff <noreply@codebuff.com>
Ctrl+Z fell through every rule in resolveChatKeyboardAction and ended in the final "none" branch, so nothing in the composer handled it. Handle it explicitly as a no-op so it cannot reach any other handler, and cover it with a test next to the Ctrl+Q tests.
Absorb Ctrl+Z in the chat composer
|
The title and description only describe lowering the tree-sitter parse defaults in More importantly, the diff is nowhere close to matching the stated scope. It also includes:
As submitted, a maintainer cannot review or port this as 'lower tree-sitter parse limits.' Please split this into separate PRs: one for the parse limits (with reasoning/benchmarks), and separate ones for the model catalog change, the keyboard handling, and the Windows bash fallback — each with its own description and tests. |
The CLI parses the whole project with tree-sitter on every run, which pushed client RAM toward 2GB. Lower the default file count, per-file size and total byte budget so typical projects stay well under 500MB. The CODEBUFF_MAX_PARSE_* env vars still override these defaults.