gastownhall/beads · error

--from-jsonl is not supported with --proxied-server

Error message

--from-jsonl is not supported with --proxied-server

What it means

runInitProxiedServer validates flag combinations up front: proxied-server mode manages its own data path and does not support importing from a JSONL export, so passing --from-jsonl together with --proxied-server returns this hard validation error before any writes.

Source

Thrown at cmd/bd/init_proxied_server.go:53

	serverRootPath         string
	serverProxyPort        int
	serverProxyIdleTimeout time.Duration
	externalConfig         *configfile.ExternalDoltConfig
	quiet                  bool
	stealth                bool
	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

View on GitHub (pinned to 71377f2769)

Solutions

1. Drop --from-jsonl when using --proxied-server and import data afterwards with a separate import command.
2. If you need JSONL import, use the regular (non-proxied-server) `bd init --from-jsonl`.
3. Choose one mode: proxied-server for remote managed dolt, local init for JSONL-based setup.

Example fix

// before
bd init --proxied-server --from-jsonl export.jsonl
// after
bd init --proxied-server
bd import -i export.jsonl

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

When it happens

Trigger: `bd init --proxied-server --from-jsonl <file>` — the fromJSONL input flag is set on initProxiedServerInput and rejected immediately.

Common situations: Copying an init command line used for local mode and appending --proxied-server, or scripting a migration from an existing JSONL export into a proxied-server setup.

Related errors

• invalid database name %q: %v
• invalid --role %q: must be "maintainer" or "contributor"
• --contributor is not supported with --proxied-server
• --team 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/82f2e04d534a26a4. Report an issue: GitHub.