GOOSE_CLI_SHOW_THINKING not working for DeepSeek model through OpenRouter
- 主要言語
- Rust
- スター
- 54.2k
- フォーク
- 6.2k
- 平均マージ
- 3日 4時間
- マージ済み PR(30日)
- 240
説明
**Describe the bug**
As the title says, after setting GOOSE_CLI_SHOW_THINKING=1 and then starting a session with DeepSeek V4 Flash 0731 (through OpenRouter), I do not see the thinking tokens in the CLI. I confirmed that the this model exposes reasoning tokens as navigating to the same session in the Goose Desktop App shows the "thinking" toggle which when clicked shows the reasoning tokens that are missing in the CLI.
---
**To Reproduce**
Steps to reproduce the behavior:
1. Start TTY and do export GOOSE_CLI_SHOW_THINKING=1
2. (Optional) goose configure in terminal and set your provider and model to open router -> DeepSeek V4 Flash 0731
3. Run goose session in the terminal and ask a question
---
**Expected behavior**
I should be able to see the same tokens that I see in the GUI in the terminal as well.
---
**Please provide the following information**
- **OS & Arch:** Fedora 44
- **Interface:** CLI
- **Version:** 1.45
- **Extensions enabled:** None
- **Provider & Model:** DeepSeek V4 Flash 0731 (through OpenRouter)
コントリビューションガイド
調査の方向性
Look for the CLI output handling code, likely in a module like `cli/src/output.rs` or `cli/src/session.rs`. Search for the environment variable `GOOSE_CLI_SHOW_THINKING` and how it controls the display of reasoning tokens. Compare the CLI's token handling with the desktop app's implementation to see where the DeepSeek/OpenRouter stream parsing differs. Run the CLI with debugging to trace the token flow.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- rust, shell
- 領域
- ai, cli
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 活発
- 明瞭さ
- 明確に書かれている
- 初心者へのやさしさ
- 65/100