Skip to content

config command accidentally removed in refactoring? #151

@ianmuscat

Description

@ianmuscat

The btca config model command documented in the README website was accidentally removed in commit 69b4888, breaking the getting started flow. The command implementation seems to still exists, but it does not seem to be registered in the main CLI program.

Steps to reproduce

  1. Install btca

    bun add -g btca opencode-ai
  2. Run the command from the README:

    btca config model --provider opencode --model claude-haiku-4-5
  3. Expected: The model/provider configuration is updated and a success message is shown.

  4. Actual: The command is not recognized. (Note: due to a separate issue, unrecognized commands silently launch the TUI instead of showing an error.)

Root cause

It seems that configCommand was (accidentally?) removed in commit 69b4888 during a refactoring that reorganized commands

69b4888#diff-4565ec586fe8103913bc7f7abc9b548cb8f4d8403669752a5f10874118093bceL32-L38

Workaround

I managed to use btca connect with short flags as an alternative, however, this doesn't provide the full functionality of config, which also includes resource management subcommands, so I currently can't use this tool.

btca connect -p opencode -m claude-haiku-4-5

Environment

  • btca version: latest from npm
  • Tested on: macOS (but likely affects all platforms)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions