Problem
Built-in integration setup flows are optimized for interactive terminals. Coding agents cannot reliably answer branching prompts, and replaying a setup command is unsafe once an earlier choice has mutated external state.
Proposed direction
Use the existing keyed Asker abstraction for every semantic setup decision, separate decision collection from mutation in complex integrations, and let headless callers provide answers by stable key. Shared one-time prerequisites such as Vercel project linking should be completed separately in headless mode rather than unexpectedly opening an interactive flow.
Interactive CLI and TUI behavior should remain unchanged, including specialized controls such as editable selects.
This issue tracks migrating the built-in integration setup flows and defining the eventual structured CLI/setup-command contract used by eve add and coding agents.
Problem
Built-in integration setup flows are optimized for interactive terminals. Coding agents cannot reliably answer branching prompts, and replaying a setup command is unsafe once an earlier choice has mutated external state.
Proposed direction
Use the existing keyed
Askerabstraction for every semantic setup decision, separate decision collection from mutation in complex integrations, and let headless callers provide answers by stable key. Shared one-time prerequisites such as Vercel project linking should be completed separately in headless mode rather than unexpectedly opening an interactive flow.Interactive CLI and TUI behavior should remain unchanged, including specialized controls such as editable selects.
This issue tracks migrating the built-in integration setup flows and defining the eventual structured CLI/setup-command contract used by
eve addand coding agents.