Henry
89bf7657a2
Co-authored-by: nova28 <17953305+nova28@users.noreply.github.com> Co-authored-by: Carlos Florencio <carlosmflorencio@gmail.com>
1.2 KiB
1.2 KiB
id, title, status, wave, depends_on, plan, requirements, acceptance_criteria, system_design
| id | title | status | wave | depends_on | plan | requirements | acceptance_criteria | system_design | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 02-profile-proxy-configuration | Persist profile proxy configuration | planned | 2 |
|
plan.md |
|
|
|
Task 02: Persist Profile Proxy Configuration
Summary
Replace temporary environment-variable selection with a structured agent-profile proxy configuration. It explicitly names the gateway vendor and endpoint, selects native/configured/disabled usage mode, and references an optional stored credential without serializing its plaintext into profile DTOs.
Acceptance
- A profile explicitly selects
teamclaude,openrouter,litellm, or no gateway; endpoint inference never selects a vendor. - The configuration persists through SQLite CRUD and is visible in profile settings, while credential values remain in the secret store.
- Resolver selection is based only on the persisted vendor configuration.
Verification
cd apps/backend && go test -tags fts5 ./internal/agent/settings/... ./internal/backendapp