Repository navigation
feat: remove the project agent and model setup - #7820
Closed
ronishrohan wants to merge 6 commits into
Closed
ronishrohan wants to merge 6 commits into
ronishrohan wants to merge 6 commits into
Conversation
Project config now contributes only role permissions to a spawn. Legacy worker/orchestrator agent, model, effort and mode are ignored and stripped on every write; the schema still accepts them so older clients keep working. - Drop DefaultWorkerReviewer; the reviewer follows the worker's own agent. - Remove Summary.orchestratorAgent and regenerate the API files. - Make --worker-agent and --orchestrator-agent hidden deprecated no-ops. - Legacy import no longer maps agent or model into project config. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAocjNsUtdxZ78MGF2WNDp
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAocjNsUtdxZ78MGF2WNDp
- Creating a local project no longer asks for agents; the setup dialog only appears for tracker intake, a repository setup notice, or a failed create. - Project settings drop the worker/orchestrator agent, model, mode and effort rows and keep approval and reviewer settings. Cloud keeps its rows. - The new-chat composer preselects the last ready agent, then the first ready agent in priority order, ignoring any old project pin. - Remove orchestratorAgent from the workspace model and the unused i18n keys. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BAocjNsUtdxZ78MGF2WNDp
Contributor
🏆 Review leaderboardOct 29, 2026–Nov 5, 2026 · UTC
Ranked by distinct external PRs reviewed, then review rounds, then PR comments. Self-activity and bot activity are excluded. Show 8 more reviewers
|
4 of 6 tasks
…trator-36/sa-ui # Conflicts: # frontend/src/renderer/components/CloudProjectSettingsForm.tsx # frontend/src/renderer/components/ProjectSettingsEditor.tsx
Adding a project no longer asks for agents, and the orchestrator spawn names none. A remote host on an AO version from before this change still needs a project agent, so its orchestrator would fail to start. When adding a project on a remote host, the desktop now also sends the host's default agent (first authorized one in the default priority) in the deprecated worker/orchestrator agent fields. Current daemons strip those fields on write, so nothing changes for them. If the agent list cannot be read, nothing extra is sent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ent-ui Conflict resolutions keep main's new work and this branch's removal of project agent and model setup: - keep main's session import, settings layout, icons, actions slot, docs renames and the new provisioning test - drop main's additions that read the removed project pins: the effort inheritance test, the agent retry test, workspace.orchestratorAgent reads (fall back to the orchestrator session's own agent) - useProjectDefaultWorker and the project agent e2e spec stay deleted - tests use main's "Orchestrator agent approval" label Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Collaborator
Author
|
Closing in favor of #8252. Rather than removing project agent settings, new projects now start on the most preferred agent and can still be changed in project settings. The branch is kept for reference. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes for users
Creating a local project no longer asks for a worker agent, an orchestrator agent or models. Pick a folder and the project is created, then you land in the orchestrator chat. Local project settings lose the agent and model pickers. An agent is chosen per session and can be switched at any time.
Defaults follow the same order as PR 1: the remembered ready agent, else the first ready one in claude-code, codex, cursor, opencode.
Stacked on #7711. Review that first. Only the local app changes; cloud projects and the mobile app keep their current agent setup.
What was removed
useProjectDefaultWorker, and theorchestratorAgentfield on workspace summaries.model,effortandmodeno longer reach a session. Project config contributes permissions only.Summary.OrchestratorAgentandDefaultWorkerReviewerare gone, and legacy import no longer maps agent or model.--worker-agentand--orchestrator-agentare hidden, deprecated no-ops.Compatibility
DisallowUnknownFields, so the legacyagent,model,effortandmodefields stay in the schema. They are ignored and stripped on create, update and set-config. Deleting them is a later breaking-API cleanup.Review notes
🤖 Generated with Claude Code