Skip to content

feat(web): attach a provider account to each project - #2

Merged
enisze merged 2 commits into
mainfrom
feat/project-default-agent
Jul 29, 2026
Merged

feat(web): attach a provider account to each project#2
enisze merged 2 commits into
mainfrom
feat/project-default-agent

Conversation

@enisze

@enisze enisze commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Add a per-project "Default agent" selector so a project can pin a
specific provider instance (account) and model. New threads in that
project start on that account, still overridable per thread.

The selection persists to the project's existing defaultModelSelection,
so no contract or server changes were needed. The field reads the value
live from the projects atom rather than the dialog's captured snapshot,
and keeps a removed/disabled instance visible as "(unavailable)" so a
stale pin can be cleared instead of silently vanishing.

Wired into both the V1 and V2 sidebar project dialogs, plus a
collapsible Providers-settings guide explaining how to set up two
accounts of the same provider and route each to a different project.

Co-Authored-By: Claude noreply@anthropic.com

enisze and others added 2 commits July 29, 2026 20:16
Add a per-project "Default agent" selector so a project can pin a
specific provider instance (account) and model. New threads in that
project start on that account, still overridable per thread.

The selection persists to the project's existing defaultModelSelection,
so no contract or server changes were needed. The field reads the value
live from the projects atom rather than the dialog's captured snapshot,
and keeps a removed/disabled instance visible as "(unavailable)" so a
stale pin can be cleared instead of silently vanishing.

Wired into both the V1 and V2 sidebar project dialogs, plus a
collapsible Providers-settings guide explaining how to set up two
accounts of the same provider and route each to a different project.

Co-Authored-By: Claude <noreply@anthropic.com>
Resolves conflicts in SidebarV2.tsx against the per-project GitHub
account feature (#1), which landed on the same project settings dialog.

Every conflict was additive rather than either/or, so both features are
kept intact: the GitHubAccountRef and ModelSelection type imports, the
GitHubIcon and ProjectDefaultAgentField component imports, and both the
updateProjectDefaultModelSelection and updateProjectGitHubAccount
callbacks (whose bodies had overlapped on their shared toast tail).

Co-Authored-By: Claude <noreply@anthropic.com>
@enisze
enisze merged commit 98a1ce0 into main Jul 29, 2026
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.

1 participant