4 ms·

Claude Code allegedly auto-includes the currently active file and often all visible tabs and sometimes neighboring files it thinks are 'related' - on every prom

Claude Code allegedly auto-includes the currently active file and often all visible tabs and sometimes neighboring files it thinks are 'related' - on every prompt. The advice I got when scouring the internets was primarily to close everything except the file you’re editing and maybe one reference file (before asking Claude anything). For added effect add something like 'Only use the currently open file. Do not read or reference any other files' to the prompt. I don't have any hard facts to back this up, but I'm sure going to try it myself tomorrow (when my weekly cap is lifted ...).

sigseg1v 9mo ago
What does "all visible tabs" mean in the context of Claude Code in a terminal window? Are you saying it's reading other terminals open on the system? Also how do you determine "currently active file"? It just greps files as needed.
- adobrawy 9mo ago
  You can install VSCode extension and use "/ide" to connect them.
  - withinboredom 9mo ago
    Do people actually use this mode? Having to approve diffs in the ide is too annoying.
    - solumunus 9mo ago
      Depends on my task. If it’s complex and my expectation is for Claude to get things wrong the diff preview is helpful.
      - vidarh 9mo ago
        Even then, I'd wait until it's had a chance to iterate and correct itself in a loop before I'd even consider looking at the output, or I end up babysitting it to prevent it from making mistakes it'd often recognise and fix itself if given the chance.
        solumunus 9mo ago
        True. I’ve been strictly in the terminal for weeks and I have a stop hook which commits each iteration after successful rust compilation and frontend typechecks, then I have a small command line tool to quickly review last commit. It’s a pretty good flow!
    - HumanOstrich 8mo ago
      You can tell it not to do that and it will show inline diffs.
- DANmode 8mo ago
  13 days ago on HN: https://news.ycombinator.com/item?id=46566292 https://news.ycombinator.com/item?id=46566292
idonotknowwhy 8mo ago
Yes, it does exactly that. It also sends other prompts like generating 3 options to choose from, prefilling a reply like 'compile the code', etc. (I can confirm this because I connect CC to llama.cpp and use it with GLM-4.7. I see all these requests/prompts in the llama-server verbose log.) You can stop most of this with export DISABLE_NON_ESSENTIAL_MODEL_CALLS=1 And might as well disable telemetry, etc: export CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 I also noticed every time you start CC, it sends off > 10k tokens preparing the different agents. So try not to close / re-open it too often. source: https://code.claude.com/docs/en/settings https://code.claude.com/docs/en/settings
- JLCarveth 8mo ago
  I would always close claude to start a new chat... Guess I should stop doing that. Thanks for bringing my attention to those two env vars.

sigseg1v 9mo ago

What does "all visible tabs" mean in the context of Claude Code in a terminal window? Are you saying it's reading other terminals open on the system? Also how do you determine "currently active file"? It just greps files as needed.

adobrawy 9mo ago
You can install VSCode extension and use "/ide" to connect them.
- withinboredom 9mo ago
  Do people actually use this mode? Having to approve diffs in the ide is too annoying.
  - solumunus 9mo ago
    Depends on my task. If it’s complex and my expectation is for Claude to get things wrong the diff preview is helpful.
    - vidarh 9mo ago
      Even then, I'd wait until it's had a chance to iterate and correct itself in a loop before I'd even consider looking at the output, or I end up babysitting it to prevent it from making mistakes it'd often recognise and fix itself if given the chance.
      - solumunus 9mo ago
        True. I’ve been strictly in the terminal for weeks and I have a stop hook which commits each iteration after successful rust compilation and frontend typechecks, then I have a small command line tool to quickly review last commit. It’s a pretty good flow!
  - HumanOstrich 8mo ago
    You can tell it not to do that and it will show inline diffs.
DANmode 8mo ago
13 days ago on HN: https://news.ycombinator.com/item?id=46566292 https://news.ycombinator.com/item?id=46566292

idonotknowwhy 8mo ago

Yes, it does exactly that. It also sends other prompts like generating 3 options to choose from, prefilling a reply like 'compile the code', etc. (I can confirm this because I connect CC to llama.cpp and use it with GLM-4.7. I see all these requests/prompts in the llama-server verbose log.) You can stop most of this with export DISABLE_NON_ESSENTIAL_MODEL_CALLS=1 And might as well disable telemetry, etc: export CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 I also noticed every time you start CC, it sends off > 10k tokens preparing the different agents. So try not to close / re-open it too often. source: https://code.claude.com/docs/en/settings https://code.claude.com/docs/en/settings

JLCarveth 8mo ago
I would always close claude to start a new chat... Guess I should stop doing that. Thanks for bringing my attention to those two env vars.