f0844f6da3
mara on #5170: "dont split caps and perms. its all perms. / dont include the now empty tool groups / nothing set -> default / also add perms to agent creation screen". - hive-sh4re: one `Permission` enum (messaging, meta, inbox, execution, web_tools, manage_root_agent) replaces `ToolGroup` and `Capability`; `lifecycle`/`forge` are gone. `Permission::default_for` is the default for an agent the swarm sets nothing for. - The record is `{ "permissions": [...] }`. Missing key, unset field or no successful read yet = default; `[]` = none; a failed read after a good one keeps the last value. - hive-agent reads its own key every 10s and builds each turn's --tools, --allowedTools and MCP config (rewritten before every turn) from it; the subagent daemon reads it on each start/continue. Agents get a read-only grant on their own key. - hive-c0re restarts an agent only when its manage_root_agent changes. The import now merges meta/capabilities.json and meta/tool-groups.json into one list per agent and deletes both; the "import pending, don't read" decision is `ImportOutcome::read_allowed`, table-tested. - swarm-controller: `GET /api/permissions` (names + default) and an optional `permissions` on `POST /api/agents`, stored before the job is queued. swarm-ui's create-agent form gets a permissions field. - Deleted: HIVE_TOOL_GROUPS and its forward to the subagent daemon, tool_groups.rs, ruth's tool-group seed, the permissions rebuild job (PermPayload/WritePermFile/perm_change), the dashboard permissions tab and its stale-entries panel. Part of #5170.
24 lines
1.1 KiB
JavaScript
24 lines
1.1 KiB
JavaScript
// Shared dashboard state — the one piece of cross-domain state in the
|
|
// dashboard SPA: the live agent roster.
|
|
//
|
|
// The roster is read by nearly every tab (the container tree and the
|
|
// selection bar), so
|
|
// it lives here as a single source of truth that each domain module
|
|
// imports rather than threading through call signatures. Everything
|
|
// else in the dashboard is domain-local and lives with its own module.
|
|
//
|
|
// `containersState` is keyed by `ContainerView.name` so a lifecycle
|
|
// form's POST → 200 → matching SSE event can flip a single row without
|
|
// a full snapshot refetch. Mutated in place (`set` / `delete` / `clear`)
|
|
// by the container apply-handlers; consumers read it by reference, so
|
|
// the imported binding always reflects the latest roster.
|
|
|
|
export const containersState = new Map();
|
|
|
|
// Replace the whole roster from a fresh `/api/state` snapshot. Called by
|
|
// the entry's `refreshState` on cold load and after async-form submits;
|
|
// live single-row updates go through the container apply-handlers.
|
|
export function syncContainersFromSnapshot(s) {
|
|
containersState.clear();
|
|
for (const c of s.containers || []) containersState.set(c.name, c);
|
|
}
|