v1.1.1

DevSpace 1.1.1 lets devspace init run without prompts, so a coding agent, a script, or a fresh machine can set DevSpace up without anyone at the keyboard.

Set up without prompts

init still asks its questions in a terminal. Now each flag answers one of them, --yes takes the defaults for the rest, and without a terminal init uses the defaults too.

devspace init --yes                                                      # subagents
devspace init --public-url https://your-tunnel.example.com --roots ~/work # also serve ChatGPT or Claude

• --providers codex,claude picks the subagents. It defaults to configured providers, else every detected one.
• --public-url sets your tunnel's origin, without /mcp. Setting one is what also serves an MCP host.
• --roots sets the project folders an MCP host may open. It's required with a public URL unless roots are already configured, so an MCP host never gets a guessed root.
• --json prints the result for scripts. It reports where the owner password is stored, never the password itself, so the password stays out of agent transcripts and tool logs.

Bad answers fail before anything is written: unknown providers list the known ones, and a public URL ending in /mcp is rejected. An MCP host can now be set up without any coding agent installed, in prompts and with flags.

Let your agent set itself up

Paste this into Codex, Claude Code, or any agent with a shell, and it installs, configures, and checks DevSpace by itself:

1. curl -fsSL https://devspace.run/install | DEVSPACE_NO_INIT=1 sh
2. devspace init --yes
3. devspace agents skill --install <claude-code|codex|opencode|agents>
   (Cursor: devspace agents skill --install cursor --project)
4. devspace agents targets

The Copy prompt button on devspace.run copies a version that also covers Windows. Your tunnel and approving a host's connection stay with you.

Update

Rerun the installer, or npm install -g @waishnav/devspace.

Full changelog: v1.1.0...v1.1.1