[FEATURE] BAD DESIGN PRACTICE AND CONTEXT USAGE DRAIN

Resolved 💬 6 comments Opened Feb 13, 2026 by IreGaddr Closed Mar 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

this app has downgraded its ability to perform on large code bases if you do not have have a 10x or 20x plan with opus. HERE'S THE STUPIDITY OF DESIGN AND TOKEN WASTAGE---CURRENTLY THE APP WHEN YOU ASK IT TO CHANGE A FEATURE WILL HAVE THE MODEL "EXPLORE" THE CODE BASE--IN LARGE CODE BASES THIS CAN BE 70-120K TOKENS GONE. THEN IT ENTERS PLAN MODE WITHOUT YOU ASKING IT TOO. 20K TOKENS GONE. WHY IS THE DEFAULT OPTION AFTER IT CREATES THE PLAN TO WIPE THE CONTEXT???? SO IT THEN HAS TO EXPLORE AGAIN??? SERIOUSLY THIS IS BAD PRACTICE AND THE MODEL WILL NEVER GET ANYTHING DONE DUE TO COMPACTION/CONTEXT USAGE FOR WEEKLY/5 HR LIMITS BEING HIT QUICKLY

Proposed Solution

FUCK YOUR EXPLORE AN AUTO PLAN ==REMOVE THE MODEL ENTERING IN TO PLANNING MODE WITHOUT MY EXPLICIT DIRECTION.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗