feat: support user identity for im +chat-create#242
Merged
YangJunzhou-01 merged 1 commit intolarksuite:mainfrom Apr 3, 2026
Merged
Conversation
github-actions
bot
added
domain/im
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughIm Changes
Sequence Diagram(s)sequenceDiagram
autonumber
participant CLI as CLI (+flags)
participant Runtime as Runtime/Auth
participant API as IM API
CLI->>Runtime: parse flags (`--as`, `--set-bot-manager`, `--dry-run`)
Runtime-->>CLI: resolve identity (bot or user)
CLI->>Runtime: validate flags (if `--set-bot-manager` require bot)
alt validation fails
Runtime-->>CLI: return validation error ("--set-bot-manager is only supported with bot identity")
else validation passes
CLI->>API: POST /im/chat.create (use identity token, include appropriate scope and set_bot_manager only when bot)
API-->>CLI: creation response or dry-run result
end
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Greptile SummaryThis PR adds Confidence Score: 5/5Safe to merge; the single remaining finding is a P2 defensive-code suggestion that does not affect current behavior. All prior review concerns (stale Scopes field, incomplete --query placeholder) are resolved. The only open finding is a minor inconsistency between DryRun and Execute that is fully guarded by validation, warranting no score reduction below 5. shortcuts/im/im_chat_create.go — Execute function's set_bot_manager guard is inconsistent with DryRun Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[lark-cli im +chat-create] --> B{--as flag}
B -->|bot / default| C[BotScopes: im:chat:create]
B -->|user| D[UserScopes: im:chat:create_by_user]
C --> E{Validate}
D --> E
E -->|--set-bot-manager + user| F[ErrValidation]
E -->|pass| G[Execute]
G --> H[POST /open-apis/im/v1/chats]
H --> I{set_bot_manager?}
I -->|Bool flag true| J[qp: set_bot_manager=true]
I -->|false| K[omit param]
J --> L[API Response]
K --> L
Reviews (8): Last reviewed commit: "feat: support user identity for im +chat..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Line 55: Update the documentation entry for the `--as <identity>` flag in
skills/lark-im/references/lark-im-chat-create.md to stop stating "default
`bot`"; instead indicate the identity is auto-detected (e.g., "auto-detected:
`user` when logged in, otherwise `bot`") where the table currently lists `bot`
as the default (the table cell containing "`--as <identity>` | No | `bot` or
`user` | Identity type (default `bot`)"). Make the same replacement for the
other occurrence of the default wording elsewhere in the file so both mentions
reflect the auto-detect behavior.
- Line 64: The example command "contact +search-user --query" is incomplete;
update the sentence to include a placeholder query value and a brief example so
users can run it directly—for example, show using an email or name as the query
(e.g., alice@example.com or "Alice Smith") and mention this returns the user's
open_id; edit the line containing contact +search-user --query to include that
placeholder and a short note about extracting open_id from the command output.
In `@skills/lark-im/SKILL.md`:
- Line 59: The two identity docs are inconsistent: update the section
referencing `chats.create` to match the `+chat-create` row (or vice versa) so
both state the same caller support (either "user/bot" or "bot-only"); locate the
table row for `+chat-create` and the descriptive paragraph that mentions
`chats.create` and make their wording identical about caller support and the
ability to create private/public chats and invite users/bots.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 24498786-2806-4318-bfd7-364e12966645
📒 Files selected for processing (3)
shortcuts/im/im_chat_create.goskills/lark-im/SKILL.mdskills/lark-im/references/lark-im-chat-create.md
shifengjuan-dev
changed the title
There was a problem hiding this comment.
🧹 Nitpick comments (1)
shortcuts/im/im_chat_create.go (1)
35-35: Clarify--set-bot-managerbehavior when using--as useridentity.The flag description ("set the bot that creates this chat as manager") assumes bot identity. The documentation lacks clarity on whether this flag works with
--as user, where a user (not a bot) is creating the chat. The code currently passes this parameter to the API unconditionally without validation or identity-aware logic.Update the flag description or documentation to clarify behavior per identity, or add validation to warn/prevent use with user identity if the API doesn't support it in that context.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@shortcuts/im/im_chat_create.go` at line 35, The flag description for "set-bot-manager" is ambiguous when the CLI is invoked with the "--as user" identity: update either the flag text in shortcuts/im/im_chat_create.go (the Name "set-bot-manager" flag) to explicitly state it only applies when creating the chat as a bot, or add identity-aware validation where the flag is parsed—detect the "--as" identity (user vs bot) and if "--as user" is used, either reject the flag with a clear error/warning or ignore it and log a warning before passing parameters to the API; ensure the change references the "set-bot-manager" flag and the "--as" identity handling code path so behavior is explicit and consistent.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@shortcuts/im/im_chat_create.go`:
- Line 35: The flag description for "set-bot-manager" is ambiguous when the CLI
is invoked with the "--as user" identity: update either the flag text in
shortcuts/im/im_chat_create.go (the Name "set-bot-manager" flag) to explicitly
state it only applies when creating the chat as a bot, or add identity-aware
validation where the flag is parsed—detect the "--as" identity (user vs bot) and
if "--as user" is used, either reject the flag with a clear error/warning or
ignore it and log a warning before passing parameters to the API; ensure the
change references the "set-bot-manager" flag and the "--as" identity handling
code path so behavior is explicit and consistent.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 75f7ba08-856e-459c-88c0-83496871b5f8
📒 Files selected for processing (2)
shortcuts/im/im_chat_create.goskills/lark-im/references/lark-im-chat-create.md
🚧 Files skipped from review as they are similar to previous changes (1)
- skills/lark-im/references/lark-im-chat-create.md
There was a problem hiding this comment.
🧹 Nitpick comments (2)
skills/lark-im/references/lark-im-chat-create.md (1)
33-34: Consider adding--as botto the--set-bot-managerexample for clarity.The example works because bot is the implicit default identity, but since line 59 explicitly states
--set-bot-manageris "only effective with--as bot," adding the flag would make the example self-documenting and avoid confusion.📝 Suggested doc fix
# Make the creating bot a group manager -lark-cli im +chat-create --name "My Group" --set-bot-manager +lark-cli im +chat-create --name "My Group" --set-bot-manager --as bot🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` around lines 33 - 34, Update the example command that makes the creating bot a group manager so it explicitly includes the identity flag by changing the invocation of the command shown as lark-cli im +chat-create --name "My Group" --set-bot-manager to include --as bot; locate the example in lark-im-chat-create.md (the line containing that command) and add the --as bot flag to the command so the sample is self-documenting and matches the note that --set-bot-manager is only effective with --as bot.shortcuts/im/im_chat_create.go (1)
37-51: Consider adding identity validation toDryRunfor consistency.The
Validatefunction correctly rejects--set-bot-managerwhen using user identity. However,DryRun(lines 37-47) will still render the request withset_bot_manager=trueeven when--as useris specified, which could confuse users into thinking the combination is valid.If
DryRunis intended to show "what would be sent regardless of validity," this is fine. Otherwise, consider adding the same check inDryRunor documenting that--dry-runbypasses validation.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@shortcuts/im/im_chat_create.go` around lines 37 - 51, DryRun currently always sets params["set_bot_manager"]=true when runtime.Bool("set-bot-manager") is true, which can mislead users when identity is not a bot; update the DryRun function (the DryRun closure) to mirror the Validate logic by checking runtime.Bool("set-bot-manager") && runtime.IsBot() and only add params["set_bot_manager"]=true when runtime.IsBot() is true (otherwise omit the key), using the same runtime.Bool("set-bot-manager") and runtime.IsBot() checks that Validate uses to keep DryRun consistent with validation.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@shortcuts/im/im_chat_create.go`:
- Around line 37-51: DryRun currently always sets params["set_bot_manager"]=true
when runtime.Bool("set-bot-manager") is true, which can mislead users when
identity is not a bot; update the DryRun function (the DryRun closure) to mirror
the Validate logic by checking runtime.Bool("set-bot-manager") &&
runtime.IsBot() and only add params["set_bot_manager"]=true when runtime.IsBot()
is true (otherwise omit the key), using the same runtime.Bool("set-bot-manager")
and runtime.IsBot() checks that Validate uses to keep DryRun consistent with
validation.
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Around line 33-34: Update the example command that makes the creating bot a
group manager so it explicitly includes the identity flag by changing the
invocation of the command shown as lark-cli im +chat-create --name "My Group"
--set-bot-manager to include --as bot; locate the example in
lark-im-chat-create.md (the line containing that command) and add the --as bot
flag to the command so the sample is self-documenting and matches the note that
--set-bot-manager is only effective with --as bot.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8ad75b72-3eb6-4098-82db-557e28764bb1
📒 Files selected for processing (3)
shortcuts/im/im_chat_create.goskills/lark-im/references/lark-im-chat-create.mdskills/lark-im/references/lark-im-chat-identity.md
✅ Files skipped from review due to trivial changes (1)
- skills/lark-im/references/lark-im-chat-identity.md
shifengjuan-dev
force-pushed
the
feat/support_uat_for_create_chat
branch
from
e598851 to
cf0bfab
Compare
|
|
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
skills/lark-im/references/lark-im-chat-create.md (1)
61-61:⚠️ Potential issue | 🟡 MinorDocument auto-detect behavior for --as parameter.
The PR objectives state "auto-detect picks user when logged in and bot when not," but the parameter table doesn't explain what happens when
--asis omitted. Users need to understand the default resolution logic.📝 Suggested documentation enhancement
-| `--as <identity>` | No | `bot` or `user` | Identity type | +| `--as <identity>` | No | `bot` or `user` | Identity type (auto-detected if omitted: `user` when logged in, otherwise `bot`) |🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` at line 61, Update the `--as` parameter documentation to explicitly state the auto-detect behavior when the flag is omitted: document that the CLI will auto-detect and use `user` when a user is logged in and `bot` when not, and show the default resolution (e.g., "`--as` omitted → auto-detect: `user` if logged in, otherwise `bot`"); ensure this text is added to the parameter table row for `--as` and optionally include a short note or example near the `--as` description to clarify the default.
🧹 Nitpick comments (3)
skills/lark-im/references/lark-im-chat-create.md (3)
59-59: Strengthen --set-bot-manager restriction wording.The phrase "only effective with" is weaker than the actual implementation, which validates and returns an error
"--set-bot-manager is only supported with bot identity (--as bot)"when used with user identity. Consider using "only supported with" to match the validation behavior.📝 Suggested wording improvement
-| `--set-bot-manager` | No | - | Set the creating bot as a group manager (only effective with `--as bot`) | +| `--set-bot-manager` | No | - | Set the creating bot as a group manager (only supported with `--as bot`) |🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` at line 59, Update the table row for the `--set-bot-manager` flag to match the runtime validation: replace the phrase "only effective with `--as bot`" with "only supported with bot identity (`--as bot`)" so the docs reflect the actual error message `"--set-bot-manager is only supported with bot identity (--as bot)"`; ensure the change is applied to the `--set-bot-manager` description in the file so wording aligns with the validation logic.
57-57: Consider cross-referencing detailed owner inference logic.The default owner behavior is correct, but users may benefit from a reference to the complete inference logic documented in
lark-im-chat-identity.md(lines 20-35), which covers edge cases like when a bot creates with/without--ownerspecified.📚 Suggested cross-reference
-| `--owner <open_id>` | No | Format `ou_xxx` | Owner open_id (defaults to the bot when using `--as bot`, or the authorized user when using `--as user`) | +| `--owner <open_id>` | No | Format `ou_xxx` | Owner open_id (defaults to the bot when using `--as bot`, or the authorized user when using `--as user`; see [lark-im-chat-identity.md](lark-im-chat-identity.md) for detailed inference logic) |🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` at line 57, Update the `--owner <open_id>` option description to include a short cross-reference to the detailed owner inference logic in lark-im-chat-identity.md so readers can inspect edge cases; explicitly mention that the default behavior (bot when `--as bot`, authorized user when `--as user`) is summarized here and link or point to lark-im-chat-identity.md for the full inference rules (see its owner inference section).
68-92: Consider reducing duplication with cross-reference.The two-step flow for error 232043 is documented both here and in
lark-im-chat-identity.md(lines 38-45). This creates a maintenance burden—updates must be synchronized. Consider providing a brief summary here with a cross-reference to the detailed guidance in the identity document.📚 Example cross-reference approach
-Bot cannot directly invite other users during group creation (error 232043). Use the **two-step flow** below. Do NOT pass other users' open_ids in `--users` during group creation. +When a bot creates a group and includes users who are mutually invisible to the bot in `--users`, the request fails with error 232043. See [lark-im-chat-identity.md](lark-im-chat-identity.md#inviting-members-during-group-creation) for the detailed two-step flow. Brief summary: 1. **Get the current user's open_id:** Run `lark-cli contact +search-user --query "<name or email>"` to retrieve it.Then shorten or remove steps 2-4 in favor of the cross-reference.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` around lines 68 - 92, Replace the full two-step flow for error 232043 with a concise summary and a cross-reference to the canonical detailed guidance in lark-im-chat-identity.md: keep a short note that bots cannot invite others during group creation (error 232043), that the workaround is a two-step flow (create group with the current user's open_id using the lark-cli im +chat-create command, then add other members via lark-cli im chat.members create as a user), and point readers to lark-im-chat-identity.md for the exact commands and details (including using succeed_type=1 and checking invalid_id_list); remove the duplicated step-by-step commands here to avoid maintenance drift.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Line 68: The sentence "Bot cannot directly invite other users during group
creation (error 232043)" is too absolute; change it to clarify scope by stating
that the restriction applies only when the bot and the users are not mutually
visible. Update the wording near the "two-step flow" guidance so it says bots
can invite users during creation if they are mutually visible, and otherwise
follow the two-step flow and do NOT pass other users' open_ids in `--users`;
keep the error code 232043 as the failure case when mutual visibility is not
present.
---
Duplicate comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Line 61: Update the `--as` parameter documentation to explicitly state the
auto-detect behavior when the flag is omitted: document that the CLI will
auto-detect and use `user` when a user is logged in and `bot` when not, and show
the default resolution (e.g., "`--as` omitted → auto-detect: `user` if logged
in, otherwise `bot`"); ensure this text is added to the parameter table row for
`--as` and optionally include a short note or example near the `--as`
description to clarify the default.
---
Nitpick comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Line 59: Update the table row for the `--set-bot-manager` flag to match the
runtime validation: replace the phrase "only effective with `--as bot`" with
"only supported with bot identity (`--as bot`)" so the docs reflect the actual
error message `"--set-bot-manager is only supported with bot identity (--as
bot)"`; ensure the change is applied to the `--set-bot-manager` description in
the file so wording aligns with the validation logic.
- Line 57: Update the `--owner <open_id>` option description to include a short
cross-reference to the detailed owner inference logic in
lark-im-chat-identity.md so readers can inspect edge cases; explicitly mention
that the default behavior (bot when `--as bot`, authorized user when `--as
user`) is summarized here and link or point to lark-im-chat-identity.md for the
full inference rules (see its owner inference section).
- Around line 68-92: Replace the full two-step flow for error 232043 with a
concise summary and a cross-reference to the canonical detailed guidance in
lark-im-chat-identity.md: keep a short note that bots cannot invite others
during group creation (error 232043), that the workaround is a two-step flow
(create group with the current user's open_id using the lark-cli im +chat-create
command, then add other members via lark-cli im chat.members create as a user),
and point readers to lark-im-chat-identity.md for the exact commands and details
(including using succeed_type=1 and checking invalid_id_list); remove the
duplicated step-by-step commands here to avoid maintenance drift.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5c57e88c-55f2-4d21-8e4d-623d3be55acb
📒 Files selected for processing (4)
shortcuts/im/im_chat_create.goskills/lark-im/SKILL.mdskills/lark-im/references/lark-im-chat-create.mdskills/lark-im/references/lark-im-chat-identity.md
✅ Files skipped from review due to trivial changes (1)
- skills/lark-im/references/lark-im-chat-identity.md
🚧 Files skipped from review as they are similar to previous changes (2)
- skills/lark-im/SKILL.md
- shortcuts/im/im_chat_create.go
shifengjuan-dev
force-pushed
the
feat/support_uat_for_create_chat
branch
2 times, most recently
from
694ae8d to
d7153bc
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
shortcuts/im/im_chat_create.go (1)
29-35:⚠️ Potential issue | 🟡 MinorUpdate the
--ownerhelp text for user mode.Line 33 still says omission defaults to the bot, so
lark-cli im +chat-create --helpnow contradicts the new--as userbehavior.📝 Suggested help-text fix
- {Name: "owner", Desc: "owner open_id (ou_xxx); defaults to the bot if not specified"}, + {Name: "owner", Desc: "owner open_id (ou_xxx); omit to use the API's default owner for the active identity"},🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@shortcuts/im/im_chat_create.go` around lines 29 - 35, The help text for the "--owner" flag (the entry with Name: "owner" in the flag definitions in shortcuts/im/im_chat_create.go) is outdated; change its Desc from "owner open_id (ou_xxx); defaults to the bot if not specified" to reflect the new --as behavior (e.g. indicate it defaults to the current user when running with "--as user", otherwise to the bot) so that lark-cli im +chat-create --help accurately describes owner selection.
♻️ Duplicate comments (1)
skills/lark-im/references/lark-im-chat-create.md (1)
66-68:⚠️ Potential issue | 🟠 MajorQualify the bot invite restriction.
Line 68 is still too absolute. Bots can invite users during creation when those users are mutually visible; error
232043is the mutually-invisible case. As written, this conflicts with the bot example above and pushes readers into the two-step flow unnecessarily.📝 Suggested wording
-Bot cannot directly invite other users during group creation (error 232043). Use the **two-step flow** below. Do NOT pass other users' open_ids in `--users` during group creation. +When a bot creates a group and includes users who are mutually invisible to the bot, the request fails with error 232043. Use the **two-step flow** below for that case. If the target users are visible to the bot, you can invite them directly during creation.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@skills/lark-im/references/lark-im-chat-create.md` around lines 66 - 68, The sentence under the "When using `--as bot`" section is too absolute; update the wording to qualify that bots cannot invite users during group creation only when those users are mutually invisible (error 232043) and that bots can invite mutually-visible users directly, so avoid telling readers to always use the two-step flow or to never pass other users' open_ids in `--users`; instead mention the mutually-visible exception, cite error 232043, and keep the guidance about the two-step flow for the mutually-invisible case.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Around line 57-59: Update the docs for the `--set-bot-manager` flag in
lark-im-chat-create.md to reflect runtime validation: change the note "only
effective with `--as bot`" to "only supported with `--as bot`" (or add a brief
note that the CLI will reject the flag when used with `--as user`), so the table
entry for `--set-bot-manager` accurately matches the behavior when using `--as
bot` vs `--as user`.
---
Outside diff comments:
In `@shortcuts/im/im_chat_create.go`:
- Around line 29-35: The help text for the "--owner" flag (the entry with Name:
"owner" in the flag definitions in shortcuts/im/im_chat_create.go) is outdated;
change its Desc from "owner open_id (ou_xxx); defaults to the bot if not
specified" to reflect the new --as behavior (e.g. indicate it defaults to the
current user when running with "--as user", otherwise to the bot) so that
lark-cli im +chat-create --help accurately describes owner selection.
---
Duplicate comments:
In `@skills/lark-im/references/lark-im-chat-create.md`:
- Around line 66-68: The sentence under the "When using `--as bot`" section is
too absolute; update the wording to qualify that bots cannot invite users during
group creation only when those users are mutually invisible (error 232043) and
that bots can invite mutually-visible users directly, so avoid telling readers
to always use the two-step flow or to never pass other users' open_ids in
`--users`; instead mention the mutually-visible exception, cite error 232043,
and keep the guidance about the two-step flow for the mutually-invisible case.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c9077349-429b-4c4a-8d29-c47fdb15c268
📒 Files selected for processing (4)
shortcuts/im/im_chat_create.goskills/lark-im/SKILL.mdskills/lark-im/references/lark-im-chat-create.mdskills/lark-im/references/lark-im-chat-identity.md
✅ Files skipped from review due to trivial changes (1)
- skills/lark-im/references/lark-im-chat-identity.md
🚧 Files skipped from review as they are similar to previous changes (1)
- skills/lark-im/SKILL.md
shifengjuan-dev
force-pushed
the
feat/support_uat_for_create_chat
branch
from
c79e930 to
202e2eb
Compare
YangJunzhou-01
previously approved these changes
Apr 3, 2026
🚀 PR Preview Install Guide🧰 CLI updatenpm i -g https://pkg.pr.new/larksuite/cli/@larksuite/cli@e9cc07bf561d2a8538910f8986d689016302d1fd🧩 Skill updatenpx skills add shifengjuan-dev/lark-cli#feat/support_uat_for_create_chat -y -g |
- Add --as user support to +chat-create - Add UserScopes (im:chat:create_by_user) / BotScopes (im:chat:create) - Update skill docs and reference files to reflect user/bot support - Default identity remains bot (first element of AuthTypes) Change-Id: I6be0a160567a0d87a92f176ae12297a11d06dcb1
shifengjuan-dev
force-pushed
the
feat/support_uat_for_create_chat
branch
from
202e2eb to
e9cc07b
Compare
github-actions
bot
added
size/L
YangJunzhou-01
approved these changes
Apr 3, 2026
Merged
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Change-Id: I6be0a160567a0d87a92f176ae12297a11d06dcb1
Summary
Allow
im +chat-createto run with user identity (UAT), so logged-in users can create group chats as themselves instead of always going through bot identity.Changes
--as usersupport to+chat-create"user"toAuthTypesinim_chat_create.goUserScopes: ["im:chat:create_by_user"]andBotScopes: ["im:chat:create"]to distinguish per-identity scopesSKILL.mdand reference doc to reflect user/bot supportAuthTypes)Test Plan
lark-cli im +chat-create --name "test" --as usercreates group with user identitylark-cli im +chat-create --name "test" --as botstill works as beforeSummary by CodeRabbit
New Features
Documentation