mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Add Workspace-Scoped LLM Configuration #133

New Issue
Closed
opened 2026-01-30 21:29:35 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 21:29:35 +00:00
Owner
Copy Link

Implement per-workspace LLM provider and personality configuration.

Objective: Allow workspaces to configure their own LLM provider and personality settings.

Tasks:

  • Add WorkspaceSettings model to schema.prisma
  • Define fields: workspace_id, default_llm_provider, default_personality, settings (JSON)
  • Create migration
  • Create workspace-settings.service.ts
  • Update workspaces.controller.ts with settings endpoints
  • Add frontend UI for workspace LLM settings
  • Implement provider selection logic (workspace > user > system)
  • Write unit and E2E tests

Configuration Hierarchy:

  1. Workspace-level settings (highest priority)
  2. User-level provider instances
  3. System-level providers (fallback)

Acceptance Criteria:

  • Workspaces can select LLM provider
  • Workspaces can set default personality
  • Settings persist correctly
  • Multi-tenant isolation maintained
  • No cross-workspace data leakage
  • Tests pass with 85%+ coverage

Related: Epic #121, Phase 5 Workspace Configuration
Depends on: #128 (LlmProviderInstance), #130 (Personality)

Implement per-workspace LLM provider and personality configuration. Objective: Allow workspaces to configure their own LLM provider and personality settings. Tasks: - Add WorkspaceSettings model to schema.prisma - Define fields: workspace_id, default_llm_provider, default_personality, settings (JSON) - Create migration - Create workspace-settings.service.ts - Update workspaces.controller.ts with settings endpoints - Add frontend UI for workspace LLM settings - Implement provider selection logic (workspace > user > system) - Write unit and E2E tests Configuration Hierarchy: 1. Workspace-level settings (highest priority) 2. User-level provider instances 3. System-level providers (fallback) Acceptance Criteria: - Workspaces can select LLM provider - Workspaces can set default personality - Settings persist correctly - Multi-tenant isolation maintained - No cross-workspace data leakage - Tests pass with 85%+ coverage Related: Epic #121, Phase 5 Workspace Configuration Depends on: #128 (LlmProviderInstance), #130 (Personality)
jason.woltje added the databasephase-5databasep0apiapi labels 2026-01-30 21:29:35 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:40:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api database database p0 phase-5
Milestone
No items
No Milestone M4-LLM (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#133
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?