bd/gc dolt port env var mismatch: GC_DOLT_PORT vs BEADS_DOLT_PORT

[alexsiri7]

Problem

When gascity starts its dolt server, it assigns a dynamic port and injects GC_DOLT_PORT into agent tmux sessions. However, bd (beads CLI) reads BEADS_DOLT_PORT for the dolt server port, defaulting to 3307 if unset.

This means agents running inside gascity sessions cannot use bd commands without manually bridging the env var gap.

Reproduction

1. gc init --provider claude && gc start
2. gc rig add /path/to/repo --include packs/gastown
3. Inside the rig directory: bd list → fails with "Dolt server unreachable at 127.0.0.1:3307"
4. BEADS_DOLT_PORT=$GC_DOLT_PORT bd list → works

Related issues

• gc rig add calls bd init --server but doesn't pass --server-port with the actual dolt port. It works if BEADS_DOLT_PORT is exported in the shell before running gc rig add.
• bd init --server --server-port <port> doesn't persist the port into metadata.json. Only BEADS_DOLT_PORT env var works at runtime.
• The dolt_server_port field in .beads/metadata.json is set by bd dolt set port but ignored by bd's connection logic.

Expected behavior

Either:

1. gascity should inject both GC_DOLT_PORT and BEADS_DOLT_PORT into agent sessions, OR
2. bd should read GC_DOLT_PORT as a fallback, OR
3. gc rig add should persist the port in a way that bd reads it (e.g. write BEADS_DOLT_PORT to the session env or use bd dolt set port)

Workaround

Set BEADS_DOLT_PORT in tmux session environment for all sessions:

for s in $(tmux -L gc list-sessions -F '#{session_name}'); do
  tmux -L gc set-environment -t "$s" BEADS_DOLT_PORT $(tmux -L gc show-environment -t "$s" GC_DOLT_PORT 2>/dev/null | cut -d= -f2)
done

Environment

• gc v0.13.5
• bd v0.63.3
• dolt v1.83.6

[julianknutsen]

Wasteland sync — tracked as w-7492f67452

Field	Value
Wanted ID	w-7492f67452
Status	open
Upstream	hop/wl-commons

Last updated by Wendy patrol — 2026-04-09T12:30Z

[Rome-1]

Tracing this against current main — I believe this is already resolved by PR #344 (commit 32a2816, 2026-04-05), which landed shortly after the issue was filed.

Main concern — env var injection into agent sessions:

sessionDoltEnv in cmd/gc/template_resolve.go:316-388 now injects both GC_DOLT_PORT and BEADS_DOLT_SERVER_PORT (plus BEADS_DOLT_SERVER_HOST/USER and BEADS_DOLT_PASSWORD) into every agent tmux session. template_resolve.go:219 wires it into the agent env built in template_resolve.go:192-253, which feeds into runtime.Config.Env and reaches tmux via NewSessionWithCommandAndEnv (internal/runtime/tmux/tmux.go:286).

Beads reads BEADS_DOLT_SERVER_PORT first with BEADS_DOLT_PORT as legacy fallback since beads v0.58.0 (gastownhall/beads commit 9c903d06, Feb 2026). Gas City's minimum supported bd is v0.61.0 (cmd/gc/init_provider_readiness.go:436), so every supported bd version reads the var gc injects.

Related concerns from the issue body:

1. "gc rig add calls bd init --server but doesn't pass --server-port" — cmd/gc/gc-beads-bd:977 now passes --server-port "$DOLT_PORT" explicitly.

2. "bd init --server --server-port <port> doesn't persist the port into metadata.json" — this is bd-side behavior; beads reads the port env var first regardless, so gc's env injection makes it moot.

If the reproduction in this issue still fails on current main, happy to dig further — but a quick repro on my end (gc main, bd v1.0.0 pin from deps.env) runs bd list inside rig sessions without the workaround. Suggesting this can be closed.