3f6cb88b5e
The default capability only granted read_file/write_file/mkdir/remove/watch, but the app also calls exists(), readTextFile(), create(), and open() from @tauri-apps/plugin-fs. Each fs-plugin command requires its own explicit permission identifier in Tauri v2 — these were never added. The most visible symptom: EditorView's automation startup calls discoveryFileExists()/readDiscoveryToken() (spawn.ts) to reuse an already- running MCP server. With allow-exists and allow-read-text-file missing, both calls silently fail (the fs-plugin IPC rejection is caught and treated as "file not found"), so the app always falls through to spawning a redundant MCP server process and registers with a freshly generated auth token instead of the real one — which the already-running server then rejects, leaving automation permanently disconnected from any already-running MCP server. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| generated | ||
| icons | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Info.plist | ||
| tauri.conf.json | ||
| tauri.native-test.conf.json | ||
| updater.key.pub | ||