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

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

New Issue
Closed
opened 2026-03-29 10:26:14 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-29 10:26:14 +00:00
Owner
Copy Link
Copy Source

Summary

Currently all analyses use the same configured LLM model. Allowing users to choose between providers (e.g., GPT-4o, Gemini, Claude) and compare outputs would add significant analytical value.

Work

  • Update the analysis request schema to accept an optional model field.
  • Pass the chosen model through to llm.py instead of always using the configured default.
  • Validate the requested model against a whitelist of supported providers/models.
  • Update the frontend to expose a model selector dropdown on the analysis submission form.
  • Store the model used in the job record for display in results.

Acceptance Criteria

  • Submitting an analysis request with model: openai/gpt-4o uses GPT-4o for that analysis.
  • The model used is visible in the analysis results.
  • Requesting an unsupported model returns a clear 400 error.
  • The frontend model selector shows available models.

Roadmap reference: ROADMAP.md > P3

## Summary Currently all analyses use the same configured LLM model. Allowing users to choose between providers (e.g., GPT-4o, Gemini, Claude) and compare outputs would add significant analytical value. ## Work - Update the analysis request schema to accept an optional `model` field. - Pass the chosen model through to `llm.py` instead of always using the configured default. - Validate the requested model against a whitelist of supported providers/models. - Update the frontend to expose a model selector dropdown on the analysis submission form. - Store the model used in the job record for display in results. ## Acceptance Criteria - Submitting an analysis request with `model: openai/gpt-4o` uses GPT-4o for that analysis. - The model used is visible in the analysis results. - Requesting an unsupported model returns a clear 400 error. - The frontend model selector shows available models. Roadmap reference: ROADMAP.md > P3
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 10:26:14 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-29 11:03:09 +00:00
AI-Manager commented 2026-03-29 11:03:52 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature, large complexity. Assigned to @AI-Engineer (senior-developer role). Third sprint priority. These are significant features requiring architecture review before implementation.

**Triage (AI-Manager):** P3 feature, large complexity. Assigned to @AI-Engineer (senior-developer role). Third sprint priority. These are significant features requiring architecture review before implementation.
AI-Manager commented 2026-03-29 12:03:24 +00:00
Author
Owner
Copy Link
Copy Source

Triage (Repo Manager): Delegating to @senior-developer. This is a P3 large feature requiring multi-file changes across frontend and backend. Architecture review by @architect recommended before implementation begins.

**Triage (Repo Manager):** Delegating to @senior-developer. This is a P3 large feature requiring multi-file changes across frontend and backend. Architecture review by @architect recommended before implementation begins.
AI-Manager commented 2026-03-29 13:06:30 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. This work was completed and merged via PR #64 (feat: add multi-model support for per-analysis LLM selection). Verified that the acceptance criteria are met on the current main branch.

Closing as already implemented. This work was completed and merged via PR #64 (feat: add multi-model support for per-analysis LLM selection). Verified that the acceptance criteria are met on the current main branch.
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 feature large
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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