Repository navigation
feat(forward): add realtime conversations and history - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add Forward Realtime Beta Conversation creation, WebSocket connections and persisted History with independent
beforepagination. Connections expose text/PCM16 input, typed and unknown events, Work progress, playback receipts, interruption and acknowledged graceful closure.Why
The Go SDK cannot currently use Forward's Realtime API. This adds the public creation/connection/history surface while reusing the existing authentication and HTTP resource conventions.
Verification
make lintmake buildmake testmake docs-checkgo build ./examples/...Additional checks:
go test -race ./forward -run Realtime -count=1, the complete offline suite on Go 1.23.12, and changelog/release-notes checks passed.CN/Global × PAT/Forward-bound SAT: 4 text and 4 PCM scenarios passed through
make test-live-realtime. These verify creation, ready, ping/pong, nonempty transcripts, decoded output audio, matching close acknowledgements and filtered History pagination. Temporary test Identities were cleaned up; existing Templates were preserved. Conversation IDs are retained because there is no public delete API. Input audio is a fixed PCM fixture; audio devices were not tested.Local WebSocket tests cover protocol validation, cancellation, redirects, deadlines, queue limits, concurrent sending and closure. Work events have offline coverage; Go did not additionally execute a live Work task.
Impact
CHANGELOG.mdunderUnreleased.env.live, logs, or generated test output committedThis is additive; migration notes are not required. Adds
github.com/coder/websocketwhile retaining Go 1.23. Transport and stage deadlines are separate from HTTP request timeouts; connections have bounded queues and do not automatically reconnect or replay inputs. Playback receipts remain application-owned.Realtime SA access currently requires a Forward-issued bound SAT. The platform
ServiceAccountCredentialexchange does not create that binding; its SAT returned 403 during the initial live checks. Passing a Forward-issued SAT through the existing direct-token interface passed. The SAT issuance API is already merged into main (#12); this PR builds on it and does not change platform credential renewal. Template Realtime configuration APIs are outside this PR.