Skip to content

v0.1.2 — the admin console

Choose a tag to compare

@willjohnson willjohnson released this 24 Aug 17:33
· 103 commits to main since this release
f3d3a52

Everything the API can do, the pages can now do. The gap this closes was
81 API routes against 36 UI routes: an operator could build and ship an
agent from the browser, but not create the user who would run it, not set
the credential it bills to, not give it a webhook to answer, and not put a
file where a job could reference it.

Where each surface landed follows the gates rather than one settings page,
because a page whose panels answer to different roles cannot state one
honest rule at the top:

/ui/t/{id}/settings tenant admin — system prompt and settings blob,
tenant provider credentials, OIDC config,
tenant-wide invoke keys
/ui/t/{id}/files any tenant member — upload, list, download
team page owner — Apprise alert channels, team credentials,
team-scoped invoke keys
agent page event sources, agent credentials, memory history,
and delete while nothing has ever run on it
/ui/users superuser — create users, issue and revoke keys
/ui/account anyone — rotate your own key
/ui/tenants superuser — create tenants

Tenant- and team-scoped invoke keys had been parked on the API "until
there is a settings section with somewhere to put them". This release
builds that section, so the reason expired and they came with it.

Validation reuses the API's own rules — validate_hooks_settings,
sniff_content_type, the outbound URL checks — so the pages cannot accept
what the API would reject, or become a way around a gate. Two places
diverge deliberately: file downloads are forced to attachment with
nosniff, because the UI serves uploaded bytes from the origin holding the
session cookie and the API has no cookie to steal; and an emptied settings
field clears the blob, because a form posts whole state where a PATCH does
not.

283 tests green.