Rename session transcript read: steps -> records#49
Merged
Conversation
Follows ellipsis-dev/ellipsis#5869 (merged), which renamed GET /v1/sessions/{id}/steps -> /records (native session_records: transcript + lifecycle, feed_seq-ordered; no compat shim). - verb: agent session steps -> agent session records - connect flag: --no-steps -> --no-records - ApiClient.getAgentSessionSteps -> getAgentSessionRecords, path /records - ListSessionStepsResponse -> ListSessionRecordsResponse - comments/README/help text to match The search scope 'steps' (sessions search arm) and the WS frame names are separate server contracts and unchanged.
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.
What
Rename the session transcript read to match the server rename in ellipsis-dev/ellipsis#5869 (merged):
agent session steps <id>->agent session records <id>agent session connect --no-steps->--no-recordsApiClient.getAgentSessionSteps->getAgentSessionRecords, callingGET /v1/sessions/{id}/recordsListSessionStepsResponse->ListSessionRecordsResponse; README/help/comments updatedWhy
The endpoint returns native
session_records(transcript + lifecycle rows,feed_seq-ordered);stepswas leftover naming from the droppedagent_stepstable. The server renamed with no compat shim (pre-customer), so released CLIs'session stepsis broken against prod until this ships - merge and cut a release promptly.Unchanged on purpose
session search --scope steps- the search-arm param is a separate server contract, not renamed.steps_appendetc. in RUN_STREAMING_SPEC.md) - the connect stream contract is a separate migration (monorepo PR Fix bun --compile release build (bundle react-devtools-core) #2).Verification
tsc --noEmitclean;vitest225/225 (incl. the updated URL assertion intest/search.test.ts).