When I run Qwen on a computer that has the repo, I want the same thing I want for every local CLI provider:

• run the session where the code is
• check in from my phone
• handle approvals
• send one follow-up

The “gotcha” with providers like Qwen is usually not the model.

It’s the practical stuff:

• install location
• PATH
• conservative auth detection

This guide is the provider-specific setup that makes phone check-ins feel smooth and predictable.

TL;DR

1. Install Qwen CLI on the computer that will host sessions and verify it runs.
2. Authenticate Qwen on that computer.
3. Don’t over-interpret auth status: Qwen auth probing is conservative and may show Unknown.
4. If Qwen isn’t detected, set HAPPIER_QWEN_PATH to the absolute path of the qwen binary.
5. Use a phone-friendly session UI for a tight loop: check → approve → follow-up → leave.

The problem

If you can’t see the session state from your phone, you’ll do one of two things:

• remote into the computer (SSH/desktop) and get dragged into terminal work
• wait until you’re back at your keyboard

A good phone workflow avoids both.

What I tried first (and where I bounced off)

• SSH from phone

• remote desktop

• just waiting

• Happier: it gives you a phone UI for “check → approvals → one follow-up → leave.” Trade-off: it still depends on the computer running the session being online.

If you’re new to Happier (what it is, and where to get it)

If you haven’t seen Happier before: it’s an open-source companion app (mobile/web/desktop) for coding sessions.

Get set up:

• GitHub: https://github.com/happier-dev/happier
• Install/download: https://github.com/happier-dev/happier#how-it-works
• Discord: https://discord.gg/W6Pb8KuHfg

Step 1: install Qwen

From provider docs, verify Qwen runs on the host computer.

Step 2: auth (machine-local)

Qwen auth is machine-local.

If you have two computers, each one needs its own auth state.

Step 3: why auth may show “Unknown”

In the Happier agent auth probe config, Qwen uses an unknown parser.

Treat Unknown as “not safely probeable,” not “broken.”

Step 4: PATH override (HAPPIER_QWEN_PATH)

If Qwen is installed but not detected:

• set HAPPIER_QWEN_PATH

Step 5: phone loop + copy/paste follow-ups

The 2-minute loop (what I actually do)

1. open session
2. check approvals
3. send one follow-up
4. leave

I try not to do more than that from a phone.

Three follow-ups I reuse

Here are follow-ups that work well when I’m not at a keyboard.

(They’re intentionally simple. That’s the point.)

1. Checkpoint

Stop after your next step and summarize:

• what you changed
• what you didn’t change
• what you want to do next

2. Constraint

Don’t touch migrations/auth. If you think you need to, stop and ask.

3. Diff-first

Before you keep going, list the files you modified and why (one sentence each).