Found while verifying archie-core-1786637491130-51-17a55e60's third acceptance criterion ('a non-interactive install still produces a valid config or fails loudly').
REPRODUCED
go run ./cmd/archied setup --defaults -config /tmp/ac3/config.toml -forge-type github -forge-secret-ref env:ARCHIE_GITHUB_TOKEN -provider openai -model ""
install.sh initialises CLOUD_MODEL="" and its cloud branch passes -provider openai -model "". archied setup's params() folds flags over the -defaults baseline and only overrides a field when the flag is non-empty, so an empty -model leaves the baseline's Model in place. That baseline is deliberately ollama-shaped: setup.go's defaultsParams comment says ollama is 'the only keyless provider, so an unattended install boots without a secret'. Pairing it with -provider openai therefore yields a model OpenAI does not serve.
WHY IT STILL PASSES THE CRITERION, AND STILL MATTERS
The config loads -- checked through the real loader (configuration.New(nil).File), not by eye -- so 'valid config or fails loudly' is satisfied in the letter. But the failure surfaces at the first chat turn against a daemon that reported a successful install, which is the same shape as the bug the installer bead was filed for: the installer's answers drifting from what the daemon needs.
NOT FIXED, because it needs a decision rather than a patch: what model an unattended cloud install should name is a product choice. Options --
setup owns a per-provider default model, alongside the baseline it already owns, so every non-interactive caller gets a coherent pair. Recommended: one source of truth, and it fixes the pairing for callers that are not install.sh.
install.sh refuses to choose: require a model flag (or an environment value) when the cloud path is taken without a TTY, and fail loudly, which is criterion 3's other arm.
install.sh stops passing -provider on the cloud path and leaves the baseline's ollama, which is honest but silently ignores that no OLLAMA is installed.
The deployments/*.toml templates each name their own model, so a fix should not invent a fourth source for them to drift from.
Imported from beads archie-core-6omt · GitHub #1167 · type bug · priority P3 · created 2026-09-21
Found while verifying archie-core-1786637491130-51-17a55e60's third acceptance criterion ('a non-interactive install still produces a valid config or fails loudly').
REPRODUCED
go run ./cmd/archied setup --defaults -config /tmp/ac3/config.toml -forge-type github -forge-secret-ref env:ARCHIE_GITHUB_TOKEN -provider openai -model ""
# exit 0, and the config it writes contains:
[models] # role -> ai-sdk runtime ref
triage = "openai/llama3"
planner = "openai/llama3"
builder = "openai/llama3"
WHY
install.sh initialises CLOUD_MODEL="" and its cloud branch passes -provider openai -model "". archied setup's params() folds flags over the -defaults baseline and only overrides a field when the flag is non-empty, so an empty -model leaves the baseline's Model in place. That baseline is deliberately ollama-shaped: setup.go's defaultsParams comment says ollama is 'the only keyless provider, so an unattended install boots without a secret'. Pairing it with -provider openai therefore yields a model OpenAI does not serve.
WHY IT STILL PASSES THE CRITERION, AND STILL MATTERS
The config loads -- checked through the real loader (configuration.New(nil).File), not by eye -- so 'valid config or fails loudly' is satisfied in the letter. But the failure surfaces at the first chat turn against a daemon that reported a successful install, which is the same shape as the bug the installer bead was filed for: the installer's answers drifting from what the daemon needs.
NOT FIXED, because it needs a decision rather than a patch: what model an unattended cloud install should name is a product choice. Options --
1. setup owns a per-provider default model, alongside the baseline it already owns, so every non-interactive caller gets a coherent pair. Recommended: one source of truth, and it fixes the pairing for callers that are not install.sh.
2. install.sh refuses to choose: require a model flag (or an environment value) when the cloud path is taken without a TTY, and fail loudly, which is criterion 3's other arm.
3. install.sh stops passing -provider on the cloud path and leaves the baseline's ollama, which is honest but silently ignores that no OLLAMA is installed.
The deployments/*.toml templates each name their own model, so a fix should not invent a fourth source for them to drift from.
---
_Imported from beads `archie-core-6omt` · GitHub #1167 · type bug · priority P3 · created 2026-09-21_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found while verifying archie-core-1786637491130-51-17a55e60's third acceptance criterion ('a non-interactive install still produces a valid config or fails loudly').
REPRODUCED
go run ./cmd/archied setup --defaults -config /tmp/ac3/config.toml -forge-type github -forge-secret-ref env:ARCHIE_GITHUB_TOKEN -provider openai -model ""
exit 0, and the config it writes contains:
[models] # role -> ai-sdk runtime ref
triage = "openai/llama3"
planner = "openai/llama3"
builder = "openai/llama3"
WHY
install.sh initialises CLOUD_MODEL="" and its cloud branch passes -provider openai -model "". archied setup's params() folds flags over the -defaults baseline and only overrides a field when the flag is non-empty, so an empty -model leaves the baseline's Model in place. That baseline is deliberately ollama-shaped: setup.go's defaultsParams comment says ollama is 'the only keyless provider, so an unattended install boots without a secret'. Pairing it with -provider openai therefore yields a model OpenAI does not serve.
WHY IT STILL PASSES THE CRITERION, AND STILL MATTERS
The config loads -- checked through the real loader (configuration.New(nil).File), not by eye -- so 'valid config or fails loudly' is satisfied in the letter. But the failure surfaces at the first chat turn against a daemon that reported a successful install, which is the same shape as the bug the installer bead was filed for: the installer's answers drifting from what the daemon needs.
NOT FIXED, because it needs a decision rather than a patch: what model an unattended cloud install should name is a product choice. Options --
The deployments/*.toml templates each name their own model, so a fix should not invent a fourth source for them to drift from.
Imported from beads
archie-core-6omt· GitHub #1167 · type bug · priority P3 · created 2026-09-21