Problem
delega init requires an interactive TTY to select options. This makes it impossible to script or run from CI/CD, agent workflows, or any non-interactive shell.
Use Case
I deploy Delega self-hosted on a Proxmox LXC via SSH. Running npx @delega-dev/cli init --api-url http://192.168.10.193:18890 from a non-interactive context fails because the wizard prompts for input.
Suggestion
Add CLI flags for all wizard choices so init can run fully non-interactive:
delega init --self-hosted --api-url http://192.168.10.193:18890 --agent-name forrestbot --no-interactive
This would cover:
--hosted / --self-hosted (deployment type)--api-url <url> (server URL)--agent-name <name> (first agent name)--no-interactive (skip all prompts, fail if required args missing)--mcp-client <client> (optional, which MCP client config to generate)
Workaround
Currently I disable auth, create agents via the REST API directly (POST /api/agents), then re-enable auth. Works but not ideal.
Problem
delega initrequires an interactive TTY to select options. This makes it impossible to script or run from CI/CD, agent workflows, or any non-interactive shell.Use Case
I deploy Delega self-hosted on a Proxmox LXC via SSH. Running
npx @delega-dev/cli init --api-url http://192.168.10.193:18890from a non-interactive context fails because the wizard prompts for input.Suggestion
Add CLI flags for all wizard choices so init can run fully non-interactive:
This would cover:
--hosted/--self-hosted(deployment type)--api-url <url>(server URL)--agent-name <name>(first agent name)--no-interactive(skip all prompts, fail if required args missing)--mcp-client <client>(optional, which MCP client config to generate)Workaround
Currently I disable auth, create agents via the REST API directly (
POST /api/agents), then re-enable auth. Works but not ideal.