Repository navigation
Conversation
An admin can now give the Issues agent and the PR agent a provider, model and effort of their own, in Settings - Workers, instead of always starting on the office's default worker. The Queue agent keeps running on the default, as do the tasks it adds. Choices are validated the way the default worker's are, kept in .agent-office/prompts.json, and one the office can no longer start is forgotten on the next boot. The first prompt at a board hires its agent on the choice made for that station, and the sign-in gate follows the provider picked.
dextah
added a commit
to dextah/agent-office
that referenced
this pull request
Oct 22, 2026
… approvals) for workers (#2) * Configurable providers for the PR and Issues board agents An admin can now give the Issues agent and the PR agent a provider, model and effort of their own, in Settings - Workers, instead of always starting on the office's default worker. The Queue agent keeps running on the default, as do the tasks it adds. Choices are validated the way the default worker's are, kept in .agent-office/prompts.json, and one the office can no longer start is forgotten on the next boot. The first prompt at a board hires its agent on the choice made for that station, and the sign-in gate follows the provider picked. * Yolo (skip approvals) for hired workers, the default worker and the board agents A "Yolo (skip approvals)" box under the provider in the hire dialog, the default worker and the Issues/PR agents' rows in Settings - Workers. Each provider's row in shared/providers.ts names its CLI's flag, and its adapter puts it on the command line through server/yolo.ts, on resume too: Claude Code --dangerously-skip-permissions, Codex --dangerously-bypass-approvals-and-sandbox (any -a/--ask-for-approval dropped, which Codex refuses alongside it), Cursor --force, Muse --yolo. A flag --agent-args already has, or an alias of it, isn't added twice. Providers without one grey the box out, and the server rejects it there. It's validated with the model and effort (prompts.json, workers.json, the spawn), admin-only where those settings are, toasted to everyone, and a worker in yolo wears a "Yolo" badge on its card, the workers list and its terminal title. A Claude worker in yolo gets hook settings with skipDangerousModePermissionPrompt, so Claude's first-run Bypass Permissions screen doesn't hold it up; if it shows anyway the desk says so. Also folds the copies of a pick in prompts.ts into one helper, and the two settings handlers' parsing of a pick into one. Co-authored-by: chrisbewz <crisbewz@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Keep the yolo box's label on one line with its flag base.css's .modal label made it a block, so the flag ran into the label. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: chrisbewz <crisbewz@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
The Issues agent and the PR agent can now each run on a provider of their own. An admin picks a provider, model and effort for either in ⚙️ Settings → 🤖 Workers (a line per agent under the Default worker, with ✏️ Edit and ↺ Use the default). The Queue agent, and the tasks it adds, always run on the office's default worker, as before.
How
PromptsState.stations(protocol): what theissuesandpullsagents start on, by station kind, kept in.agent-office/prompts.jsonbeside the default worker. A newprompts.stationadmin message sets one or puts it back on the default (ConfigurableStation = Exclude<StationKind, 'queue'>makes the queue agent unaddressable by type).OfficePrompts.station/setStationvalidate a choice exactly assetAgentdoes (provider known, custom only when configured, model and effort checked); one the office can no longer start is forgotten on restore.WorkerManager.station()spawns the board agent onstationChoice(kind, prompts, officeDefault)(src/server/stations.ts) — its own pick, else the office default. Thestation.promptsign-in gate follows the resolved provider.ui/settings-boards.ts(reuses theagentFieldspicker), wired into the Workers pane;settings.tsgrew 8 lines (547/600), and the size guard holds —workers/manager.tsstayed at exactly its 1029-line ceiling (the spawn change swaps one line for one).Verification
npm run typecheck— clean (server + client).852e2abwithout this diff, and server-dispatch passes once commit signing is disabled. Not caused by this change.npm run build— clean (vite + tsc).