Hi team, the extension automatically attaches full workspace and open-file co...
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Hi team, the extension automatically attaches full workspace and open-file context in the background on every request. This instantly causes a '413 Request too large' token limit error when using strict API providers like Groq's free tier. Please add an easily visible toggle in the chat UI to disable automatic context fetching, so we can stay under token limits by only manually tagging files
| Field | Value |
|---|---|
| App version | 1.1.14 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the /chat entry point and trace where full workspace and open-file context is automatically attached to requests. Add the visible chat toggle so users can disable automatic context fetching while retaining manual file tagging. Done means requests no longer include automatic context when the toggle is off, avoiding the reported token-limit error.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100