What the CLI is for
Vidova CLI is the native capture companion for AVS.
Its role is to handle workflows that are better done outside the browser:
- native screen and window recording
- device enumeration
- permission inspection
- packaging recordings into
.vidovabundles - uploading recordings into AVS projects
Install
npm i -g @vidova/cli
That installs the vidova binary.
Core command groups
Interactive recorder
vidova
Launches the interactive recorder UI.
Direct record
vidova record --window "Safari" --system-audio
Useful for scripted or flag-driven capture sessions.
Device auth
vidova auth login
Uses the browser-based AVS device authorization flow rather than embedding auth UI inside the recorder.
Device inspection
vidova devices --json
Enumerates monitors, windows, microphones, cameras, and permission state.
Project listing
vidova projects list
Lets the CLI discover upload destinations in AVS.
Package inspection
vidova info ./recording.vidova
Package extraction
vidova extract ./recording.vidova
Features exposed in the beta app for CLI support
The web app includes dedicated backend routes for:
- device auth start
- device auth poll
- device auth authorize
- CLI token management
- project listing
- default project lookup
- recording import
This is why the CLI can work as a real product surface instead of a disconnected uploader.
What a .vidova bundle represents
The CLI can pack recordings into a .vidova archive that may contain:
manifest.json- captured media
- cursor metadata
- keyboard metadata
Once imported, AVS can treat this material as a richer screen-recording asset rather than just a flat MP4.
Persistent defaults
The CLI also supports persistent capture defaults for things like:
- FPS
- width
- quality
- codec
- countdown
- output directory
- cursor tracking
- keyboard tracking
That makes repeated capture sessions less error-prone.