QRun-IO/qbit-assistant
0
0 Fork 0
Code Issues 3 Pull Requests 7 Actions Packages Projects Releases 23 Wiki Activity

Register assistant user settings as a core Preferences section (replace /assistant/preferences) #25

New Issue
Open
opened 2026-10-13 23:39:00 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-13 23:39:00 +00:00 (Migrated from github.com)
Copy link
Copy source

QQQ core is adding a standard per-user Preferences capability: GET /qqq/v1/preferences, GET and PATCH /qqq/v1/preferences/{section} (spec: docs/USER-PREFERENCES.md in QRun-IO/qqq, branch feature/user-preferences). Qbits register a section of typed fields (normal QFieldMetaData), with storage delegated to a provider SPI (UserPreferenceProviderInterface), so each qbit keeps its own table. Next UI renders every section on one Preferences page from the user menu, and features can deep-link to their own section.

When #21 (write mode) lands, the assistant's per-user settings should register as an "Assistant" section instead of shipping a bespoke GET/PATCH /assistant/preferences endpoint.

Proposed shape

  • Section assistant (label "Assistant", icon smart_toy, app scope the assistant app, permission the assistant's use permission).
  • Fields: defaultWriteMode (ENUM: Read-only / Write), autoConfirmLowRisk (BOOLEAN). Make it read-only, with a reason, when the policy doesn't allow auto-confirm.
  • Provider: an AssistantPreferencesProvider backed by the existing assistant_user_preference table. Its validate enforces the policy (today's 403 becomes a 400 message).
  • /config can keep reporting preferences, but read them through the provider. Drop or deprecate the bespoke operations, so clients have a single way to change preferences.
  • The Next panel's write-mode toggle keeps working. It reads and writes through /qqq/v1/preferences/assistant.

Depends on: the QQQ RC that ships user preferences, plus #21.

QQQ core is adding a standard per-user Preferences capability: `GET /qqq/v1/preferences`, `GET` and `PATCH /qqq/v1/preferences/{section}` (spec: `docs/USER-PREFERENCES.md` in QRun-IO/qqq, branch `feature/user-preferences`). Qbits register a **section** of typed fields (normal `QFieldMetaData`), with storage delegated to a provider SPI (`UserPreferenceProviderInterface`), so each qbit keeps its own table. Next UI renders every section on one Preferences page from the user menu, and features can deep-link to their own section. When #21 (write mode) lands, the assistant's per-user settings should register as an **"Assistant" section** instead of shipping a bespoke `GET/PATCH /assistant/preferences` endpoint. **Proposed shape** - Section `assistant` (label "Assistant", icon `smart_toy`, app scope the assistant app, permission the assistant's use permission). - Fields: `defaultWriteMode` (ENUM: Read-only / Write), `autoConfirmLowRisk` (BOOLEAN). Make it read-only, with a reason, when the policy doesn't allow auto-confirm. - Provider: an `AssistantPreferencesProvider` backed by the existing `assistant_user_preference` table. Its `validate` enforces the policy (today's 403 becomes a 400 message). - `/config` can keep reporting `preferences`, but read them through the provider. Drop or deprecate the bespoke operations, so clients have a single way to change preferences. - The Next panel's write-mode toggle keeps working. It reads and writes through `/qqq/v1/preferences/assistant`. **Depends on:** the QQQ RC that ships user preferences, plus #21.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
architecture
Architecture review: coupling, cohesion, UI API
 bug
Something isn't working
 dependencies
documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 github_actions
Pull requests that update GitHub Actions code
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 java
Pull requests that update java code
 question
Further information is requested
 release:rc
Merging this develop PR cuts the next release candidate
 secuurity
ux
Admin UX / information architecture
 wontfix
This will not be worked on
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
forge-recovery (Forge Recovery) james.maes (James Maes)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-assistant#25