feat(login): custom provider rows, URL / name / key steps, and custom:<name> authenticate
The picker lists Custom provider (OpenAI compatible) and (Anthropic compatible).
The TUI asks for a base URL, a name (default from the host), and a key, saves the
definition and the key, and the agent validates the key against GET {base}/models.
PTY e2e covers both wires against the mock inference server.
This commit is contained in:
1 parent
eb86d7ec26
commit
791f953c07
18 files changed
+1198
-85
No files matched your search
@@ -15,6 +15,8 @@ mod agent_response;
|
||||
mod auto_compact_top_row;
|
||||
#[path = "pty_e2e/basename_path_demo_pty.rs"]
|
||||
mod basename_path_demo_pty;
|
||||
#[path = "pty_e2e/custom_provider.rs"]
|
||||
mod custom_provider;
|
||||
#[path = "pty_e2e/doubled_lines_out_of_band_repro.rs"]
|
||||
mod doubled_lines_out_of_band_repro;
|
||||
#[path = "pty_e2e/initial_prompt_positional_auto_submits.rs"]
|
||||
|
||||
Reference in new issue
Block a user