Skip to content

Fix CLI banner model label#124

Closed
akseljoonas wants to merge 1 commit intomainfrom
codex/fix-cli-banner-model-label-20260425-232307
Closed

Fix CLI banner model label#124
akseljoonas wants to merge 1 commit intomainfrom
codex/fix-cli-banner-model-label-20260425-232307

Conversation

@akseljoonas
Copy link
Copy Markdown
Collaborator

Summary

  • load the CLI config before printing the startup banner
  • pass the loaded CLI model into print_banner()
  • remove the stale hardcoded Bedrock fallback label from the banner helper

Why

The CLI session already uses configs/cli_agent_config.json, but the startup banner still claimed the default model was Bedrock because it was printed before config load.

Testing

  • python -m compileall agent/main.py agent/utils/terminal_display.py

The CLI already reads direct Anthropic defaults from
configs/cli_agent_config.json, but the banner was rendered before that
config was loaded and fell back to a hardcoded Bedrock label. This made
startup output claim the CLI default was Bedrock even when the session
was actually using direct Anthropic.

Constraint: Startup UI must reflect the same model source the CLI session actually uses
Rejected: Keep the hardcoded Bedrock fallback in print_banner | it misreports the active CLI default
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Model labels shown in CLI startup/status UI should come from loaded config or live session state, not stale hardcoded defaults
Tested: python -m compileall agent/main.py agent/utils/terminal_display.py
Not-tested: Interactive manual CLI launch in this sandbox
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant