Feature guide · subagents

Give every helper its own namespace.

A subagent lane is a persisted project/agent record connected to one generated headless-desktop prefix.

Behavior

Enter a project, agent, and room count in Workspaces. Electron calls create_headless_desktops, then stores the prefix, count, creation time, and status so a later agent can recognize the lane.

Configuration

Lane records live in Electron user data and travel through settings export. The underlying MCP desktop list remains available to agents that do not use the GUI.

Failure modes

Empty names are rejected locally; duplicate names and server failures are returned factually and do not create a ready record.

Security

Lane metadata coordinates work; it does not sandbox commands. Each room retains the server user's privileges, and the trusted-LAN port must stay private.

Verification