tauri-agent-tools 0.6.0 → 0.7.1

package/examples/tauri-bridge/tauri.conf.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://schema.tauri.app/config/2",
+  "productName": "tauri-dev-bridge-example",
+  "version": "0.1.0",
+  "identifier": "com.tauri-agent-tools.bridge-example",
+  "build": {
+    "frontendDist": "../frontend-stub"
+  },
+  "app": {
+    "windows": [
+      {
+        "label": "main",
+        "title": "Bridge Example",
+        "width": 800,
+        "height": 600
+      }
+    ],
+    "security": {
+      "csp": null
+    }
+  },
+  "bundle": {
+    "active": false
+  }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tauri-agent-tools",
-  "version": "0.6.0",
+  "version": "0.7.1",
   "description": "Agent-driven inspection toolkit for Tauri desktop apps",
   "type": "module",
   "bin": {
@@ -44,6 +44,8 @@
     "access": "public"
   },
   "dependencies": {
+    "ajv": "^8.20.0",
+    "ajv-formats": "^3.0.1",
     "commander": "^14.0.0",
     "zod": "^3.25.76"
   },

package/rust-bridge/README.md

@@ -16,6 +16,9 @@ rand = "0.8"
 uuid = { version = "1", features = ["v4"] }
 tracing = "0.1"
 tracing-subscriber = "0.3"
+
+[target.'cfg(unix)'.dependencies]
+libc = "0.2"
 ```
 
 ### 2. Copy the bridge module
@@ -84,7 +87,7 @@ tauri-agent-tools eval "document.title"
 3. `tauri-agent-tools` discovers the token file and authenticates via the token
 4. The bridge exposes four endpoints: `POST /eval` (JS evaluation), `POST /logs` (Rust log retrieval), `POST /describe` (bridge metadata), and `GET /version` (unauthenticated health check)
 5. `/eval` accepts an optional `window` field to target specific webview windows (defaults to `"main"`)
-6. The injected JS evaluates the expression, then calls back into Rust via `window.__TAURI__.core.invoke("__dev_bridge_result", { id, value })` to deliver the result
+6. The injected JS evaluates the expression, then calls back into Rust via `window.__TAURI_INTERNALS__.invoke("__dev_bridge_result", { id, value })` to deliver the result, falling back to `window.__TAURI__.core.invoke()` for older/global-enabled apps
 7. The HTTP handler thread waits for the result (up to 5 seconds) and returns it as JSON
 8. `/logs` drains the ring buffer of captured `tracing` events and returns them as JSON
 9. `/describe` returns PID, window labels, and capabilities
@@ -98,6 +101,12 @@ tauri-agent-tools eval "document.title"
 - **Inspection is read-only** — inspection commands only read DOM state
 - **Interaction is debug-only** — interaction commands use eval-based DOM dispatch, sandboxed to the webview
 
+## Troubleshooting
+
+### `Eval timeout: no result callback received`
+
+Re-copy `examples/tauri-bridge/src/dev_bridge.rs` from the latest package. Current bridge code uses Tauri 2's always-present `window.__TAURI_INTERNALS__.invoke()` callback path and does **not** require `app.withGlobalTauri: true`. Older copied bridge files used `window.__TAURI__.core.invoke()` and can time out in apps that keep Tauri's global API disabled.
+
 ## Agent-Assisted Setup
 
 If you're using an AI coding agent (Claude Code, Codex, Cursor, etc.), the `tauri-bridge-setup` skill can guide automated setup. See `.agents/skills/tauri-bridge-setup/SKILL.md` or run: