Repository navigation
期望支持 token 直传 #129
Description
Activity
Thanks for the feedback! Direct token passthrough is currently in development and will be supported in an upcoming release, which should enable multi-user concurrent usage scenarios.
Stay tuned — we'll update this issue once it's available.
+1,token 直传对团队场景非常关键。
目前每个团队成员都得自己创建应用才能用 CLI,如果支持 token 直传,管理员就可以统一管理应用,成员拿到 token 即可使用,不用每人都走"建应用 → 配权限 → 审批"的完整流程。
这个能力对于把 lark-cli 推广给非技术同事来说是刚需,期待尽快发布。
相关讨论见 #234
- addeddomain/coreCLI framework and core librariesCLI framework and core libraries
on Apr 7, 2026 Thanks for the feedback and sorry for the wait! This has been shipped in v1.0.5. Please upgrade and let us know if it works for your use case. Closing this one out
@liangshuo-1 can I know what is your solution and how to use this new feature? I could not found any relevant information in the README and CHANGELOG.
Sorry for the missing docs! You can pass tokens directly via environment variables:
User identity
export LARKSUITE_CLI_APP_ID="cli_xxx"
export LARKSUITE_CLI_USER_ACCESS_TOKEN="u-xxx"
lark-cli contact +search-user --query "test"Bot identity
export LARKSUITE_CLI_APP_ID="cli_xxx"
export LARKSUITE_CLI_TENANT_ACCESS_TOKEN="t-xxx"
lark-cli im +send --receive-id-type open_id --receive-id ou_xxx --msg-type text --content '{"text":"hello"}'No config init or auth login needed — the CLI picks up env vars automatically.
We'll update the README with this usage. Thanks for flagging it!
LARKSUITE_CLI_USER_ACCESS_TOKEN 不是 2 小时过期么?
user access token 怎么获取呢 为啥 readme 文件没有更新
- added 2 commits that reference this issue
on Jul 28, 2026
CLI 封装好了命令,不想重复造轮子,能支持多用户并行使用就太好了。