CommandCodeAI / CommandCodeAI/command-code

<think> tags and "thought" leaks into transcript feed with qwen-3.7-plus

Open
#598 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

Description

Summary

I am building a spell checking mod with qwen-3.7-plus and several times (when context gets a big longer), the <think> end tag isn't parsed and thus "thought" leaks into the feed window of TUI:

✻ Thought for 4 seconds [ctrl+o to expand]

⠶ </think>



  The user wants me to continue. I need to fix the __dirname / import.meta issue. Since this is a mod that runs in Command Code's jiti environment, __dirname
  should be available. But the TypeScript checker is complaining because it doesn't know about the runtime environment.

  Let me simplify the _dirname resolution to just use __dirname since jiti provides it. Or I can use a different approach - use cmd.cwd which is the workspace
  root, and then resolve relative to that.

  Actually, looking at the mod-builder docs, mods are loaded by jiti which compiles TypeScript at load time. The __dirname should be available in that context.
  But the TypeScript checker doesn't know about it.

  Let me just use a simpler approach - declare __dirname as a global or use a try/catch approach. Or better yet, since the mod file and the dictionary file are in
   the same directory, I can use import.meta.url but that also has issues with TypeScript.

  The simplest fix is to just declare __dirname at the top of the file or use a different approach. Let me check what the mod-builder examples do.

  Actually, looking at the mod-builder skill instructions, it says mods are loaded by jiti which compiles TypeScript at load time. In a CommonJS context (which
  jiti uses), __dirname is available. The issue is just that TypeScript doesn't know about it.

  Let me just add a declaration at the top of the file or use a workaround. The simplest is to use process.cwd() or pass the path as a parameter.

  Actually, the best approach is to just use __dirname but declare it properly. Let me fix this.
  Now fix the __dirname issue — jiti provides __dirname at runtime, but TypeScript doesn't know about it:


───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Edit File .commandcode/mods/spell-checker.ts

 534 │ - const _dirname = typeof __dirname !== 'undefined'
 535 │ -  ? __dirname
 536 │ -  : dirname(fileURLToPath(import.meta.url));
 534 │ + // jiti (the mod loader) provides __dirname at runtime
 535 │ + declare const __dirname: string;
 536 │
 538 │ - const BUILTIN_DICTIONARY_PATH = join(_dirname, 'frequency_dictionary_en_82_765.txt');
 537 │ + const BUILTIN_DICTIONARY_PATH = join(__dirname, 'frequency_dictionary_en_82_765.txt');
Expected Behavior
  • model though is hidden behind expand ctrl+0
Actual Behavior

The </think> end tag is seen in the feed conversation transcript.

Steps to reproduce the issue
  1. Use qwen-3.7-plus
Command Code Version

1.4.6

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with qwen-3.7-plus and inspect the transcript feed's handling of blocks and their closing tags. Verify that the model's thought content is hidden behind the expand control and that no literal tag appears in the feed.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ai, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.