Skip to content

feat: enhance generalized UI with sidebar navigation and field descriptions - #15

Open
hdkiller wants to merge 5 commits into
BlackBeltTechnology:developfrom
hdkiller:feat/extension-settings-ui
Open

feat: enhance generalized UI with sidebar navigation and field descriptions#15
hdkiller wants to merge 5 commits into
BlackBeltTechnology:developfrom
hdkiller:feat/extension-settings-ui

Conversation

@hdkiller

Copy link
Copy Markdown

Enhances the generalized UI schema to support field descriptions, sections, and sidebar-based navigation. Adds an Extensions button to the session header.

@hdkiller

Copy link
Copy Markdown
Author
image image

robertcsakany added a commit that referenced this pull request Apr 27, 2026
…cture

Captures the multi-proposal architectural exploration for making the dashboard
shell pluggable. Two design proposals (no implementation yet) plus seven
implementation/extraction scaffolds.

Design proposals (artifacts complete, all 15 open questions resolved):

- extension-ui-system: pull-based discovery probe (ui:list-modules) +
  bounded slot taxonomy for descriptor-only third-party extensions.
  Phases: management-modal (1), live decorations (2), RJSF forms (4).
  PR #15's "Generalized Extension UI System" rebuilt fresh on develop;
  PR #15 referenced as ground-truth, not merged.

- dashboard-plugin-architecture: umbrella for first-party plugin tier.
  Two-tier model — third-party descriptors + first-party React plugins
  target the same slot contract. 9 first-party slots
  (sidebar-folder-section, session-card-badge, session-card-action-bar,
  content-view, content-header-sticky, content-inline-footer,
  anchored-popover, command-route, settings-section, tool-renderer).
  Manifest format forward-compatible with future node_modules discovery
  (unblocks PR-back paths to upstream packages like @tintinweb/pi-subagents).
  Plugin context API + reactive settings persistence under plugins.<id>.*
  validated against JSON Schema. Bundled-by-default plugin concept for
  universally-relevant features (e.g. git).

Implementation scaffolds (proposal.md only; design/specs/tasks via /opsx:continue):

- add-extension-ui-modal, add-extension-ui-decorations,
  add-extension-ui-rjsf-form (descriptor-protocol implementation phases)
- extract-openspec-as-plugin (~65 file move into packages/openspec-plugin)
- extract-flows-as-plugin (~12 file move; introduces reducer-slice mechanism)
- extract-subagents-as-plugin (~7 file move; future PR upstream to
  @tintinweb/pi-subagents once node_modules discovery lands)
- extract-git-as-plugin (~25 file move; bundled by default; no upstream
  PR path because git is the OS, not a vendored package)

Documentation:

- openspec/specs/extension-ui-system/spec.md stub for the eventual
  archive target (cross-references interactive-ui-dialogs, ui-proxy,
  extension-ui-forwarding).
- docs/architecture.md gains "Extension UI System (planned, design-only)"
  section.
@robertcsakany

Copy link
Copy Markdown
Member

Thanks for your contribution. I've used to design more generalized solution for the feature you draw in this PR.

@robertcsakany robertcsakany self-assigned this May 2, 2026
@robertcsakany robertcsakany added the enhancement New feature or request label May 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants