Skip to content

[Bug]: API Error: "invalidArgument: HTTP error: 400 Bad Request" #51

@rishitank

Description

@rishitank

What happened?

After a session has gone on for a while, I tend to get an error like API Error: "invalidArgument: HTTP error: 400 Bad Request" and I am unable to continue the session. The last thing the agent was doing was running a sed command and then the next response showed this error.

What did you expect to happen?

It should be able to continue the session without stopping or getting stuck or preventing further messages from going through.

Steps to reproduce

  • Have a long running session
  • Make it make edits, using the sed command
  • Eventually you get this issue

Auggie version

0.11.1

Request ID

37ed24f5-9b5e-4518-abdf-bef6bf8852fb

Environment details

Environment
  • OS: Mac OS 26.0.1
  • Shell: ZSH
  • Tool/CLI version: Auggie 0.11.1

Anything else we need to know?

It might be related, but it was making edits to a folder outside the current repository. Although it had no issues doing this before and so it seems a bit random.

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