Skip to content

feat(llm): Support per-project model settings#566

Open
kairan0 wants to merge 1 commit into
nashsu:mainfrom
kairan0:feature/per-project-llm-settings
Open

feat(llm): Support per-project model settings#566
kairan0 wants to merge 1 commit into
nashsu:mainfrom
kairan0:feature/per-project-llm-settings

Conversation

@kairan0

@kairan0 kairan0 commented Jul 11, 2026

Copy link
Copy Markdown

Projects can now keep their own active LLM provider, provider overrides, and resolved model config. Opening or switching projects restores that project's saved model settings, while projects without an override continue to use the existing global defaults.

The same project-scoped config is used by the desktop Agent, local API, and MCP chat paths, so external callers address the requested project's model instead of silently using the global setting. Existing top-level LLM settings remain the fallback, and project overrides are stored in app-state by stable project id.

Closes #562

Persist active provider, provider overrides, and resolved LLM config per project while preserving the existing global fallback behavior.

Restore project-specific LLM settings on project switch and use them for desktop Agent, local API, and MCP chat calls.

Closes nashsu#562
@kairan0
kairan0 marked this pull request as ready for review July 11, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: Support per-project LLM/model settings

1 participant