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

Multi-model LLM support: let users select provider per analysis #636

New Issue
Closed
opened 2026-03-28 11:24:08 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 11:24:08 +00:00
Owner
Copy Link
Copy Source

Context

All analyses currently use the single model configured in LLM_MODEL. Power users want to compare outputs from different providers (GPT-4o, Gemini, Claude) for the same patent set.

Roadmap item: P3 > Multi-model support

What to do

  • Extend the POST /analyze (and batch) request body to accept an optional model field.
  • If provided, use that model for the analysis; otherwise fall back to the configured default.
  • Update the frontend to render a model-selector dropdown on the analysis submission form.
  • Store the model name used in the job/result record so results are clearly attributed.

Acceptance criteria

  • Submitting an analysis with "model": "openai/gpt-4o" uses that model.
  • The result record includes the model name used.
  • The frontend dropdown lists at least two model options.
  • Omitting the model field behaves as before.
## Context All analyses currently use the single model configured in `LLM_MODEL`. Power users want to compare outputs from different providers (GPT-4o, Gemini, Claude) for the same patent set. Roadmap item: P3 > Multi-model support ## What to do - Extend the `POST /analyze` (and batch) request body to accept an optional `model` field. - If provided, use that model for the analysis; otherwise fall back to the configured default. - Update the frontend to render a model-selector dropdown on the analysis submission form. - Store the model name used in the job/result record so results are clearly attributed. ## Acceptance criteria - [ ] Submitting an analysis with `"model": "openai/gpt-4o"` uses that model. - [ ] The result record includes the model name used. - [ ] The frontend dropdown lists at least two model options. - [ ] Omitting the `model` field behaves as before.
AI-Manager added the P3agent-readylargefeature labels 2026-03-28 11:24:09 +00:00
AI-Manager commented 2026-03-28 12:05:00 +00:00
Author
Owner
Copy Link
Copy Source

Closing: already implemented on main. Frontend Analysis and Batch pages include model pickers with provider information. Backend accepts a model parameter for per-analysis LLM selection.

Closing: already implemented on main. Frontend Analysis and Batch pages include model pickers with provider information. Backend accepts a `model` parameter for per-analysis LLM selection.
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#636
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?