Skip to content

Persist and restore workspace-scoped ACP sessions - #136

Closed
Maximooch wants to merge 1 commit into
feat/acp-tool-eventsfrom
feat/acp-session-lifecycle
Closed

Maximooch wants to merge 1 commit into
feat/acp-tool-eventsfrom
feat/acp-session-lifecycle

Conversation

@Maximooch

Copy link
Copy Markdown
Owner

Stacked on Expose scoped tool lifecycle and plans through ACP (#135). ACP-created sessions now persist immutable workspace ownership and the visible user/tool/assistant update history inside Penguin's native session store. Clients can list, load with ordered replay before acknowledgement, resume without replay, and close without deleting history. Other workspaces and legacy sessions without ACP ownership are not exposed. Interrupted tool entries recover as failed without re-execution. Shared-core lifecycle and prompt operations remain serialized.

The pinned SDK gates resume/close behind its historical unstable switch even though current v1 docs include them; the stdio adapter enables that dispatcher switch, while unimplemented methods remain unadvertised. Deletion remains a follow-up because the SDK omits that route. This is not a claim of complete v1 parity.

Validation: 28 aggregate ACP tests pass; native SessionManager disk restart and core message continuation; full ordered visible replay; workspace/ID rejection; pagination; interrupted-tool repair; actual CLI subprocess restart/load/resume/close wire tests. Scoped Ruff and diff checks pass. Fake provider cores are used; no real-editor/provider smoke is claimed. History snapshots are currently persisted per update for correctness; high-volume performance remains an optimization opportunity.

@vercel

vercel Bot commented Oct 28, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
penguin Ready Ready Preview Oct 28, 2026 5:02am UTC

@coderabbitai

coderabbitai Bot commented Oct 28, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Maximooch

Copy link
Copy Markdown
Owner Author

Integrated with preserved commit history through #161 (main commit abd8a66). Closing this stacked review after verifying its current head is an ancestor of main.

@Maximooch Maximooch closed this Oct 28, 2026

This branch was successfully deployed

1 active deployment
Preview — a6a4bd11 Deployed Oct 28, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant