[Bug]: T3code cannot find the locally installed agy.

[Draqun]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

Hey. I wanted to work with T3Code, OpenCode, and Aga on Ubuntu 26.04.1 LTS.
It just so happens that it doesn't recognize the latter (see the screenshot for more details).
For some reason, my local ~/.local/bin directory is being ignored. Any advice on how to fix this?

Expected behavior

T3Code checks ~/.local/bin or allow setup custom PATH.

Actual behavior

It discover (I've hope it uses agents installed in system instead own copies) other tools installed in ~/.local/bin.

Impact

Blocks work completely

Version or commit

0.0.42

Environment

Ubuntu 26.04.1 LTS

Logs or stack traces

Screenshots, recordings, or supporting files

Workaround

No response

Best regards.
Draqun

[juliusmarminge]

Triage

Confirmed on current main and shipping 0.0.42. This is not a PATH / ~/.local/bin miss. T3 is looking for a different binary than agy.

What the code does

1. The Antigravity provider does not run the agy CLI.

Resolution in apps/server/src/provider/AntigravityInstallation.ts is:

1. an explicit Binary path override (must be the ACP executable)
2. else the managed runtime under the environment state dir
3. else agy_acp_server.par (Linux/macOS) or agy_acp_server.exe (Windows) on PATH, plus a sibling localharness_external

agy is never a candidate. Pointing Binary path at ~/.local/bin/agy also fails: fromExternal requires localharness_external next to the chosen file.

That is intentional. #9348 shipped Google’s official ACP agent, not the CLI. #3056 (drive antigravity-cli like Codex/Claude) was closed.

2. ~/.local/bin is already on the search path when the login shell has it.

• Desktop hydrates PATH from a login shell on Linux (DesktopShellEnvironment.ts).
• The server does the same on startup (os-jank.ts fixPath).
• Antigravity settings already have Binary path (“Custom ACP executable”).
• Docs already say Antigravity is installed from Settings and does not need a PATH CLI.

The screenshot itself shows OpenCode 1.18.2 authenticated. If other tools in ~/.local/bin are found, PATH hydration is working. agy is ignored because it is the wrong program, not because the directory is skipped.

Linux does not hardcode $HOME/.local/bin the way Windows adds %USERPROFILE%\.local\bin. That is a real platform gap for a login-shell probe failure, but it is not what this screenshot shows. Related open work: #5013 / #9232 (do not attribute this issue to them as the primary fix).

3. The status copy makes this look like a PATH bug.

getProviderSummary uses headline Not found and falls back to “CLI not detected on PATH.” For Antigravity the server message is the generic “not installed” line, so a user who just ran which agy reasonably files a PATH issue.

Open #10932 only changes that copy to clarify ACP vs CLI. It does not accept agy as a runtime.

4. The screenshot already has the intended setup path.

The Antigravity card shows Install Antigravity. On linux-x64 that downloads the ACP pair (agy_acp_server.par ~1.8 GB + localharness_external), then Sign in with Google. No agy on PATH is required.

Related, not duplicates

Work	Why it does not close this as filed
Open #10932	Status copy only — same confusion, different deliverable.
Merged #9348	ACP agent on purpose.
Closed #3056	CLI-as-provider request, declined.
#7360 / #9429	Windows User PATH / macOS login-shell refresh — different platforms, different triggers.
Open #5013 / #9232	systemd / known CLI dirs including ~/.local/bin — useful if login-shell hydrate fails; not this screenshot.

Workaround (unblock now)

1. Settings → Providers → Antigravity → Install Antigravity. Allow disk (linux-x64 archive ~650 MB, extracted runtime ~2 GB).
2. Wait until status is Installed, then Sign in with Google.
3. Manual ACP install is also valid: extract agy_acp_server.par and localharness_external into the same directory, set Binary path to the .par. Do not set it to agy.

Do not add a custom PATH setting or treat agy as the runtime.

Classification: not-a-bug for the PATH/agy ask · expected ACP-vs-CLI split; misleading Not found copy tracked by #10932
Labels: remove bug, needs-triage; add question, via-triage
Discord tags: skip (not actionable as the filed PATH defect)