zlacker

[parent] [thread] 7 comments
1. sigseg+(OP)[view] [source] 2026-01-23 03:24:44
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.
replies(2): >>adobra+sd >>DANmod+Jm3
2. adobra+sd[view] [source] 2026-01-23 05:37:52
>>sigseg+(OP)
You can install VSCode extension and use "/ide" to connect them.
replies(1): >>within+Qk
◧◩
3. within+Qk[view] [source] [discussion] 2026-01-23 06:48:20
>>adobra+sd
Do people actually use this mode? Having to approve diffs in the ide is too annoying.
replies(2): >>solumu+Iq >>HumanO+dK1
◧◩◪
4. solumu+Iq[view] [source] [discussion] 2026-01-23 07:43:14
>>within+Qk
Depends on my task. If it’s complex and my expectation is for Claude to get things wrong the diff preview is helpful.
replies(1): >>vidarh+8y
◧◩◪◨
5. vidarh+8y[view] [source] [discussion] 2026-01-23 08:49:17
>>solumu+Iq
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.
replies(1): >>solumu+IP
◧◩◪◨⬒
6. solumu+IP[view] [source] [discussion] 2026-01-23 11:24:47
>>vidarh+8y
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!
◧◩◪
7. HumanO+dK1[view] [source] [discussion] 2026-01-23 16:51:10
>>within+Qk
You can tell it not to do that and it will show inline diffs.
8. DANmod+Jm3[view] [source] 2026-01-24 04:02:11
>>sigseg+(OP)
13 days ago on HN:

>>46566292

[go to top]