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.
81 lines
2.5 KiB
Go
81 lines
2.5 KiB
Go
package webui
|
|
|
|
import (
|
|
"net/http"
|
|
"strings"
|
|
)
|
|
|
|
// SetupStep is one item in the dashboard's getting-started checklist.
|
|
type SetupStep struct {
|
|
Title string `json:"title"`
|
|
Detail string `json:"detail,omitempty"`
|
|
Done bool `json:"done"`
|
|
}
|
|
|
|
// handleSetup reports which parts of archied are configured.
|
|
//
|
|
// The checklist exists so a new operator is told what is missing rather than
|
|
// shown a dashboard of zeroes and left to infer it. Steps are phrased as
|
|
// actions in plain language -- "Connect a chat channel", not "channels.telegram
|
|
// .bot_token unset" -- because someone who already knows the config key does
|
|
// not need the checklist.
|
|
//
|
|
// Every step is derived from live state, so the list disappears on its own
|
|
// once setup is complete rather than needing to be dismissed.
|
|
func (s *Server) handleSetup(w http.ResponseWriter, r *http.Request) {
|
|
steps := []SetupStep{}
|
|
|
|
if s.Cfg == nil {
|
|
// No config wired in: report nothing rather than guessing, so the
|
|
// dashboard simply omits the panel.
|
|
writeJSON(w, map[string]any{"steps": steps})
|
|
return
|
|
}
|
|
|
|
// The operator's name is deployment data, configured once in [chat]. The
|
|
// dashboard greets with it rather than hardcoding a name, which would be
|
|
// wrong on every deployment but one.
|
|
operator := strings.TrimSpace(s.Cfg.Chat.Operator)
|
|
|
|
steps = append(steps, SetupStep{
|
|
Title: "Give Archie an identity",
|
|
Detail: "The account it commits and comments as.",
|
|
Done: strings.TrimSpace(s.Cfg.BotUser) != "",
|
|
})
|
|
|
|
steps = append(steps, SetupStep{
|
|
Title: "Connect a repository",
|
|
Detail: "Archie polls these for issues assigned to it.",
|
|
Done: len(s.Cfg.Repos) > 0,
|
|
})
|
|
|
|
steps = append(steps, SetupStep{
|
|
Title: "Connect a chat channel",
|
|
Detail: "Talk to Archie and approve its work from your phone.",
|
|
Done: s.hasChannel(),
|
|
})
|
|
|
|
// Only meaningful once there is somewhere to run work.
|
|
if count, err := s.Store.StatusCounts(r.Context()); err == nil {
|
|
total := 0
|
|
for _, n := range count {
|
|
total += n
|
|
}
|
|
steps = append(steps, SetupStep{
|
|
Title: "Run your first task",
|
|
Detail: "Assign Archie an issue, or ask it for something in chat.",
|
|
Done: total > 0,
|
|
})
|
|
}
|
|
|
|
writeJSON(w, map[string]any{"steps": steps, "operator": operator})
|
|
}
|
|
|
|
// hasChannel reports whether any conversational front-end is configured.
|
|
// Chat is disabled entirely when no channel token is set, so the presence of
|
|
// one is the honest signal here.
|
|
func (s *Server) hasChannel() bool {
|
|
return strings.TrimSpace(s.Cfg.Chat.Telegram.TokenEnv) != "" ||
|
|
strings.TrimSpace(s.Cfg.Chat.WebhookAddr) != ""
|
|
}
|