Repository navigation
Replies: 4 comments 2 replies
|
This is an Auggie CLI version mismatch, not a gateway problem. OmniRoute starts Auggie as I installed both from npm to check:
Until OmniRoute updates the args, go back to the 0.x line: If you want to keep 1.2 installed for your own use, install 0.37.1 somewhere else and point OmniRoute at it with The real fix is dropping |
|
@Addy-95 @dylanpulver's diagnosis is right. I looked inside both npm packages. The 0.37.1 CLI still has I've opened #20250 to drop the flag and check that the 1.2 output still parses. Until that ships, the workaround above holds. Run |
|
thanks for the help @diegosouzapw @dylanpulver . |
|
Glad it's sorted, @Addy-95. If the 0.37.1 downgrade got it working, mark @dylanpulver's comment as the Answer (the check mark on the comment) so the next person with this error finds it faster. The fix itself is tracked in #20250. |
Uh oh!
There was an error while loading. Please reload this page.
message: Gateway returned HTTP 502
httpStatus: 502
requestUrl: http://localhost:20128/v1/v1/messages
probedModel: aug/haiku4.5
responseBody: {"error":{"message":"[502]: Auggie CLI exited with code 1: Error: Unknown option: --quiet","type":"server_error","code":"bad_gateway"}}
endpoint: http://localhost:20128/
checkedAt: 2026-11-14T13:21:10.658Z
All reactions