Add --agent to runner setup so -y can run without a provider picker

[gtrrz-victor]

https://entire.io/gh/entireio/cli/trails/1254

Stacked on #2272. Addresses finding 1 on https://entire.io/gh/entireio/cli/trails/1239.

Why

-y answers setup's own questions, but the summary provider is resolved outside the mode decision. With no summary_generation.provider configured and several agents installed, a terminal still gets the provider picker after the defaults are created, so -y was not promptless.

What changed

• entire runner setup --agent <name> names the text-generation agent for this run. It takes the same override path as dispatch --local --agent: validated, used once, nothing written to settings.local.json.
• -y --agent codex opens no picker.
• --agent is rejected with --defaults-only and --print-prompt, which never call a provider. The check runs before the scaffold so a usage error leaves no files behind.
• One sentence in the Long help says when the picker appears and how --agent avoids it. The shared resolver is untouched, so explain --generate and dispatch behave as before.

Testing

Two tests in runner_setup_test.go. TestRunRunnerSetup_AgentFlagIsPromptless stubs the resolver's worst case (no configured provider, two candidates, terminal available) with the picker and the settings writer both failing the test if reached, and asserts the named agent is called once and no local settings are written. TestRunRunnerSetup_AgentRequiresAProviderMode pins the rejection for the two provider-free modes.

Runner and dispatch tests pass; golangci-lint v2 reports 0 issues on the package. The full-package TestRunUninstall_* failures on my machine are the known stale mise shim issue and reproduce on the base branch.

Follow-up

Once this lands, the -y flag help on runner_setup.go:138 should drop "without asking" or point at --agent, which closes the trail finding.

🤖 Generated with Claude Code

---

Note

Low Risk
CLI-only change to runner setup provider selection with validation before writes; shared resolver is reused, not modified.

Overview
entire runner setup now accepts --agent <name> so -y / --dry-run can pick a text-generation agent for tailoring without the interactive provider picker and without writing to settings.local.json.

Provider resolution switches from resolveCheckpointSummaryProvider to the shared resolveDispatchSummaryProvider path (same one-off override behavior as dispatch). --agent is rejected early for --defaults-only and --print-prompt, before any runner files are scaffolded. Command help documents when the picker appears and how --agent avoids it.

Tests cover promptless -y --agent (picker/settings save must not run) and invalid flag combinations.

^{Reviewed by Cursor Bugbot for commit b6446d5. Configure here.}

[Copilot]

🟡 Changes recommended

The new --agent help/usage messaging is misleading about when the flag is valid (it’s not strictly limited to --yes/--dry-run), so user-facing guidance should be corrected before approval.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Adds a one-off --agent override to entire runner setup so non-interactive flows (notably -y) can tailor runners without triggering the interactive provider picker or persisting a provider choice.

Changes:

• Add --agent <name> to runner setup and route provider resolution through resolveDispatchSummaryProvider(..., override) so the choice is validated/used once and not saved.
• Reject --agent for provider-free modes (--defaults-only, --print-prompt) before scaffolding to avoid leaving files behind on usage errors.
• Add tests to pin promptless -y --agent behavior and invalid flag combinations.

File summaries

File	Description
cmd/entire/cli/runner_setup.go	Adds the --agent flag, validates its compatibility with the chosen setup mode, and switches provider resolution to the shared dispatch resolver.
cmd/entire/cli/runner_setup_test.go	Adds coverage ensuring --agent avoids picker/persistence behavior and is rejected for modes that never call a provider.

Review details

Suppressed comments (1)

cmd/entire/cli/runner_setup.go:188

• The usage error for --agent currently tells users to "pass it with --yes or --dry-run", but the actual rule is that --agent only makes sense when tailoring runs, and it’s incompatible with provider-free modes like --defaults-only and --print-prompt. Tightening the message makes it clearer and avoids implying --yes/--dry-run are the only valid paths.

	if opts.agent != "" && !mode.needsProvider() {
		return errors.New("--agent only applies when setup calls a provider: pass it with --yes or --dry-run")
	}

• Files reviewed: 2/2 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.