Yaha Desktop + GIMP
Edit images in local GIMP 3 from Yaha Chat. The gateway never dials the companion.
Yaha Chat can edit images in local GIMP 3 through Yaha Desktop, a loopback companion on your machine.
The gateway never dials GIMP or the companion. Marketplace transport local_desktop is a recipe only.
Yaha Cloud / Console --HTTPS--> yaha-gateway
│ tool_calls (gimp_*)
▼
Yaha Console --Bearer localhost HTTP /v1--> yaha-desktop
│ authenticated JSON-RPC
▼
GIMP 3 plugin → GIMPInstall
- Install GIMP 3.
- Install the Yaha Desktop Windows app (or
yaha-desktop serve+yaha-desktop install-gimp-plugin). - Console → Marketplace → Yaha GIMP → Add to my account.
- Click Connect this device once (GIMP is not health-checked in the background).
- Start GIMP 3 and run Filters → Development → Yaha Desktop Bridge if image tools stay disconnected.
- Ask Yaha Chat — in the Windows app or the web Console on the same PC — to resize, crop, snapshot, or export.
v1 client is Yaha Chat. The cloud never dials GIMP.
Security
Loopback peer → origin allowlist → PNA → Bearer session → schema → server tool registry → path jail → execute.
PKCE + CLI approve blocks silent pairing from an untrusted origin. It is not a defense against a compromised local machine. Companion restart revokes every session.
Data that may leave the machine
Bounded PNG snapshots Chat requested (1024 px long edge, 1.5 MiB), plus image_id, revision, width, height, and basename. Source files, full pixels, and absolute paths stay local.
Failure paths
| Condition | Result |
|---|---|
| Invalid pairing | Rejected |
| Expired session | 401 — re-pair |
| GIMP closed | DEGRADED / NOT_CONNECTED |
Stale image_id | IMAGE_NOT_FOUND |
| Revision mismatch | REVISION_CONFLICT |
| Export exists | FILE_EXISTS |
| Path outside roots | PERMISSION_DENIED |
local_desktop on the gateway | Never dials |
See also
- MCP Tool Bridge (remote MCP; not this companion)
- Integrations overview