Run all ACP harnesses on persistent live sessions - #2291
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
ApprovabilityVerdict: Needs human review Major refactor replacing the ACP composition pattern with inheritance-based You can customize Macroscope's approvability policy. Learn more. |
2263061 to
f471f80
Compare
623522e to
c65d7e7
Compare
212f5db to
add2799
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 3 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9c027ec. Configure here.
92e3b69 to
4b5c609
Compare
d37b717 to
cdbd9fd
Compare

Summary
This makes persistent LiveACP the single v1 execution model for every ACP-backed harness.
ACPHarnesslifecycle.session_pathcontinuation, and stateless fallback.Why
The harnesses previously mixed live sessions, one-shot processes, and file-backed resume. Rebuilding a conversation at those boundaries changed model-visible history and produced false branches even when the agent completed the task correctly.
With LiveACP as the common backend, every interaction segment continues on the same native session. The graph can therefore represent one append-only conversation, and harness-specific code no longer needs to emulate continuation.
Provider and agent differences remain local to their harnesses: Kimi and Pi select their transport, Hermes resolves its native catalog, OpenClaw supervises its Gateway, and Pool now uses the same live lifecycle as the other ACP agents.
Stack
Validation
typre-push parity checkgit diff --check