wdevs/amcs
5
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Add an admin UI for browsing and managing AMCS data #11

New Issue
Open
opened 2026-04-03 11:12:38 +00:00 by sam · 0 comments
sam commented 2026-04-03 11:12:38 +00:00
Member
Copy Link

Summary

Provide an admin interface for inspecting thoughts, projects, links, files, skills, guardrails, and maintenance state without relying only on MCP or direct database access.

Why

An admin UI is listed as a deferred feature in the implementation plan and would improve operability, debugging, and day-to-day maintenance.

Scope ideas

  • Browse/search thoughts and projects
  • Inspect metadata status, related links, and attachment/file records
  • Trigger maintenance actions such as backfill or metadata retry where appropriate
  • View server/version/config diagnostics that are safe to expose
  • Add authentication/authorization for the UI
  • Decide whether this is server-rendered, SPA, or a lightweight embedded panel

Acceptance criteria

  • Operators can inspect core AMCS entities through a documented UI
  • Sensitive actions are authenticated and permissioned
  • Maintenance and diagnostics visibility improve without exposing secrets
  • UI scope and deployment model are documented

Source

Deferred feature from llm/plan.md: admin UI.

## Summary Provide an admin interface for inspecting thoughts, projects, links, files, skills, guardrails, and maintenance state without relying only on MCP or direct database access. ## Why An admin UI is listed as a deferred feature in the implementation plan and would improve operability, debugging, and day-to-day maintenance. ## Scope ideas - Browse/search thoughts and projects - Inspect metadata status, related links, and attachment/file records - Trigger maintenance actions such as backfill or metadata retry where appropriate - View server/version/config diagnostics that are safe to expose - Add authentication/authorization for the UI - Decide whether this is server-rendered, SPA, or a lightweight embedded panel ## Acceptance criteria - Operators can inspect core AMCS entities through a documented UI - Sensitive actions are authenticated and permissioned - Maintenance and diagnostics visibility improve without exposing secrets - UI scope and deployment model are documented ## Source Deferred feature from `llm/plan.md`: admin UI.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
debugging
integration
planned
ux
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hein root sam sgcommand warkanum
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wdevs/amcs#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?