leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add multi-model LLM support: let users choose provider per analysis #423

New Issue
Closed
opened 2026-03-27 18:25:50 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 18:25:50 +00:00
Owner
Copy Link
Copy Source

Summary

All analyses are run through a single hardcoded model. Allowing users to choose their LLM provider per analysis enables comparison and flexibility.

What to do

  1. Extend the analysis request schema to include an optional model field (default: the configured MODEL env var)
  2. Update llm.py to accept and pass the model override to OpenRouter
  3. Store the model used in the analysis result for reference
  4. Add a model selector in the frontend analysis request form
  5. Document supported model strings in the README

Acceptance Criteria

  • Submitting an analysis with model: "openai/gpt-4o" uses that model
  • The analysis result record stores which model was used
  • The frontend model selector lists at least 3 common options
  • Omitting model in the request uses the configured default

Reference

Roadmap: P3 - Multi-model support

## Summary All analyses are run through a single hardcoded model. Allowing users to choose their LLM provider per analysis enables comparison and flexibility. ## What to do 1. Extend the analysis request schema to include an optional `model` field (default: the configured `MODEL` env var) 2. Update `llm.py` to accept and pass the model override to OpenRouter 3. Store the model used in the analysis result for reference 4. Add a model selector in the frontend analysis request form 5. Document supported model strings in the README ## Acceptance Criteria - Submitting an analysis with `model: "openai/gpt-4o"` uses that model - The analysis result record stores which model was used - The frontend model selector lists at least 3 common options - Omitting `model` in the request uses the configured default ## Reference Roadmap: P3 - Multi-model support
AI-Manager added the P3agent-readylarge labels 2026-03-27 18:25:50 +00:00
AI-Manager commented 2026-03-27 19:06:51 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already Implemented

After reviewing the codebase, this issue has already been fully implemented in the current main branch.

This issue can be closed.

## Triage: Already Implemented After reviewing the codebase, this issue has already been fully implemented in the current `main` branch. This issue can be closed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready large
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#423
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?