Automation architecture
PhotoCraft exposes the same engine through several transports:
photocraft-cli commands/run/batch
|
MCP stdio ---+--> photocraft-automation::Headless --> engine Session
MCP bridge --> BridgeClient --> 127.0.0.1 control server --> UI ControlRequest
JSON-lines stdio/TCP --> rpc::respond --> Headless::handle --> engine Session
Headless file operations are implemented in crates/automation/src/files.rs; RPC dispatch is in crates/automation/src/rpc.rs; MCP tools are registered in crates/automation/src/server.rs; and the live client is in crates/automation/src/bridge.rs. The desktop TCP listener is the framework's control server (craft::automation::server), started by --control or by the agent link (craft::automation::agents::AgentLink).
The control and headless TCP listeners are restricted to loopback addresses. Stdio MCP avoids a listening network socket, but the MCP process still acts with the filesystem permissions of the user who launched it.
Loopback is not authentication. TCP transports require a bearer token and enforce request-byte,
batch-step, and active-connection limits. Remote file methods use an AuthorizedWorkspace with
independent read and write directory capabilities; paths are relative to a configured root and
fail closed when the applicable root is absent. General per-method scopes, client identity,
encryption, and operation budgets are not implemented. See the
Automation security model and
Automation security before exposing or extending these
surfaces.