Problem
Users cannot see what configuration is actually in effect. The config system supports TOML file defaults, environment variable overrides (CAT_*), and the values get merged at load time. When something behaves unexpectedly, there's no way to inspect the effective configuration without reading the source code.
What to do
Add a config (or config show) CLI command to src/context_analyzer_tool/cli.py that:
- Calls
load_config() and prints the result as a formatted Rich table or TOML
- Shows the config file path
- Optionally highlights values that differ from defaults (compare against
CATConfig() with no overrides)
Files to look at
src/context_analyzer_tool/config.py — config loading logic, CATConfig dataclasssrc/context_analyzer_tool/cli.py — where to add the new command (follow pattern of existing commands like health)
Why this is a good first issue
It's a self-contained addition — one new CLI command that calls an existing function and formats the output. No database, no async complexity.
Problem
Users cannot see what configuration is actually in effect. The config system supports TOML file defaults, environment variable overrides (
CAT_*), and the values get merged at load time. When something behaves unexpectedly, there's no way to inspect the effective configuration without reading the source code.What to do
Add a
config(orconfig show) CLI command tosrc/context_analyzer_tool/cli.pythat:load_config()and prints the result as a formatted Rich table or TOMLCATConfig()with no overrides)Files to look at
src/context_analyzer_tool/config.py— config loading logic,CATConfigdataclasssrc/context_analyzer_tool/cli.py— where to add the new command (follow pattern of existing commands likehealth)Why this is a good first issue
It's a self-contained addition — one new CLI command that calls an existing function and formats the output. No database, no async complexity.