You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status update after code audit: partially shipped, keep open. Implemented: Agents, Agent detail, Instances, and Instance detail pages exist and consume admin APIs. Remaining gaps vs acceptance: unpublish/delete/cancel actions are not present because the moderation API in #34 is still open, and live runtime status still depends on the #31 live-check gap.
What already existed (so this was smaller than the ticket implies): Agents.tsx, Instances.tsx, AgentDetail.tsx and InstanceDetail.tsx were all already present from the #35 scaffold. Agents had a search box; Instances had nothing at all; the details rendered connectors/consents/board/usage.
What was missing, and is now built:
Agents list — the filters the API gained in 5b7fe86 are wired: visibility, status, owner (login or id) alongside search, plus server-side pagination against total (any filter change resets the offset, so a narrowed set cannot page into nothing). Added the category + status columns.
Instances list — filters for agent (slug or id), owner, status, pagination, display name, last-seen, and a live runtime column. The filter state is mirrored into the URL, so Agents → subscribers and User → instances deep-link here pre-filtered instead of making an operator retype a slug.
Live vs claimed runtime. The list renders the relay value and renders the capped fan-out's null as unknown, never as offline — plus a third state, "no runner", for instances that never registered one. Instance detail shows connected per node beside the DB column, labelled Live vs Reported, with a line saying which to trust: instance_runtime_nodes.status is never cleared on an unclean disconnect and reads "online" for machines off for days.
Agent detail — subscriber rollup (active/ever), the cross-instance recent-activity feed ("is this working for anyone"), owner/instance deep links, and the moderation panel.
Activity
serge-ivo commentedon Aug 6, 2026
Status update after code audit: partially shipped, keep open. Implemented: Agents, Agent detail, Instances, and Instance detail pages exist and consume admin APIs. Remaining gaps vs acceptance: unpublish/delete/cancel actions are not present because the moderation API in #34 is still open, and live runtime status still depends on the #31 live-check gap.
feat(admin): the operator can now act, and be audited for it (#38, #41)
serge-ivo commentedon Aug 6, 2026
Shipped in 66fcc23 (CI + Deploy Host green; live at https://proagentstore.online/admin/).
What already existed (so this was smaller than the ticket implies):
Agents.tsx,Instances.tsx,AgentDetail.tsxandInstanceDetail.tsxwere all already present from the #35 scaffold. Agents had a search box; Instances had nothing at all; the details rendered connectors/consents/board/usage.What was missing, and is now built:
visibility,status,owner(login or id) alongside search, plus server-side pagination againsttotal(any filter change resets the offset, so a narrowed set cannot page into nothing). Added the category + status columns.agent(slug or id),owner,status, pagination, display name, last-seen, and a live runtime column. The filter state is mirrored into the URL, soAgents → subscribersandUser → instancesdeep-link here pre-filtered instead of making an operator retype a slug.nullas unknown, never as offline — plus a third state, "no runner", for instances that never registered one. Instance detail showsconnectedper node beside the DB column, labelled Live vs Reported, with a line saying which to trust:instance_runtime_nodes.statusis never cleared on an unclean disconnect and reads "online" for machines off for days.All three ACs met. Runtime status is green/grey/yellow-unknown rather than green/grey, deliberately — see the #41 comment.
ci: typecheck the admin app