feat(recording): export smooth 60 FPS captures#29
Merged
Conversation
kitlangton
force-pushed
the
recording-60fps
branch
from
July 19, 2026 04:12
0261e72 to
aae97bd
Compare
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
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
Export MP4 recordings at 60 FPS by default while keeping visible OpenCode TUI sessions free of Drive service and progress output. Development checkouts now reuse the installed OpenTUI preload through a local symlink instead of reinstalling it into every artifact directory.
How
packages/drive/src/recording: defaults replay and encoding to 60 FPS, reuses unchanged terminal snapshots, avoids repeatedly serializing full frames for deduplication, and emits an exact one-frame tail for off-grid final states.packages/drive/src/instance/runtime.ts: keeps service stdio in artifact logs and links the checkout's existing@opentui/solidpreload into development artifacts.packages/drive/src/cli/start.tsandsrc/log.ts: continue writing lifecycle progress toopencode-drive.logwithout painting over a visible TUI.Scope
This does not replace the in-memory replay API with a streaming API. It bounds the expensive part of quiet 60 FPS recordings by sharing immutable snapshots and deduplication keys while preserving the existing public result shape.
Testing
bun run --bun vitest run test/recording/replay.test.ts test/recording/export.test.ts(19 passed)bun run test:effect(127 passed)bun test test/cli/integration.test.ts -t "creates a type-checkable Effect script without overwriting it|keeps service and progress output out of a visible client terminal"(2 passed)60/1,0.466667s, 28 frames, and the off-grid final frame pixels.bun run typecheckpassed.bun run lintcompleted with three pre-existing warnings outside this diff.Flow