claude-ide-bridge 2.23.2 → 2.23.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "claude-ide-bridge",
|
|
3
|
-
"version": "2.23.
|
|
3
|
+
"version": "2.23.4",
|
|
4
4
|
"description": "Standalone MCP bridge for Claude Code IDE integration with any editor — 136+ tools for LSP, debugging, terminals, Git, GitHub, and more",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -1,17 +1,19 @@
|
|
|
1
1
|
## Claude IDE Bridge
|
|
2
2
|
|
|
3
3
|
@import .claude/rules/bridge-tools.md
|
|
4
|
-
|
|
5
4
|
> **BRIDGE TOOL ENFORCEMENT — mandatory when bridge is connected**
|
|
6
|
-
> Do NOT
|
|
5
|
+
> Do NOT use native Claude Code tools or shell commands for workspace operations:
|
|
6
|
+
> - File reading: `getBufferContent` (not `Read` tool)
|
|
7
|
+
> - File editing: `editText` or `searchAndReplace` (not `Edit`/`Write` tools)
|
|
8
|
+
> - File search: `searchWorkspace` / `findFiles` (not `Grep`/`Glob` tools)
|
|
7
9
|
> - Testing: `runTests` (not `npm test` / `npx vitest`)
|
|
8
10
|
> - Diagnostics: `getDiagnostics` (not `tsc --noEmit` / `npm run lint`)
|
|
9
11
|
> - Git: `gitCommit`, `gitAdd`, `gitPush` (not `git commit` etc.)
|
|
10
|
-
> -
|
|
11
|
-
>
|
|
12
|
+
> - Shell commands: `runInTerminal` (not `Bash` tool)
|
|
13
|
+
>
|
|
14
|
+
> **Exceptions:** `Read`/`Edit`/`Write` on files outside the workspace (`~/.claude/`, system paths) have no bridge equivalent.
|
|
12
15
|
>
|
|
13
16
|
> Full substitution table: see `.claude/rules/bridge-tools.md` (loaded above via @import).
|
|
14
|
-
|
|
15
17
|
The bridge is connected via MCP. The session-start hook reports connection status, tool count, and extension state automatically — check that summary before proceeding. If tools appear missing, call `getBridgeStatus` to diagnose.
|
|
16
18
|
|
|
17
19
|
### Bug fix methodology
|
|
@@ -5,9 +5,21 @@
|
|
|
5
5
|
> **These rules are active when the `claude-ide-bridge` MCP server is connected** (green in `/mcp`).
|
|
6
6
|
> If the bridge is not running, fall back to standard shell equivalents.
|
|
7
7
|
|
|
8
|
-
### MANDATORY: Bridge MCP tools replace shell commands
|
|
8
|
+
### MANDATORY: Bridge MCP tools replace shell commands AND native Claude Code tools
|
|
9
9
|
|
|
10
|
-
Do NOT
|
|
10
|
+
Do NOT use native Claude Code tools or shell commands for workspace operations. Call the MCP tool instead.
|
|
11
|
+
|
|
12
|
+
#### File I/O — native Claude Code tools replaced by bridge
|
|
13
|
+
|
|
14
|
+
| ❌ Do NOT use | ✅ Call instead |
|
|
15
|
+
|---|---|
|
|
16
|
+
| `Read` tool on workspace files | `getBufferContent` |
|
|
17
|
+
| `Edit` tool on workspace files | `editText` (line range) or `searchAndReplace` (pattern) |
|
|
18
|
+
| `Write` tool on workspace files | `editText` or `createFile` for new files |
|
|
19
|
+
| `Glob` tool to find files | `findFiles` |
|
|
20
|
+
| `Bash` for build/shell commands | `runInTerminal` |
|
|
21
|
+
|
|
22
|
+
> **Exceptions:** `Read`/`Edit`/`Write` on files **outside** the workspace (`~/.claude/`, system paths, etc.) have no bridge equivalent — native tools are correct there.
|
|
11
23
|
|
|
12
24
|
#### Diagnostics & linting
|
|
13
25
|
|