aws / aws/amazon-q-developer-cli
bug: Context overflow when reading large files
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again
### Operating system
MacOS 15.5
### Expected behaviour
Q should inspect file sizes before reading files to prevent overflowing the context window. The better solution is for the fs_read tool to refuse to read large files and adhere to a reasonable default which is user definable.
### Actual behaviour
Q gleefully shoots itself in the head 🤯🔫 , and then much of my context is lost in the summarization process.
### Steps to reproduce
Tell Q to read a ridiculously large log file. This happens to me when conductng code debugging and e2e testing.
### Environment
```yaml
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by locating the fs_read tool entry point and tracing how it handles large files. Reproduce the issue by asking Q to read a very large log file during debugging or end-to-end testing. Done means large reads are bounded or refused using a reasonable user-definable default, without losing the remaining context.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- ai, cli
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100