Use devlanes from an agent sandbox
Use this when an agent’s devlanes commands fail with auto-spawn refused in sandbox: the agent host runs its shell in a sandbox, Codex among them, and devlanes does not start a daemon from there.
Start the daemon outside the sandbox
Section titled “Start the daemon outside the sandbox”On macOS and Linux, run this in your own terminal, not through the agent. It starts the daemon now and at each login, and the agent’s commands then reach it.
$ devlanes daemon installIf the agent’s commands still fail, the sandbox does not let them reach the daemon either. Use the MCP server instead.
Give the agent the MCP server
Section titled “Give the agent the MCP server”The agent host starts the MCP server itself. On Windows, Codex starts it outside its sandbox, so the agent’s devlanes tools reach the daemon where its shell cannot.
$ codex mcp add devlanes -- devlanes mcpSet up a coding agent has the line for each agent host. A server the host starts inside its sandbox fails the same way the shell does.