Skip to content

vos record reads the hosted recording cap live - #128

Merged
hblee12294 merged 1 commit into
mainfrom
cli-limits
Sep 3, 2026
Merged

vos record reads the hosted recording cap live#128
hblee12294 merged 1 commit into
mainfrom
cli-limits

Conversation

@hblee12294

Copy link
Copy Markdown
Member

vos record and vos create stop a take at the hosted recording cap so what lands is what the platform hosts. Until now that cap was a constant here, and a change on the platform meant a CLI release.

The cap is now resolved once before each take: --max-duration when given; else the platform's public GET /api/limits (limits.recordingMaxSeconds), asked with the caller's key when one resolves so a plan with a longer cap gets it; else the built-in 30 minutes, said in a note, because a take longer than the platform's cap is refused at push time. The read is bounded at two seconds and fail-open, so an offline machine records exactly as before. parseHostedCap refuses any payload that is not a limits table.

Verified: pnpm check, pnpm typecheck, pnpm lint, pnpm test green (cli 192).

The cap a take records under is --max-duration when given; else the
platform's public GET /api/limits, asked with the caller's key when one
resolves so a plan with a longer cap gets it; else the built-in 30 minutes,
said in words, because a take longer than the platform's cap is refused at
push time. Bounded at two seconds and fail-open, so an offline machine
records exactly as before.
@hblee12294
hblee12294 merged commit d4b1f0f into main Sep 3, 2026
3 checks passed
@hblee12294
hblee12294 deleted the cli-limits branch September 3, 2026 16:10
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.

1 participant