Problem:
When passing boolean flags like --continue and --resume to Claude Code
through ccr, they were incorrectly transformed to "--continue true" and
"--resume true". Claude Code expects these as standalone flags without
values, causing them to not be recognized.
Solution:
Modified the argument reconstruction logic in codeCommand.ts to check if
a flag value is boolean true. Boolean flags are now passed without values
(e.g., "--continue"), while non-boolean flags retain their values
(e.g., "--option value").
The previous null‑ish coalescing treated empty strings as a valid value, which could result in an invalid path. Switching to logical OR keeps the precedence (config > env) but now falls back to the default `claude`
- Add LOG_LEVEL configuration option to control logging verbosity
- Update UI to include LOG_LEVEL dropdown in settings
- Fix logging inconsistency between environment variables and config file
- Unify logging configuration to use config file settings
- Maintain separate logging systems for different purposes:
* Server-level logs (HTTP requests, API calls) using pino in ~/.claude-code-router/logs/
* Application-level logs (routing decisions, business logic) in ~/.claude-code-router/claude-code-router.log
- Update documentation with accurate logging system information
- Add detailed information about dual logging systems in README.md and README_zh.md
- Improve type safety and validation in ConfigProvider
Co-authored-by: qwen-cli <https://github.com/QwenLM/qwen-code>
musistudio
TonyGeezandGitHub
user.name
TonyGeez
小星虎andGitHub
Robin Chiu
Nico Thomaier
BigUncleandqwen-cli <https://github.com/QwenLM/qwen-code>