Files
archie/internal/webui/api_memory.go
T
sam 4d44ef76f5 feat(webui): rebuild the dashboard
The old UI was a single 200-line Go file serving one hand-written HTML
page of task rows. It showed that archied was running and almost nothing
about what it was doing -- skills, workflows, memory, channels, logs and
configuration were all invisible unless you read the source or the
config file.

The dashboard now covers each of those as its own section, built as a
Vite app under ui/ at the repo root: it is a separate artefact from the
Go daemon, not an internal package of it. dist/ is committed so building
archied never needs a Node toolchain, and the !no_ui build tag keeps an
embed-free build available.

Both sides are split by concern rather than by layer -- one Go file per
API area, one folder per UI section with its own CSS -- so a change to
logs cannot disturb tasks.

Pages report consequences, not just state: an empty memory page says
Archie starts every conversation with no recollection of earlier ones,
and the setup checklist names what is missing in plain language instead
of showing a grid of zeroes. Nothing greets by a hardcoded name; the
operator comes from [chat], which is deployment data.

Auth is exposure control, not capability control -- the agent already
holds this user's authority through its own tools. So a loopback bind
needs no token, and only a reachable bind mints one and logs a URL,
which means an instance cannot be exposed merely by omitting config.

Container startup now degrades instead of aborting, for the reason
resolveForge already does: a missing agent image should not deny the
operator chat and the dashboard, and under Restart=on-failure it turns a
recoverable problem into a crash loop with the real error scrolling past.

`task dev` runs the daemon under air and the Vite server together in one
terminal.
2026-08-04 01:45:36 +10:00

66 lines
2.0 KiB
Go

package webui
import (
"net/http"
"github.com/samcharles93/archie-core/internal/memory"
)
// MemoryProviderView describes one memory provider for the dashboard.
type MemoryProviderView struct {
Name string `json:"name"`
// Role is "builtin" or "external". Archie always has a builtin provider;
// an external one is optional and configured separately.
Role string `json:"role"`
// Available reports the provider's own readiness check -- a provider can
// be configured but unusable when a binary is missing or a connection is
// down, and that distinction is exactly what an operator needs to see.
Available bool `json:"available"`
// Tools are the capabilities this provider gives the agent, by name.
Tools []MemoryToolView `json:"tools"`
}
// MemoryToolView is one tool a provider exposes to the agent.
type MemoryToolView struct {
Name string `json:"name"`
Description string `json:"description"`
}
// handleMemory reports what Archie can remember and with what.
//
// Memory is otherwise invisible: it is a set of tools handed to the model at
// discovery time, so without this the only way to know what the agent can
// recall is to read the provider source.
func (s *Server) handleMemory(w http.ResponseWriter, r *http.Request) {
if s.Memory == nil {
writeJSON(w, map[string]any{"providers": []any{}, "enabled": false})
return
}
views := []MemoryProviderView{}
if p := s.Memory.Builtin(); p != nil {
views = append(views, providerView(p, "builtin"))
}
if p := s.Memory.External(); p != nil {
views = append(views, providerView(p, "external"))
}
writeJSON(w, map[string]any{"providers": views, "enabled": true})
}
func providerView(p memory.MemoryProvider, role string) MemoryProviderView {
view := MemoryProviderView{
Name: p.Name(),
Role: role,
Available: p.IsAvailable(),
Tools: []MemoryToolView{},
}
for _, t := range p.GetToolSchemas() {
view.Tools = append(view.Tools, MemoryToolView{
Name: t.Name,
Description: t.Description,
})
}
return view
}