larksuite / larksuite/cli

Install with user level terminal result in missing PATH in Codex

Open
#2,626 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
17.3k
Forks
1.4k
Avg merge
2d 4h
Merged PRs (30d)
105

Description

I used the command:

npx @larksuite/cli@latest install

but in ChatGPT(Codex) APP, it says cannot find lark-cli.

lark-cli installs and runs fine in a normal PowerShell/cmd, but is not found in restricted/sandboxed shells such as
the OpenAI Codex desktop app on Windows. The root cause: the npm global bin directory (%APPDATA%\npm) is added to the
user-level Path only, while sandboxed shells inherit only the machine-level Path. Node itself works in Codex because
C:\Program Files\nodejs\ is on the machine PATH; lark-cli does not, because its install dir is user-scoped.

This makes the CLI effectively unusable from these shells, with no hint about why.

Environment

  • OS: Windows 11 Enterprise, build 10.0.26200
  • Package: @larksuite/cli 1.0.93
  • Node: v24.18.0 · npm: 11.16.0 (global prefix C:\Users...\AppData\Roaming\npm)
  • Install: npm install -g @larksuite/cli → shims installed to C:\Users...\AppData\Roaming\npm\lark-cli.cmd /
    .ps1
  • Repro environment: OpenAI Codex desktop app (sandboxed shell)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing npx @larksuite/cli@latest install on Windows, then compare the user-level npm bin path with the environment inherited by the Codex sandbox. The issue names no source file or test, so trace the Windows installation and CLI entry points first. Done means the installed lark-cli is discoverable there, or the installation clearly explains the PATH limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, node.js
Domain
cli, developer-experience, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.