You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ACP: @deepseek-ai/dsh-acp does not implement session/load, so clients cannot restore conversation history
#7359
The ACP bridge (@deepseek-ai/dsh-acp) advertises sessionCapabilities: { close, list, resume } and implements session/resume — which by design resumes a session without replaying history. It does not implement the standard session/load method (resume + replay of prior turns as session/update notifications).
Reproduction
Connect an ACP client that uses session/load to restore a previous conversation (e.g. Paseo).
initialize → session/load { sessionId, cwd }
Server returns -32601 Method not found: session/load.
Impact
Clients that rely on session/load (e.g. Paseo, which rebuilds its UI timeline from the ACP replay) show an empty conversation after a client/daemon restart, even though the session log is intact. session/resume alone cannot fix this because it explicitly does not replay history.
Suggestion
Implement session/load in packages/acp: same checks as resumeSession, then replay the persisted history to the client as session/update notifications before responding, and advertise load: {} in sessionCapabilities.
Tested on @deepseek-ai/dsh-acp 0.1.5-rc.2; the latest dsh-v0.1.6-alpha.2 source has the same method set.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
The ACP bridge (
@deepseek-ai/dsh-acp) advertisessessionCapabilities: { close, list, resume }and implementssession/resume— which by design resumes a session without replaying history. It does not implement the standardsession/loadmethod (resume + replay of prior turns assession/updatenotifications).Reproduction
session/loadto restore a previous conversation (e.g. Paseo).initialize→session/load { sessionId, cwd }-32601 Method not found: session/load.Impact
Clients that rely on
session/load(e.g. Paseo, which rebuilds its UI timeline from the ACP replay) show an empty conversation after a client/daemon restart, even though the session log is intact.session/resumealone cannot fix this because it explicitly does not replay history.Suggestion
Implement
session/loadinpackages/acp: same checks asresumeSession, then replay the persisted history to the client assession/updatenotifications before responding, and advertiseload: {}insessionCapabilities.Tested on
@deepseek-ai/dsh-acp0.1.5-rc.2; the latestdsh-v0.1.6-alpha.2source has the same method set.All reactions