Skip to content

[Bug]: auggie went off the deep end and sent tons of base64 encoded responses #77

@jwatte

Description

@jwatte

What happened?

My auggie --print "prompt" session went off the deep end, sending base64 encoded response, and then died.

What did you expect to happen?

I expected it to not send junk and to not die.

Steps to reproduce

Who knows?

Final bits:

QkicnYtcGFydG5lci1kb2NzLXBsYXlncm91bmQiOiBQYXJ0bmVyRG9jc1BsYXlncm91bmQ7
Cgl9Cn0K

❌ API Error: "augmentTooLarge: HTTP error: 413 Request Entity Too Large"
⎿ Request ID: 70e85c4f-973f-42a5-850f-03a2406b4723

Auggie version

0.15.0 (commit 8c3839b5)

Request ID

70e85c4f-973f-42a5-850f-03a2406b4723

Environment details

Environment
  • OS: linux debian trixie
  • Shell: bash
  • Tool/CLI version: 0.15.0 (commit 8c3839b5)

Anything else we need to know?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions