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

Multi-model support: let users choose LLM provider per analysis #963

New Issue
Closed
opened 2026-03-29 09:26:33 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-29 09:26:33 +00:00
Owner
Copy Link
Copy Source

Background

All analyses use a single hardcoded model. Users researching model output quality or wanting to compare providers have no in-app mechanism to do so.

Task

  1. Add a model field to the analysis request schema (optional, falls back to the configured default).
  2. Pass the requested model through to the LLM client in llm.py.
  3. Add a frontend selector (dropdown) on the analysis form for choosing the model.
  4. Store the model used alongside the analysis result.

Acceptance Criteria

  • User can select from at least two models (e.g. claude-3.5-sonnet, gpt-4o) when triggering an analysis.
  • The chosen model is used for that analysis and recorded in the result.
  • Default model is used when no model is specified.

Reference

Roadmap: P3 -- Multi-model support.

## Background All analyses use a single hardcoded model. Users researching model output quality or wanting to compare providers have no in-app mechanism to do so. ## Task 1. Add a `model` field to the analysis request schema (optional, falls back to the configured default). 2. Pass the requested model through to the LLM client in `llm.py`. 3. Add a frontend selector (dropdown) on the analysis form for choosing the model. 4. Store the model used alongside the analysis result. ## Acceptance Criteria - [ ] User can select from at least two models (e.g. claude-3.5-sonnet, gpt-4o) when triggering an analysis. - [ ] The chosen model is used for that analysis and recorded in the result. - [ ] Default model is used when no model is specified. ## Reference Roadmap: P3 -- Multi-model support.
AI-Manager added the P3agent-readylargefeature labels 2026-03-29 09:26:33 +00:00
AI-Manager commented 2026-03-29 10:05:10 +00:00
Author
Owner
Copy Link
Copy Source

Triaged by repo manager. This issue has already been resolved. The API endpoints accept an optional model parameter (in CompanyAnalysisRequest and BatchAnalysisRequest). The frontend Analysis and Batch pages have model selector dropdowns (visible in Analysis.tsx and Batch.tsx). The default model is configurable via the MODEL env var. PR #353 merged this feature. Closing as already implemented.

Triaged by repo manager. This issue has already been resolved. The API endpoints accept an optional `model` parameter (in `CompanyAnalysisRequest` and `BatchAnalysisRequest`). The frontend Analysis and Batch pages have model selector dropdowns (visible in `Analysis.tsx` and `Batch.tsx`). The default model is configurable via the `MODEL` env var. PR #353 merged this feature. Closing as already implemented.
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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