* Handle ACP `session/resume`. Per ACP spec, `session/resume` is the * lighter-weight sibling of `session/load`: same on-disk session * rehydration, same `configOptions:` advertisement — but the client * is expected to have already seen the prior turns, so the agent * deliberately does N
(params: ResumeSessionRequest)
| 391 | * rationale, and gap-4.1 for the matching capability advertisement. |
| 392 | */ |
| 393 | async resumeSession(params: ResumeSessionRequest): Promise<ResumeSessionResponse> { |
| 394 | const { session, configOptions } = await this.setupSessionFromExisting({ |
| 395 | cwd: params.cwd, |
| 396 | sessionId: params.sessionId, |
| 397 | mcpServers: params.mcpServers, |
| 398 | mode: 'resume', |
| 399 | }); |
| 400 | this.scheduleAvailableCommandsUpdate(session.id); |
| 401 | return { configOptions }; |
| 402 | } |
| 403 | |
| 404 | /** |
| 405 | * Shared setup for `session/load` and `session/resume`: gates auth, |
no test coverage detected