gastownhall/beads · error

--team is not supported with --proxied-server

Error message

--team is not supported with --proxied-server

What it means

runInitProxiedServer rejects --team with --proxied-server. Team mode's shared-server assumptions conflict with proxied-server's managed external dolt binary, so the combination is rejected up front like the other flag conflicts.

Source

Thrown at cmd/bd/init_proxied_server.go:59

	skipHooks              bool
	skipAgents             bool
	reinitLocal            bool
	contributor            bool
	team                   bool
	teamServer             bool
	fromJSONL              bool
	nonInteractive         bool
}

func runInitProxiedServer(cmd *cobra.Command, ctx context.Context, in initProxiedServerInput) error {
	if in.fromJSONL {
		return fmt.Errorf("--from-jsonl is not supported with --proxied-server")
	}
	if in.contributor {
		return fmt.Errorf("--contributor is not supported with --proxied-server")
	}
	if in.team {
		return fmt.Errorf("--team is not supported with --proxied-server")
	}

	// Preflight the external dolt binary before any .beads/ write below
	// (checkExistingBeadsData onward). This only applies to managed
	// proxied-server mode (in.externalConfig == nil): external mode talks
	// to a remote/pre-existing dolt sql-server over the network and never
	// spawns a local dolt binary, so it has nothing to preflight here.
	// Failing here means a missing/broken dolt produces a clean preflight
	// error instead of a half-initialized .beads/ directory from a later
	// failure in newManagedProxiedServerUOWProvider.
	//
	// Shares resolveAndProbeDolt (uow_factory.go) with
	// newManagedProxiedServerUOWProvider, which this same `bd init
	// --proxied-server` invocation goes on to call a few lines below via
	// newProxiedServerUOWProvider: the shared doltVersionWarnOnce means the
	// version advisory prints at most once for the command, not once per
	// call site.
	if in.externalConfig == nil {

View on GitHub (pinned to 71377f2769)

Solutions

1. Remove --team when using --proxied-server.
2. Use `bd init --team` (without --proxied-server) for team-mode setup.
3. Pick exactly one init mode per invocation: local, team, contributor, or proxied-server.

Example fix

// before
bd init --proxied-server --team
// after
bd init --team   # or: bd init --proxied-server

if proxiedServer && team {
    return errors.New("--team cannot be combined with --proxied-server")
}

When it happens

Trigger: `bd init --proxied-server --team` — the team flag is set and rejected as the third validation check.

Common situations: Setting up a shared team database while opting into proxied-server mode, or script templates that always pass --team plus other mode flags.

Related errors

• invalid database name %q: %v
• invalid --role %q: must be "maintainer" or "contributor"
• --from-jsonl is not supported with --proxied-server
• --contributor is not supported with --proxied-server
• got %d close reasons for %d issue IDs; provide exactly one s

AI-assisted analysis of gastownhall/beads@71377f2769 (2026-08-30). Data as JSON: /api/errors/ee55b677eb297e5c. Report an issue: GitHub.