openJiuwen Agent Runtime 是 openJiuwen 体系中的智能体运行与部署管理平台,致力于将 Agent 从“开发态”稳定带到“生产态”,让发布、运行、管理更加标准与可控。
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs(api): config_refresh 明确代价与低峰期建议; 补齐 config-plane-api 三轮特性同步 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !545 merge develop into develop docs(api): config_refresh 明确代价与低峰期建议; 补齐 config-plane-api 三轮特性同步 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #208](https://github.com/openJiuwen-ai/agent-runtime/pull/208) ↔ [GitCode !545](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/545) <!-- 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 <label> **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-runtime gitcode_mr: 545 github_repo: openJiuwen-ai/agent-runtime github_pr: 208 github_branch: sync/pr-545 --> See merge request: openJiuwen/agent-runtime!545 | 3 天前 | |
填加audit log sdk Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !542 merge support-observability-v2 into develop 填加audit log sdk Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: cyz95 Description: Paired: [GitHub #206](https://github.com/openJiuwen-ai/agent-runtime/pull/206) ↔ [GitCode !542](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/542) <!-- 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 542 github_repo: openJiuwen-ai/agent-runtime github_pr: 206 github_branch: sync/pr-542 --> See merge request: openJiuwen/agent-runtime!542 | 5 天前 | |
docs: 补充HTTP/SSE内部链路mTLS证书认证设计与接口文档 Co-authored-by: whq<whqxbs@163.com> # message auto-generated for no-merge-commit merge: !533 merge docs/link-mtls-four-layer into develop docs: 补充HTTP/SSE内部链路mTLS证书认证设计与接口文档 Created-by: u010240195 Commit-by: whq Merged-by: cyz95 Description: Paired: [GitHub #191](https://github.com/openJiuwen-ai/agent-runtime/pull/191) ↔ [GitCode !533](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/533) <!-- 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 <label> **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-runtime gitcode_mr: 533 github_repo: openJiuwen-ai/agent-runtime github_pr: 191 github_branch: sync/pr-533 --> See merge request: openJiuwen/agent-runtime!533 | 8 天前 | |
填加audit log sdk Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !542 merge support-observability-v2 into develop 填加audit log sdk Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: cyz95 Description: Paired: [GitHub #206](https://github.com/openJiuwen-ai/agent-runtime/pull/206) ↔ [GitCode !542](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/542) <!-- 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 542 github_repo: openJiuwen-ai/agent-runtime github_pr: 206 github_branch: sync/pr-542 --> See merge request: openJiuwen/agent-runtime!542 | 5 天前 | |
fix agentserver boot issue Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !448 merge fix-agentserver-boot-issue into develop fix agentserver boot issue Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: cyz95 Description: Paired: [GitHub #97](https://github.com/openJiuwen-ai/agent-runtime/pull/97) ↔ [GitCode !448](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/448) <!-- 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 <label> **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-runtime gitcode_mr: 448 github_repo: openJiuwen-ai/agent-runtime github_pr: 97 github_branch: sync/pr-448 --> See merge request: openJiuwen/agent-runtime!448 | 29 天前 | |
agent-runtime 分布式服务首提交 docs(e2e): 新增端到端测试用例说明——全部场景/输入/预期输出逐条化 docs/e2e-test-cases.md: - 四层体系总览(双实例 pytest / M6 冒烟 65 项 / 多副本 e2e 35 项 / 压测) 与退出码约定 - 通用约定:请求信封格式、错误码契约表、Redis 真相源键、前置自检与 FLUSHDB 防误刷语义 - M6 冒烟:模板矩阵 + 13 阶段 52 条用例逐条(场景映射/输入/预期) - 多副本 e2e:S0–S8 逐条(含 DEGRADED 语义、failover 目标选择、 winner∈candidates 互斥不变量) - 双实例 12 用例与压测 3 场景的输入/判定 - 环境与重现手册(Redis DB1/DB2 约定、集群部署、逐层命令) - 已知语义差异(多副本冷突发 NO_POD_AVAILABLE、冷竞争双 Pod 自愈、 场景 N 暂缓、config_sync 串行) README/code-guide §7/CLAUDE.md 增交叉引用 Co-Authored-By: Claude <noreply@anthropic.com> fix(e2e): 经多副本 LB 跑 M6 冒烟 63/65 的根因修复——65/65 两处失败初判「多副本冷突发语义」,排查证明均为部署配置差异: 1. F-队列超时 504 缺失:集群部署漏设 AGENT_RUNTIME_SCOPE_FULL_TIMEOUT (默认 30s 恰等于 tpl-f session_ttl=30s)→ 等待者 deadline≈会话到期, 被到期驱逐的 PUBLISH 提前唤醒 → 竞态窗口内 2×NO_POD_AVAILABLE+ 2×200 混合、无干净 504。修复:部署模板补该变量(默认 8,红线注释 「须显著小于 session_ttl」)+ env.example。 2. cleanup 空目标 500:admin 凭据对不存在 ns list 得空列表,in-cluster SA 的 namespaced RBAC 先行 403 → ApiException 未处理裸 500(4/4 稳定 复现)。修复:产品 cleanup 对 404 容忍为 cleaned=0(跨凭据形态行为 对齐),403 保持 fail-fast(静默清零会掩盖 RBAC 配错);+2 单测。 测试空目标改用无匹配 label_selector——期间实测踩坑:业务 ns 会误删 同 label 真实 AgentServer(default ns 2 个 gateway 管理的 Pod 被误删, 其一 16s 自愈,handoff §十一.6 教训再现);min_idle 热备 1s 重建致 刚清空的 ns 也不为空。三坑实录入 docs/e2e-test-cases.md §8.1。 验证:M6 冒烟经 LB 65/65 + 单实例 65/65;多副本 e2e 35/35; pytest 104→106 全绿。文档计数与归因同步(CLAUDE/README/code-guide/ handoff §十一.1 补记)。 Co-Authored-By: Claude <noreply@anthropic.com> | 1 个月前 | |
refactor(observability): 诊断端点 /debug → /visualization——对外去敏感化,行为零变化 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !473 merge develop into develop refactor(observability): 诊断端点 /debug → /visualization——对外去敏感化,行为零变化 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: ZYQ5333 Description: Paired: [GitHub #122](https://github.com/openJiuwen-ai/agent-runtime/pull/122) ↔ [GitCode !473](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/473) <!-- 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 <label> **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-runtime gitcode_mr: 473 github_repo: openJiuwen-ai/agent-runtime github_pr: 122 github_branch: sync/pr-473 --> See merge request: openJiuwen/agent-runtime!473 | 23 天前 | |
优化流水线编译镜像的速度,解决半夜编译过慢的问题 Co-authored-by: chen hui<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !499 merge improve-ci into develop 优化流水线编译镜像的速度,解决半夜编译过慢的问题 Created-by: chen-hui-zhe-xi Commit-by: chen hui Merged-by: cyz95 Description: Paired: [GitHub #154](https://github.com/openJiuwen-ai/agent-runtime/pull/154) ↔ [GitCode !499](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/499) <!-- 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> <!-- bot4-pr-sync-meta schema_version: 1 source: gitcode gitcode_repo: openJiuwen/agent-runtime gitcode_mr: 499 github_repo: openJiuwen-ai/agent-runtime github_pr: 154 github_branch: sync/pr-499 --> See merge request: openJiuwen/agent-runtime!499 | 15 天前 | |
test(补强): 真环境缺陷复盘五项落地——真镜像门禁/自然老化/不变量巡检/停机韧性/指纹键序 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !455 merge develop into develop test(补强): 真环境缺陷复盘五项落地——真镜像门禁/自然老化/不变量巡检/停机韧性/指纹键序 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #104](https://github.com/openJiuwen-ai/agent-runtime/pull/104) ↔ [GitCode !455](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/455) <!-- 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 <label> **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-runtime gitcode_mr: 455 github_repo: openJiuwen-ai/agent-runtime github_pr: 104 github_branch: sync/pr-455 --> See merge request: openJiuwen/agent-runtime!455 | 27 天前 | |
docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Co-authored-by: wangmingqi<wangmingqi@huawei.com> # message auto-generated for no-merge-commit merge: !439 merge develop1 into develop docs: 文档重构支持项目记忆管理。文档三分重组——design/spec/feature 下沉模块根,spec 按子包拆分 Created-by: wangmingqi Commit-by: wangmingqi Merged-by: cyz95 Description: Paired: [GitHub #87](https://github.com/openJiuwen-ai/agent-runtime/pull/87) ↔ [GitCode !439](https://gitcode.com/openJiuwen/agent-runtime/merge_requests/439) <!-- 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 <label> **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-runtime gitcode_mr: 439 github_repo: openJiuwen-ai/agent-runtime github_pr: 87 github_branch: sync/pr-439 --> See merge request: openJiuwen/agent-runtime!439 | 30 天前 | |
fix: 补充代码版权申明、三方引用申明、License文件 Co-authored-by: ZYQ5333<zhangyaqing8@huawei.com> # message auto-generated for no-merge-commit merge: !81 merge develop into develop fix: 补充代码版权申明、三方引用申明、License文件 Created-by: ZYQ5333 Commit-by: ZYQ5333 Merged-by: cyz95 Description: <!-- 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 task **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!81 | 5 个月前 | |
fix: 补充代码版权申明、三方引用申明、License文件 Co-authored-by: ZYQ5333<zhangyaqing8@huawei.com> # message auto-generated for no-merge-commit merge: !81 merge develop into develop fix: 补充代码版权申明、三方引用申明、License文件 Created-by: ZYQ5333 Commit-by: ZYQ5333 Merged-by: cyz95 Description: <!-- 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 task **Self-checklist**:(**请自检,在[ ]内打上x,我们将检视你的完成情况,否则会导致pr无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!81 | 5 个月前 | |
fix: missing studio module Co-authored-by: chen-hui-zhe-xi<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !219 merge fix-missing-studio-module into develop fix: missing studio module Created-by: chen-hui-zhe-xi Commit-by: chen-hui-zhe-xi Merged-by: cyz95 Description: <!-- 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!219 | 4 个月前 | |
fix: missing studio module Co-authored-by: chen-hui-zhe-xi<chenhui280@h-partners.com> # message auto-generated for no-merge-commit merge: !219 merge fix-missing-studio-module into develop fix: missing studio module Created-by: chen-hui-zhe-xi Commit-by: chen-hui-zhe-xi Merged-by: cyz95 Description: <!-- 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无法合入**) + - [x] **设计**:PR对应的方案是否已经经过Maintainer评审,方案检视意见是否均已答复并完成方案修改 + - [x] **测试**:PR中的代码是否已有UT/ST测试用例进行充分的覆盖,新增测试用例是否随本PR一并上库或已经上库 + - [x] **验证**:PR描述信息中是否已包含对该PR对应的Feature、Refactor、Bugfix的预期目标达成情况的详细验证结果描述 + - [x] **接口**:是否涉及对外接口变更,相应变更已得到接口评审组织的通过,API对应的注释信息已经刷新正确 + - [x] **文档**:是否涉及官网文档修改,如果涉及请及时提交资料到Doc仓 <!-- **Special notes for your reviewers**: --> <!-- + - [ ] 是否导致无法前向兼容 --> <!-- + - [ ] 是否涉及依赖的三方库变更 --> See merge request: openJiuwen/agent-runtime!219 | 4 个月前 |
openJiuwen Agent Runtime
openJiuwen Agent Runtime(简称 Runtime)是面向 AI Agent 的运行时与部署管理系统,核心目标是将智能体从“开发态”稳定地带到“生产态”。
项目定位
Runtime 主要解决以下问题:
- 如何把不同类型的 Agent 统一部署并对外服务;
- 如何在多租户场景下隔离不同用户和空间的运行实例;
- 如何支持多种部署方式(进程、Docker、Kubernetes);
- 如何对运行态 Agent 做生命周期管理(部署、查看、删除、健康检查)。
核心能力
1)统一的部署管理
Runtime 暴露标准 REST API,可通过配置文件和元数据完成 Agent 部署,支持部署、查询、删除与状态管理。
2)多部署策略支持
Runtime 内置策略化部署能力,支持三种模式:
subprocess:以独立子进程方式运行 Agent(默认);docker:以容器方式运行 Agent;k8s:在 Kubernetes 集群中运行 Agent。
3)多租户隔离
Runtime 支持租户上下文注入(如 user_id、space_id),用于隔离不同租户的 Agent 资源和操作范围。
4)可扩展架构
Runtime 采用模块化设计,部署策略、Agent 类型、基础能力均可独立扩展,便于在不同业务场景中快速接入新能力。
系统架构
Runtime 由以下核心模块组成:
- Agent Runtime(总体):覆盖从发布、部署到对外调用的全生命周期。
- Service(引擎模块,
service/):AgentApp/BaseApp封装 FastAPI 与对话面 API(/query、/health、/reset_conversation),承载业务请求。 - Management(管理模块,
management/):DeploymentManager与 Deployer(进程、Docker、K8s 等)负责部署策略、实例启停与状态持久化。 - Server(运行时服务模块,
server/):暴露管理面 REST(部署与实例查询、删除等)、租户中间件与健康检查;对话在已拉起的 Agent 进程(Service + Applications)内完成。 - Foundation(基础服务模块,
foundation/):SQLite / MySQL、可选 Redis、端口与部署目录、虚拟环境、Docker 工具、日志等共用基础能力。 - Applications(应用适配模块,
applications/):具体智能体实现与运行支撑(如低码 Agent、工作流 IR 执行),基于 Service,由 Management 拉起为独立进程。
典型部署流程
- 客户端调用 Runtime 部署接口,提交 Agent 配置;
- Runtime 根据配置选择部署策略并创建部署记录;
- 策略执行器完成实例拉起(进程 / 容器 / K8s);
- Agent 服务启动并暴露标准接口(如
/query、/health); - 业务侧通过 Runtime 或 Agent 地址进行调用与运维管理。
目录结构
agent-runtime/
├── applications/ # Agent 应用与运行支持
├── cli/ # CLI 命令行工具
├── docker/ # Docker 构建文件
├── foundation/ # 基础库:DB、端口、部署工具等
├── management/ # 部署管理核心与部署器
├── server/ # FastAPI 管理服务
├── service/ # 应用抽象与服务层
├── scripts/ # 启动与构建脚本
└── docs/ # 项目文档
环境要求
- python>=3.11.4
- uv>=0.25.x
- git(用于拉取代码)
- bash(Linux/macOS 系统)或 PowerShell(Windows 系统)
快速开始
1) 获取代码
git clone https://gitcode.com/openJiuwen/agent-runtime.git
cd agent-runtime
2) 准备环境配置
cd server
cp .env.example .env
然后按需修改 server/.env,重点包括:
RUNTIME_DB_TYPE:支持sqlite/mysql/gaussdb/opengaussIP:Runtime 服务地址LOWCODE_IMAGE:低码 Agent 相关镜像配置
说明:
- 默认安装仅包含
sqlite/mysql所需依赖。 - 当
RUNTIME_DB_TYPE=gaussdb或RUNTIME_DB_TYPE=opengauss时,需要额外安装async-gaussdb。 - 使用仓库自带启动脚本时,脚本会根据
server/.env中的RUNTIME_DB_TYPE自动安装foundation[gaussdb]可选依赖;手工安装时可执行uv pip install -e "./foundation[gaussdb]"。
完整配置项说明请参考 docs/zh/2. 配置说明.md。
3) 一键启动 Runtime 服务
Linux / macOS:
bash scripts/run-server.sh
Windows(PowerShell):
.\scripts\run-server.ps1
脚本会自动完成依赖安装、构建与服务拉起。默认监听端口为 8186(可通过 PORT 覆盖)。
API 概览
运行时管理服务默认提供以下管理接口:
GET /health:服务健康检查POST /api/v1/agents/deploy:部署 AgentGET /api/v1/agents:查询部署列表GET /api/v1/agents/{deployment_id}:查询部署详情DELETE /api/v1/agents/{deployment_id}:删除部署
部署完成后,Agent 应用本身可通过其运行端口提供:
GET /health:应用健康检查POST /query:对话查询(支持流式响应)POST /reset_conversation:重置会话上下文
与 openJiuwen Studio 协作
在 agent-studio 中配置 Runtime 地址后,可直接完成:
- 智能体一键发布到 Runtime
- 发布后在线对话验证
- 自动生成 API 调用示例(curl / Python / JavaScript)
- 一键下架并回收运行态实例
配置说明
当前支持的关键配置能力:
- 运行端口与服务地址配置
- 数据库类型配置(SQLite / MySQL / GaussDB / openGauss)
- 部署模式选择(进程;容器与 K8s 持续完善)
- 租户上下文透传与隔离策略
详细配置请参考 docs/zh/2. 配置说明.md。
文档导航
- 项目介绍:
docs/zh/0. 项目介绍.md - 快速开始:
docs/zh/1. 快速开始.md - 配置说明:
docs/zh/2. 配置说明.md - Agent 部署:
docs/zh/3. Agent部署.md - Agent 接入:
docs/zh/4. Agent接入.md
Roadmap
- 完善 Docker / Kubernetes 部署能力
- 补齐 CLI 接入能力
- 补齐 WebUI 接入能力