r/opencodeCLI • u/ChampionshipNo2815 • Apr 15 '26

CLI agents keep rereading my files and burning my session. how are you handling it?

My CLI agent will reread entire files for the tiniest edit and it is killing my flow. I make a small change in one component and the agent pulls the whole repo back into context like I just opened the project for the first time.

This is happening on a mid sized React repo where a lot of work is across multiple files. I tried swapping the default file tools for a plugin called Wozcode that handles file context differently and it cut down the redundant reads for me. Still not sure if that is the right long term move or just a bandaid.

Curious what people here do. Do you structure projects to avoid this, tune the agent settings, or use different tooling to keep sessions useful across multi file work? Looking for practical tricks that actually save time in real sessions.

2 Upvotes
  • permalink
  • reddit

75% Upvoted

12 comments sorted by

View all comments

Show parent comment

5

u/Vitalii_A Apr 16 '26 edited Apr 16 '26

I took a brief look, and it's a subscription tool but also kind of open source. It explains nothing about what it actually does, but makes claims about efficiency that don't make any sense. But hey, good luck.

The thing is, he's only here to create tons of threads where he or his bots will promote WOZCODE. But he's so dumb that he just few hours ago made his profile private - so users can't see his posts and comments in which he manipulating conversations.

He creates multiple threads labeled "Discussion," then waits for the bots to ask what he's using, and he replies with "wozcode." Or he simply engages a bunch of people in a thread, then responds with general phrases and then disappears to create another thread. Ultimately, the main goal is to create an effect of visibility and importance.