Rust panic at Claude Desktop Start

[SpeedySH]

thread 'main' panicked at src\fs_service.rs:516:53:
range end index 41 out of range for slice of length 2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
2025-05-29T16:48:53.413Z [filesystem] [info] Message from client: {"jsonrpc":"2.0","method":"notifications/cancelled","params":{"requestId":175,"reason":"Error: MCP error -32001: Request timed out"}}
2025-05-29T16:48:53.417Z [filesystem] [info] Server transport closed
2025-05-29T16:48:53.418Z [filesystem] [info] Client transport closed
2025-05-29T16:48:53.418Z [filesystem] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-05-29T16:48:53.418Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}
2025-05-29T16:48:53.419Z [filesystem] [info] Client transport closed
2025-05-29T16:55:57.953Z [filesystem] [info] Initializing server...
2025-05-29T16:55:57.993Z [filesystem] [error] spawn rust-mcp-filesystem ENOENT {"context":"connection","stack":"Error: spawn rust-mcp-filesystem ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n    at onErrorNT (node:internal/child_process:483:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-05-29T16:55:57.994Z [filesystem] [error] spawn rust-mcp-filesystem ENOENT {"stack":"Error: spawn rust-mcp-filesystem ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n    at onErrorNT (node:internal/child_process:483:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-05-29T16:55:58.031Z [filesystem] [info] Server transport closed
2025-05-29T16:55:58.032Z [filesystem] [info] Client transport closed
2025-05-29T16:55:58.032Z [filesystem] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-05-29T16:55:58.032Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}
2025-05-29T16:57:22.206Z [filesystem] [info] Initializing server...
2025-05-29T16:57:22.245Z [filesystem] [error] spawn rust-mcp-filesystem ENOENT {"context":"connection","stack":"Error: spawn rust-mcp-filesystem ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n    at onErrorNT (node:internal/child_process:483:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-05-29T16:57:22.246Z [filesystem] [error] spawn rust-mcp-filesystem ENOENT {"stack":"Error: spawn rust-mcp-filesystem ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n    at onErrorNT (node:internal/child_process:483:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"}
2025-05-29T16:57:22.293Z [filesystem] [info] Server transport closed
2025-05-29T16:57:22.293Z [filesystem] [info] Client transport closed
2025-05-29T16:57:22.294Z [filesystem] [info] Server transport closed unexpectedly, this is likely due to the process exiting early. If you are developing this MCP server you can add output to stderr (i.e. `console.error('...')` in JavaScript, `print('...', file=sys.stderr)` in python) and it will appear in this log.
2025-05-29T16:57:22.294Z [filesystem] [error] Server disconnected. For troubleshooting guidance, please visit our [debugging documentation](https://modelcontextprotocol.io/docs/tools/debugging) {"context":"connection"}

[hashemix]

Interesting, that is an edge case when LLM requests an invalid/impossible edit operation. Will be fixed in the upcoming version soon. 👍