Skip to content

feat: Implement cloud follow-up resume for agent sessions#1189

Open
tatoalo wants to merge 1 commit intomainfrom
feat/code/cloud-resume-snapshot
Open

feat: Implement cloud follow-up resume for agent sessions#1189
tatoalo wants to merge 1 commit intomainfrom
feat/code/cloud-resume-snapshot

Conversation

@tatoalo
Copy link
Contributor

@tatoalo tatoalo commented Mar 11, 2026

agent server broadcasts a notification when a turn finishes, needed for follow ups messages to cloud runs.
added support for cloud resume flow and snapshot-aware state management.

Edited UI to allow user to add messages while cloud run is executing and/or snapshot created ready to be resumed.

ph_code_snapshot_functionality.mp4

@tatoalo tatoalo force-pushed the feat/code/cloud-resume-snapshot branch 4 times, most recently from 98e4786 to eaab07a Compare March 11, 2026 13:31
@tatoalo tatoalo requested a review from a team March 11, 2026 13:34
method: "session/update",
jsonrpc: "2.0",
id: ts,
method: "session/prompt",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch

}
}

private broadcastTurnComplete(stopReason: string): void {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the reasoning behind using this versus just catching the session/prompt response which already includes a stopReason? See: https://agentclientprotocol.com/protocol/prompt-turn#4-check-for-completion

Probably just convenience?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah good question, so as far as I could gather, the broadcast can be fired asap whilst the session/prompt response is tied to the request/response lifecycle. For cloud runs where there's no active prompt request in flight (prompt passed via pending_user_message inside the run state), there's no session/prompt response to catch

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sick, sounds good

@tatoalo tatoalo force-pushed the feat/code/cloud-resume-snapshot branch from eaab07a to b0f9a3d Compare March 11, 2026 15:40
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.

2 participants