Andrew Barba
4.4 KiB
issue, status, last_updated
| issue | status | last_updated |
|---|---|---|
| TBD | in-progress | 2026-09-16 |
From init to chat
Interactive eve init scaffolds and opens the TUI. Connection readiness replaces the model, channels, integrations, and review interview. /login connects; /model selects models and settings; /add searches and installs one addition immediately.
The public direct-provider surfaces are openai(model?) from eve/models/openai and anthropic(model?) from eve/models/anthropic, alongside chatgpt(model?). Defaults are gpt-5.6-luna-fast and claude-sonnet-5. Source edits recognize eve-owned helpers and reject unsafe custom expressions.
A project's choice wins over discovery. New connections prefer explicit environment credentials, the machine default, then Vercel CLI's current team. Projectless Gateway requests carry the account token and validated x-vercel-ai-gateway-team header. CLI credential rotation remains CLI-owned. eve-owned refresh credentials and keys use just-secrets; rotating access tokens remain in memory behind a credential broker and cross-process refresh lock. Authored files, generated artifacts, and workflow state contain no discovered secrets. Local discovery never supplies deployment credentials.
Menus retain eve's renderer and scrollback with borderless rows, a › marker, bold selection, dim secondary text, filtering, and Enter/Esc navigation. Authorization semantics and required setup remain intact. Connection-ready and first-response telemetry contains timing and state only.
Release acceptance requires projectless Gateway account-token support for the intended audience; this backend capability is feature-gated. The OAuth client ID is isolated and shared with Vercel CLI for its supported device authorization flow. Deterministic tests cover routing and failure behavior. Local acceptance on 2026-09-14 also validated the existing CLI account/team and streamed a gpt-5.6-luna-fast response without a linked project. CI fixture evals remain the end-to-end gate.
Vercel CLI installation and account login belong to interactive deployment, including already-linked projects. /vc:install and /vc:login are removed. Remote chat reuses existing credentials without starting a browser login; noninteractive deployment remains nonblocking.
The setup panel owns one heading across loading and questions. Question painters supply the body; they do not repeat the heading. Closing a question hands presentation to the next phase without an immediate idle repaint. Routine cancellation has one quiet outcome, while partial work and failures retain their reports.
Connection activation
Authentication returns validated connection metadata and any model list obtained during validation. Local model inspection reads editable source without compiling; dynamic expressions retain routing inspection and safe refusal. Gateway catalog loading overlaps authentication, while provider-specific model lists wait for credentials. Catalog failures are collected without abandoning browser prompts.
Activation compares the intended project settings before writing. Only model source changes acquire a runtime suspension lease and wait for activation. Account, team, and key changes are atomic metadata updates; they do not recompile the agent or replace its worker.
The development host owns credential resolution. Workers request current credentials through the authenticated loopback control plane, reusing the host’s OAuth access token and ChatGPT broker across worker replacements. Rejected-token fingerprints allow refresh without placing tokens in URLs. Credential selection happens at request time; deployments continue using their explicit server credentials.
Successful login returns nonsecret model and connection metadata directly to the TUI. /info and setup diagnostics refresh in the background, with revision checks discarding stale results. Neither a failed inspection nor a pending footer refresh delays the first message. Source activation still completes before a changed model is used.
Status text describes the current wait: browser sign-in, team loading, Gateway access, model availability, or loading the selected model. Local settings reads and credential validation have distinct labels. Loading indicators wait 150 ms to avoid flashing for quick work. Fixed-name debug events measure source inspection, catalog loading, authentication, and activation without recording credentials or team details.