Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(i18n): address RFC translation review

Browse Source
This commit is contained in:
Tianyi Cui
2026-07-22 22:29:39 +08:00
parent 0b1857904a
commit 1a39953f69
447 changed files with 1106 additions and 1106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/rfc/rejected/simplification/2026-06-20-single-session-acp-bridge.md
View File

@@ -1,9 +1,9 @@
# RFC: Return the ACP bridge to one live session per connection
English | [中文](2026-06-20-single-session-acp-bridge.zh.md)
Status: rejected — Zed is the current target ACP client and its ACP implementation is explicitly multi-session: it stores live sessions in a `HashMap<SessionId, AcpSession>`, tracks `pending_sessions`, joins concurrent loads for the same id, and tests close-during-load behavior.
English | [中文](2026-06-20-single-session-acp-bridge.zh.md)
## Problem
The ACP bridge now supports multiple live sessions on one JSON-RPC connection. That capability brings multi-entry session maps, reverse session/agent lookups, per-session prompt state, loading ids, demux for every event, cross-session teardown, and isolation concerns for future permission prompts and background tasks. The older [multi-session ACP proposal](../../implemented/feature/2026-06-14-acp-multi-session.md) still tracks the unfinished permission-ownership piece; this RFC is the competing simplification path.