[Bug]: auggie silently exits after 3 seconds

[jeremyheld-hs]

What happened?

When I run auggie or auggie login, the command seems to execute for about 3 seconds, then exits, without output

What did you expect to happen?

The command should produce an output

Steps to reproduce

• Open bash shell
• Download the latest auggie release from GitHub Releases (in my case version 0.28)
• Run auggie or auggie login

Auggie version

0.28

Request ID

No error

Environment details

Environment

• OS: Ubuntu 24.04 on WSL 2
• Shell: Bash
• Tool/CLI version: Auggie 0.28

Anything else we need to know?

The help command works fine: auggie --help displays the help

Is there any way of starting the app in verbose or debug mode to troubleshoot the issue ?

[harjothkhara]

Reproduced the exact symptom — ~3s, then silent exit, no output — and isolated it to the standalone GitHub-Releases binary vs the npm package.

Repro (macOS, auggie-darwin-x64 v0.28.0 — same release channel as the reporter's auggie-linux-x64)

Run bare auggie (or auggie login) with stdin that isn't a raw-mode TTY (here </dev/null, which mimics the WSL2 / non-interactive case):

Build, identical non-TTY stdin	Exit	Output	Time
Standalone binary auggie-darwin-x64 (bare & login)	0	0 bytes — silent	~2.8–3.7s
npm @augmentcode/auggie (same condition)	1	clear message (below)	instant

The npm build, in the identical condition, prints:

Interactive mode requires a terminal with raw mode support.
Automatically switching to print mode (--print).
To avoid this message:
  • Use --print flag explicitly for non-interactive environments
  • Ensure stdin is connected to a proper TTY

So the underlying trigger is no raw-mode TTY (common on some WSL2 / SSH / piped setups), and the actual bug is that the standalone binaries suppress this diagnostic and exit 0 instead of printing it and exiting non-zero. auggie --help works because it short-circuits before the interactive path; --version prints fine, so the binary's stdio isn't globally broken — only the interactive/non-TTY branch is silent.

Workarounds for @jeremyheld-hs (any one)

1. Install via npm instead of the Releases binary — it surfaces the real message: npm install -g @augmentcode/auggie (needs Node 22+).
2. Run non-interactively with --print, e.g. auggie --print "your prompt".
3. Use a terminal/stdin that supports raw mode (a native interactive TTY).

Suggested fix

Have the standalone binaries emit the same raw-mode/"switching to print mode" message the npm build already produces (and exit non-zero) instead of exiting 0 with no output — likely an stdout/stderr flush or logger-wiring difference in the packaged build.

---

Note: reproduced on the darwin-x64 binary rather than linux-x64; the npm-vs-standalone differential is the key signal. @jeremyheld-hs — confirming whether the npm install behaves correctly on your WSL2 would pin it down.

[jeremyheld-hs]

The version installed with npm works