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

[Migration #121.1] Implement multi-provider LLM abstraction layer #308

New Issue
Closed
opened 2026-02-04 02:35:53 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-02-04 02:35:53 +00:00
Owner
Copy Link

Parent EPIC: #121 - Backend Migration from Jarvis r1
Phase: 1 - LLM Abstraction Layer
Estimate: 2-3 days

Description

Migrate the multi-provider LLM infrastructure from jarvis r1 to support Ollama, OpenAI, Anthropic, and other providers.

Source Files

  • jarvis/core/conversation.py (LLM manager)
  • jarvis/storage/models/llm_routing.py
  • jarvis/storage/repositories/llm_routing.py
  • jarvis/api/routes/llm.py
  • jarvis/api/schemas/llm_routing.py

Target Implementation

  • Create apps/api/src/llm/ module
  • Implement provider abstraction interfaces
  • Add support for multiple LLM providers
  • Create provider registry and routing logic
  • Add configuration management

Acceptance Criteria

  • LLM provider interface defined
  • Ollama provider implemented
  • Provider registry and routing
  • Configuration schema for providers
  • Unit tests (85% coverage)
  • Integration tests for each provider
**Parent EPIC:** #121 - Backend Migration from Jarvis r1 **Phase:** 1 - LLM Abstraction Layer **Estimate:** 2-3 days ## Description Migrate the multi-provider LLM infrastructure from jarvis r1 to support Ollama, OpenAI, Anthropic, and other providers. ## Source Files - `jarvis/core/conversation.py` (LLM manager) - `jarvis/storage/models/llm_routing.py` - `jarvis/storage/repositories/llm_routing.py` - `jarvis/api/routes/llm.py` - `jarvis/api/schemas/llm_routing.py` ## Target Implementation - Create `apps/api/src/llm/` module - Implement provider abstraction interfaces - Add support for multiple LLM providers - Create provider registry and routing logic - Add configuration management ## Acceptance Criteria - [ ] LLM provider interface defined - [ ] Ollama provider implemented - [ ] Provider registry and routing - [ ] Configuration schema for providers - [ ] Unit tests (85% coverage) - [ ] Integration tests for each provider
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-02-04 02:35:53 +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
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#308
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?