| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[mirror] openJiuwen-ai/agent-core#119: mango merge <!-- bot1-mirror-meta --> github_pr: 119 head_repo: LYA2333/agent-core head_ref: mango_branch head_sha: 88b01dffabc4a5b2ad07913f0961f956171b1f2e base_repo: openJiuwen-ai/agent-core base_ref: develop github_repo: openJiuwen-ai/agent-core base_branch: develop base_sha: 82e508116dc4b5d90f35d50ec0d4a1ebdae83129 github_user: LYA2333 <!-- /bot1-mirror-meta --> GitHub PR mirror for CodeArts CI. GitHub author: @LYA2333 GitHub PR: mango merge — https://github.com/openJiuwen-ai/agent-core/pull/119 | 2 个月前 | |
[mirror] openJiuwen-ai/agent-core#152: feat(example):merge perstream Paired: [GitHub #152](https://github.com/openJiuwen-ai/agent-core/pull/152) ↔ [GitCode !2099](https://gitcode.com/openJiuwen/agent-core/merge_requests/2099) <!-- bot1-mirror-meta --> github_pr: 152 head_repo: dashingsss/agent-core head_ref: push_Perstream head_sha: 1b3f749852b2de93721c230597be3dd64b4b678d base_repo: openJiuwen-ai/agent-core base_ref: develop github_repo: openJiuwen-ai/agent-core base_branch: develop base_sha: 91f4077bfb4bdcb79774e8a73a5048445f4dc960 github_user: dashingsss <!-- /bot1-mirror-meta --> GitHub PR mirror for CodeArts CI. <!-- bot1-source-body --> <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind feature **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes [#1417](https://gitcode.com/openJiuwen/agent-core/issues/1417) **What scenarios were tested, and what were the verification results（Function, performance, reliability, etc.）**： * Need to describe clearly **Self-checklist**:（**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**） + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [ ] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [ ] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> <!-- /bot1-source-body --> <!-- bot1-related-issues --> Linked Closing Issues: - [#1417](https://gitcode.com/openJiuwen/agent-core/issues/1417) <!-- /bot1-related-issues --> | 2 个月前 | |
fix: A2A extension invoke should return combined results Refs: #998 Co-authored-by: wangyuejoanna<wangyue335@h-partners.com> # message auto-generated for no-merge-commit merge: !1615 fix: A2A extension invoke should return combined results From: @gcw_XiLNLWHF Reviewed-by: @iamcandiceguo, @deyang See merge request: openJiuwen/agent-core!1615 | 4 个月前 | |
feat(examples): add adaptive multi-agent collaboration example Refs: #1418 <!-- bot1-mirror-meta --> github_pr: 155 head_repo: Nova1729/agent-core head_ref: feat/adaptive-multi-agent-collab head_sha: 46fc82f32452c2adb9c1e90074e83ffacd215c9b base_repo: openJiuwen-ai/agent-core base_ref: develop github_repo: openJiuwen-ai/agent-core base_branch: develop base_sha: de725c7e97c7ad31e4e49d4756428b04e382398e github_user: Nova1729 <!-- /bot1-mirror-meta --> Paired: [GitHub #155](https://github.com/openJiuwen-ai/agent-core/pull/155) ↔ [GitCode !2094](https://gitcode.com/openJiuwen/agent-core/merge_requests/2094) GitHub PR mirror for CodeArts CI. GitHub author: @Nova1729 <!-- bot1-source-body --> <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind feature **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes [#1418](https://gitcode.com/openJiuwen/agent-core/issues/1418) **What scenarios were tested, and what were the verification results（Function, performance, reliability, etc.）**： * Need to describe clearly **Self-checklist**:（**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**） + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [x] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [ ] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [ ] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> <!-- /bot1-source-body --> <!-- bot1-related-issues --> Linked Closing Issues: - [#1418](https://gitcode.com/openJiuwen/agent-core/issues/1418) <!-- /bot1-related-issues --> | 2 个月前 | |
fix(skill-evlution): improve skill evolution active review for fuzzy signals Refs: #1021 Co-authored-by: zhangzhongteng<zhangzhongteng1@huawei.com> # message auto-generated for no-merge-commit merge: !1644 fix(skill-evolution): improve skill evolution active review for fuzzy signals From: @z2tng Reviewed-by: @deyang, @iamcandiceguo See merge request: openJiuwen/agent-core!1644 | 4 个月前 | |
feat(context_evolver): include quickstart rail with cognition Co-authored-by: gan bingzheng<gan.bingzheng@huawei.com> Co-authored-by: bhyeo<yeo.boon.hong@huawei.com> Co-authored-by: Ubaidillah Ariq<ubaidillah.ariq.prathama@h-partners.com> # message auto-generated for no-merge-commit merge: !1201 feat(context_evolver): include quickstart rail with cognition From: @bhyeo Reviewed-by: @alan_cheng, @deyang See merge request: openJiuwen/agent-core!1201 | 3 个月前 | |
fix(llm): Modify the default value of top_p Paired: [GitHub #881](https://github.com/openJiuwen-ai/agent-core/pull/881) ↔ [GitCode !2476](https://gitcode.com/openJiuwen/agent-core/merge_requests/2476) <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openjiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- 选择下面一种标签替换下方 /kind <label>，可选标签类型有： - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范，修改PR描述后需要/check-pr重新检查PR规范。 --> /kind bug **Self-checklist**:（**请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入**） + - [ ] **设计**：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改 + - [x] **测试**：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [ ] **接口**：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确 + - [ ] **文档**：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-core gitcode_mr: 2476 github_repo: openJiuwen-ai/agent-core github_pr: 881 github_branch: sync/pr-2476 --> <!-- related-issues --> Linked Closing Issues: - [#1661](https://gitcode.com/openJiuwen/agent-core/issues/1661) <!-- /related-issues --> | 1 个月前 | |
[mirror] openJiuwen-ai/agent-core#395: fix(harness): store agent-history under jiuwenswarm dir Paired: [GitHub #395](https://github.com/openJiuwen-ai/agent-core/pull/395) ↔ [GitCode !2240](https://gitcode.com/openJiuwen/agent-core/merge_requests/2240) <!-- bot1-mirror-meta --> github_pr: 395 head_repo: chenran0522/agent-core head_ref: develop head_sha: 06452ec408c6dab65c02f52391f9f75d710458b4 base_repo: openJiuwen-ai/agent-core base_ref: develop github_repo: openJiuwen-ai/agent-core base_branch: develop base_sha: 709eb5d29ee1cf157d3288762a93fa4cfbc77c39 github_user: chenran0522 <!-- /bot1-mirror-meta --> GitHub PR mirror for CodeArts CI. <!-- bot1-source-body --> <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/openJiuwen/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openJiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- Choose one label from bug, task, feature and refactor, and replace <label> below the comment block. If this pr is not only bugfix/task/feature and also a refactor, you can append /kind refactor label after /kind bug, /kind task and /kind feature. --> /kind bug **What does this PR do / why do we need it**: * Need to describe clearly **Which issue(s) this PR fixes**: <!-- *Automatically closes linked issue when PR is merged. Usage: Fixes #<issue number>, or Fixes (paste link of issue). --> Fixes [#1490](https://gitcode.com/openJiuwen/agent-core/issues/1490) **What scenarios were tested, and what were the verification results（Function, performance, reliability, etc.）**： * Need to describe clearly **Self-checklist**:（**Please check carefully,and mark an x in the [] brackets. We will review your completion status.**） + - [x] **Design**: Has the solution corresponding to the PR been reviewed by the Maintainer, and have all review comments been replied to and revised + - [x] **Test**: Has the code in the PR been fully covered by UT/ST test cases, and have the newly added test cases been uploaded to the repository along with this PR or already uploaded. + - [ ] **Verification**: Does the PR description contains a detailed description of the verification results regarding the achievement of the expected goals for the Feature, Refactor, and Bugfix to this PR. + - [ ] **Interface**: Does it involve changes to external interfaces? The corresponding changes have been approved by the interface review organization, and the annotation information for the API has been correctly refreshed. + - [ ] **Document**: Does it involve modifications to the official website documentation? If so, please submit the materials to the Doc repository in a timely manner. <!-- **Special notes for your reviewers**: --> <!-- + - [ ] Whether it causes forward compatibility failure --> <!-- + - [ ] Whether the dependent third-party library change is involved --> <!-- /bot1-source-body --> <!-- bot1-related-issues --> Linked Closing Issues: - [#1490](https://gitcode.com/openJiuwen/agent-core/issues/1490) <!-- /bot1-related-issues --> | 2 个月前 | |
feat: Adapt to Intelli Router to support observability Refs: #951 Co-authored-by: Yoggaboomin<yutao131@huawei.com> # message auto-generated for no-merge-commit merge: !1422 Adapt to Intelli Router to support observability From: @JustinBieber1223 Reviewed-by: @iamcandiceguo, @deyang See merge request: openJiuwen/agent-core!1422 | 3 个月前 | |
docs(example): Update the examples/interact/weather_assistant_interact.ipynb Refs: #448 Co-authored-by: MapleKing<983563691@qq.com> # message auto-generated for no-merge-commit merge: !560 Update the examples/interact/weather_assistant_interact.ipynb From: @MapleLiu Reviewed-by: @yangzequ, @deyang See merge request: openJiuwen/agent-core!560 | 7 个月前 | |
refactor(online-rl): simplify gateway collector boundary Paired: [GitHub #251](https://github.com/openJiuwen-ai/agent-core/pull/251) ↔ [GitCode !2141](https://gitcode.com/openJiuwen/agent-core/merge_requests/2141) <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openjiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- 选择下面一种标签替换下方 /kind <label>，可选标签类型有： - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范，修改PR描述后需要/check-pr重新检查PR规范。 --> /kind feature **Self-checklist**:（**请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入**） + - [ ] **设计**：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改 + - [ ] **测试**：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库 + - [ ] **验证**：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [ ] **接口**：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确 + - [ ] **文档**：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-core gitcode_mr: 2141 github_repo: openJiuwen-ai/agent-core github_pr: 251 github_branch: sync/pr-2141 --> <!-- related-issues --> Linked Closing Issues: - [#1371](https://gitcode.com/openJiuwen/agent-core/issues/1371) <!-- /related-issues --> | 2 个月前 | |
| 5 个月前 | ||
| 7 个月前 | ||
feat(mobile_gui): add mobile gui agent with multimodal skill Refs: #936 Co-authored-by: p84436560<peeranat.kjp@gmail.com> Co-authored-by: Ubaidillah Ariq<ubaidillah.ariq.prathama@h-partners.com> # message auto-generated for no-merge-commit merge: !1413 feat(mobile_gui): add mobile gui agent with multimodal skill From: @p84436560 Reviewed-by: @SnapeK, @iamcandiceguo See merge request: openJiuwen/agent-core!1413 | 4 个月前 | |
fix(multi-agent): fix hierarchical team(tool mode) stream timeout Refs: #747 Co-authored-by: lamsaan_yau<qiulinshan1@huawei.com> # message auto-generated for no-merge-commit merge: !1373 fix(multi-agent): fix hierarchical team(tool mode) stream timeout From: @lamsaan_yau Reviewed-by: @iamcandiceguo, @wangxiaolong100 See merge request: openJiuwen/agent-core!1373 | 4 个月前 | |
feat(harness): Security protection. Extract permission structure, remove channel, use auto_confirm to replace persist_allow, and add docs. Refs: #705 Co-authored-by: Haowei_Du<duhaowei1@huawei.com> # message auto-generated for no-merge-commit merge: !1221 feat(harness): Security protection. Extract permission structure, remove channel, use auto_confirm to replace persist_allow, and add docs. From: @Haowei_Du Reviewed-by: @SnapeK, @alan_cheng See merge request: openJiuwen/agent-core!1221 | 5 个月前 | |
refactor(agent): BaseAgent remove ability's interface, directly call interface of ability manager Refs: #203 Co-authored-by: yangzequ<yangzequ1@huawei.com> # message auto-generated for no-merge-commit merge: !303 refactor(agent): BaseAgent remove ability's interface, directly call interface of ability manager From: @yangzequ Reviewed-by: @deyang, @SnapeK See merge request: openJiuwen/agent-core!303 | 8 个月前 | |
feat(retrieval): add Dashscope multimodal embedding support Refs: #535 Co-authored-by: SushiNinja<jin.huang2@h-partners.com> # message auto-generated for no-merge-commit merge: !667 feat(retrieval): add Dashscope multimodal embedding support From: @SushiNinja Reviewed-by: @yangzequ, @alan_cheng See merge request: openJiuwen/agent-core!667 | 6 个月前 | |
fix(agent_rl): Align agent RL docs with DeepAgent rollout Refs: #836 Co-authored-by: rolandyang<yangdongdong34@huawei.com> # message auto-generated for no-merge-commit merge: !1258 fix(agent_rl): Align agent RL docs with DeepAgent rollout From: @rolandyang Reviewed-by: @deyang, @iamcandiceguo See merge request: openJiuwen/agent-core!1258 | 5 个月前 | |
fix(agent_rl): Align agent RL docs with DeepAgent rollout Refs: #836 Co-authored-by: rolandyang<yangdongdong34@huawei.com> # message auto-generated for no-merge-commit merge: !1258 fix(agent_rl): Align agent RL docs with DeepAgent rollout From: @rolandyang Reviewed-by: @deyang, @iamcandiceguo See merge request: openJiuwen/agent-core!1258 | 5 个月前 | |
feature: security rail, sync from enterprise branch Refs: #921 Co-authored-by: luoruiping<luoruiping@huawei.com> # message auto-generated for no-merge-commit merge: !1377 feature: security rail, sync from enterprise branch From: @gcw_wZ6Lfs1I Reviewed-by: @SnapeK, @alan_cheng See merge request: openJiuwen/agent-core!1377 | 4 个月前 | |
| 5 个月前 | ||
feat: add skill evaluator module with ut and example Refs:#540 Co-authored-by: zhiqiuzoeyye<yezhiqiu3@h-partners.com> # message auto-generated for no-merge-commit merge: !900 feat: add skill evaluator module with ut and example From: @zhiqiuzoeyye Reviewed-by: @SnapeK, @iamcandiceguo See merge request: openJiuwen/agent-core!900 | 6 个月前 | |
doc(operator): Reproducibility test case supplement Refs: #1434 Paired: [GitHub #216](https://github.com/openJiuwen-ai/agent-core/pull/216) ↔ [GitCode !2124](https://gitcode.com/openJiuwen/agent-core/merge_requests/2124) <!-- Thanks for sending a pull request! Here are some tips for you: 1) If this is your first time, please read our contributor guidelines: https://gitcode.com/openJiuwen/community/blob/master/CONTRIBUTING.md 2) If you want to contribute your code but don't know who will review and merge, please add label openjiuwen-assistant to the pull request, we will find and do it as soon as possible. --> **What type of PR is this?** <!-- 选择下面一种标签替换下方 /kind <label>，可选标签类型有： - /kind bug - /kind task - /kind feature - /kind refactor - /kind clean_code 如PR描述不符合规范，修改PR描述后需要/check-pr重新检查PR规范。 --> /kind bug **Self-checklist**:（**请自检，在[ ]内打上x，我们将检视你的完成情况，否则会导致pr无法合入**） + - [ ] **设计**：PR对应的方案是否已经经过Maintainer评审，方案检视意见是否均已答复并完成方案修改 + - [ ] **测试**：PR中的代码是否已有UT/ST测试用例进行充分的覆盖，新增测试用例是否随本PR一并上库或已经上库 + - [ ] **验证**：PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [ ] **接口**：是否涉及对外接口变更，相应变更已得到接口评审组织的通过，API对应的注释信息已经刷新正确 + - [x] **文档**：是否涉及官网文档修改，如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-core gitcode_mr: 2124 github_repo: openJiuwen-ai/agent-core github_pr: 216 github_branch: sync/pr-2124 --> <!-- related-issues --> Linked Closing Issues: - [#1434](https://gitcode.com/openJiuwen/agent-core/issues/1434) <!-- /related-issues --> | 2 个月前 | |
fix: Enhance GaussDB ORM capabilities: add field type conversion and reflection Refs: #763 Co-authored-by: zhuyi007<zhuchunguang1@huawei.com> # message auto-generated for no-merge-commit merge: !1164 Enhance GaussDB ORM capabilities: add field type conversion and reflection From: @zhuyi007 Reviewed-by: @iamcandiceguo, @SnapeK See merge request: openJiuwen/agent-core!1164 | 5 个月前 | |
fix(agent): react agent support self-manage session Refs: #166 Co-authored-by: yangzequ<yangzequ1@huawei.com> # message auto-generated for no-merge-commit merge: !687 fix(agent): react agent support self-manage session From: @yangzequ Reviewed-by: @deyang, @SnapeK See merge request: openJiuwen/agent-core!687 | 7 个月前 | |
refactor: change project package structure Refs: #78 | 9 个月前 | |
refactor: change project package structure Refs: #78 | 9 个月前 |
设计思路： MCP SDK（ToolServerConfig + Runner + resource_mgr.tool()）已经把MCP Server → Tool 列表 → 调用工具这条链路封好了，要做的就是：
1.把 MCP server 注册进 resource_mgr.tool()。
2.用 Runner.list_tools(server_name) 拿到 McpToolCard。
3.把每个 McpToolCard 转成一个 LocalFunction（名字 / 描述 / 参数来自 JSON-Schema）。
4.在 LocalFunction._func 里，通过 Runner.run_tool(server_name.tool_name, arguments) 实际调用 MCP 工具。
5.把这些 LocalFunction 丢给 SuperReActAgent(tools=...)。
问题： 现在的 LocalFunction 例子都是同步（lambda a,b: a+b），MCP 工具是通过网络调用的，必须 async，所以 SuperReActAgent 在调用工具时需要类似await这样的逻辑