Problem
eve dev is designed for an interactive terminal session. Agents, scripts, and continuous integration jobs need a supported way to invoke an eve agent without a TTY and consume a machine-readable result.
Automating the current terminal interface is brittle. Its prompts, control sequences, and human-oriented output do not provide a stable contract for task execution.
Proposed solution
Add a non-interactive task mode to eve dev. One possible shape is:
eve dev --json https://agent.example.com
The mode should:
- run without interactive prompts or terminal control sequences
- accept the target and task through automation-friendly inputs
- emit structured output that callers can parse
- return exit codes that distinguish success from failure
- preserve the CLI's existing authentication and session setup
The exact command syntax, task input method, event schema, and final result format remain open.
Expected behavior
An agent or script can invoke eve dev, submit one task, parse the response, and determine whether the task succeeded without emulating a terminal session.
Current behavior
eve dev starts an interactive experience intended for a person at a terminal. There is no documented non-interactive mode with a machine-readable output contract.
Alternatives considered
Callers can automate the terminal interface or call eve's HTTP endpoints directly. Terminal automation depends on presentation details, while direct HTTP calls require each caller to reproduce CLI behavior such as authentication and session setup.
Problem
eve devis designed for an interactive terminal session. Agents, scripts, and continuous integration jobs need a supported way to invoke an eve agent without a TTY and consume a machine-readable result.Automating the current terminal interface is brittle. Its prompts, control sequences, and human-oriented output do not provide a stable contract for task execution.
Proposed solution
Add a non-interactive task mode to
eve dev. One possible shape is:The mode should:
The exact command syntax, task input method, event schema, and final result format remain open.
Expected behavior
An agent or script can invoke
eve dev, submit one task, parse the response, and determine whether the task succeeded without emulating a terminal session.Current behavior
eve devstarts an interactive experience intended for a person at a terminal. There is no documented non-interactive mode with a machine-readable output contract.Alternatives considered
Callers can automate the terminal interface or call eve's HTTP endpoints directly. Terminal automation depends on presentation details, while direct HTTP calls require each caller to reproduce CLI behavior such as authentication and session setup.