| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat(harness/worktree): persist worktree across session with validation fixes - Persist active worktree across agent Session lifecycle - Move workspace symlink view to team workspace - Close fail-closed gap in exit validation - Add single-deepagent e2e worktree example docs | 5 个月前 | |
refactor(agent_teams): move worktree to harness for single-agent reuse worktree was 90% generic git isolation but lived under agent_teams, so deepagent could not mount the same enter/exit tools. Move the generic implementation to openjiuwen/harness/tools/worktree/, switch the manager to a generic event_handler callback (decoupling from TeamEvent), and migrate ToolCard descriptions to harness prompt providers (worktree.enter / worktree.exit IDs). The team-specific RemoteWorktreeBackend stays in openjiuwen/agent_teams/worktree_remote.py because it depends on the team paths layout. agent_teams imports are switched to harness; agent_teams/worktree/ is removed entirely. Tests move under tests/unit_tests/harness/tools/worktree/ with a new test_tools.py covering owner_id/legacy kwargs, guards, and a real git happy path. examples/harness/deepagent_with_worktree.py demonstrates the single-agent integration end-to-end. Refs: #751 | 5 个月前 | |
feat(harness/worktree): persist worktree across session with validation fixes - Persist active worktree across agent Session lifecycle - Move workspace symlink view to team workspace - Close fail-closed gap in exit validation - Add single-deepagent e2e worktree example docs | 5 个月前 | |
[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 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 5 个月前 | ||
| 5 个月前 | ||
| 5 个月前 | ||
| 2 个月前 |