oceanbase / oceanbase/powercontext

feat: expose all supported artifact families in the Dashboard

Open
#1,533 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
1.1k
Forks
214
Avg merge
1d 11h
Merged PRs (30d)
199

Description

Problem

The current Dashboard does not expose all artifact families supported by the Runtime. In the current UI, the sidebar shows:

  • Home
  • Handoff
  • Memory
  • Experience & Skills
  • Usage

However, there is no dedicated Dashboard entry for Topic Memory, Profile, or Prompt configuration. This makes backend capabilities difficult to discover and prevents users from inspecting or managing artifacts that are already supported by the Server/API.

The attached user screenshot shows the current artifact navigation state.

Expected behavior

The Dashboard should provide a discoverable view for every supported artifact family, or clearly explain when a family is API-only. At minimum, the UI should expose or link to:

  • Memory
  • Topic Memory
  • Experience
  • Skill
  • Handoff
  • Profile
  • Prompt configuration
  • Usage/diagnostics

Topic Memory should show active topics, revisions/publications, source lineage, and processing status. Prompt configuration should show auto/custom mode, effective instructions, and the configured scope.

Acceptance criteria

  • Dashboard navigation reflects the artifact families advertised by the Server capabilities/API.
  • Topic Memory is inspectable without requiring direct API calls or SQLite access.
  • Profile and Prompt configuration have either dedicated views or explicit, documented API-only status.
  • Empty states and disabled capabilities are represented clearly instead of silently omitting the artifact.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the current Dashboard sidebar and comparing it with the artifact families exposed by the Server capabilities/API. Done means every advertised family is inspectable, or its API-only status is explicit, with clear empty and disabled states.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, sqlite
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.