Files
photocraft/packaging/linux
FuroxfufuandClaude Opus 5.5 f84bbb6fa5 AI Integrations: connect MCP clients to the running app without a terminal
Edit › Preferences › AI Integrations › Let AI agents connect (off by
default) starts the loopback control server at runtime, with a fresh
token on every start, and publishes agent-connection.json in the
settings folder. Agent requests go through the automation policy with
the read/write folders chosen in the panel.

`photocraft-cli mcp --live` finds the app from that file before every
tool call, so MCP clients survive app restarts and port changes. While
the app is closed, `whenAppClosed` (or --when-closed) decides: start the
app, serve a headless session with the same folders, or explain what to
do. The panel's Add to Claude Desktop / Claude Code / Cursor buttons and
`photocraft-cli mcp install --client` write the client configuration
(merged, with a backup); Copy Configuration gives the JSON.

`--control`, `mcp --bridge` and headless `mcp` behave as before; with
--control the panel says the launch options manage the connection.

- automation: agent_link (connection file, client install), live
  backend, app_dirs moved here so the app and the CLI agree.
- prefs: connectAgents, readFolder, writeFolder, whenAppClosed;
  controlPort is now read (settings that do nothing 26 -> 25).
- packaging: photocraft-cli inside PhotoCraft.app; AppImage `--cli`.
- 18 new strings translated in all 20 catalogs; docs and book updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 11:34:29 +00:00
..
2026-10-01 10:49:51 -04:00