feat: add wenxin channel for openclaw#12298
Conversation
|
Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7bafe61649
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| conf, err := readOpenclawConfig(agent.ConfigPath) | ||
| if err != nil { | ||
| return err | ||
| } | ||
| appendPluginAllow(conf, pluginID) |
There was a problem hiding this comment.
plugins.entries after install
All of the existing plugin-backed channels in this file (setQQBotConfig, setWecomConfig, setDingTalkConfig, setFeishuPluginEnabled) mark their plugin under plugins.entries before the channel can be used, but the new Weixin flow only appends to plugins.allow. A repo-wide search for openclaw-weixin only finds this install path and the login command, so on OpenClaw configs that require an enabled plugins.entries.<id> for discovery, install+login will still leave Weixin unavailable and there is no later UI/API path to turn it on.
Useful? React with 👍 / 👎.
| const rules = reactive({ | ||
| name: [Rules.requiredInput], | ||
| name: [Rules.appName], | ||
| agentType: [Rules.requiredSelect], |
There was a problem hiding this comment.
Switching this field to Rules.appName narrows accepted names to the app-install regex, while the server still only requires dto.AgentCreateReq.Name to be non-empty (agent/app/dto/agents.go). That means users can no longer create agents with names that previously worked—such as names containing dots, spaces, CJK characters, or more than 30 characters—even though the backend duplicate checks and persistence still accept them.
Useful? React with 👍 / 👎.
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wanghe-fit2cloud The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
No description provided.