aws / aws/amazon-q-developer-cli

bug: Context overflow when reading large files

Offen
#2,187 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Rust
Sterne
2k
Forks
439
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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

```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
rust
Bereich
ai, cli
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.