Inspect the source.
Inspect duration, resolution, audio, captions, and local sidecars before deciding what the task actually needs.
python skill/scripts/voidscape.py inspect "clip.mp4"
Voidscape turns a local file or URL into grounded frames and timestamped text—while keeping cost, cloud processing, and model downloads visible before work begins.
Start with source facts, preview the boundary, then prepare artifacts an agent can inspect.
Inspect duration, resolution, audio, captions, and local sidecars before deciding what the task actually needs.
python skill/scripts/voidscape.py inspect "clip.mp4"
Separate transcription spend from vision-token cost, flag dependencies, and show whether approval is required.
python skill/scripts/voidscape.py preview "clip.mp4" --tier both --backend captions
Extract only the frames and transcript you approved, then hand agents artifacts they can cite and inspect.
python skill/scripts/voidscape.py read "clip.mp4" --tier both --backend captions
Preview is a decision point, not a receipt. It exposes the frame plan, transcription path, cloud boundary, and model-download state before reading changes anything.
$ voidscape.py preview "clip.mp4" --tier both
Every direction is explicitly labeled: working today, designed next, or longer-term exploration.
A local-first pipeline for evidence, pricing, and agent-ready outputs.
Analyze demos, meetings, tutorials, screen captures, and personal archives from a local file.
Bring a supported video URL into the same inspect → preview → read path, including individual YouTube links.
Extract audio artifacts, use available captions, or transcribe locally before cloud analysis is approved.
A repository-only helper validates and deduplicates confirmed public Reel URLs; it is not an installed Voidscape command.
Give an agent timestamped frames, transcripts, and manifests instead of asking it to guess what happened in a video.
The next steps extend source capture without changing the consent-first reading core.
Queue videos from a user-owned private playlist through the official Data API, then keep the normal analysis flow.
Apply the same inspect-before-send model to visual posts, slides, and image collections.
Bring saved talks, podcasts, and voice material into a consistent local transcription workflow.
Extract a shared interface only after the Instagram and YouTube paths prove the common behavior.
Directions worth testing after product, privacy, platform, and legal review.
Potential adapters for X bookmarks, TikTok favorites, LinkedIn saves, newsletters, and RSS collections.
Extend the evidence model beyond media to web reading, written research, and saved knowledge.
Make approved analysis artifacts easier for agent environments to discover and use.
Lower the setup barrier only after the local product, user controls, and operating model are ready.
Research directions—not current commitments—until their safety, cost, and platform constraints are validated.
Voidscape is useful when a recording contains information an agent cannot safely infer from a title, thumbnail, or prompt.
Bring a confirmed public Reel or video URL into a local queue, inspect it through the normal gate, then keep a timestamped note instead of another forgotten save.
Transcribe a recorded brainstorm locally, preserve the evidence, and let an agent compare ideas against the words that were actually said.
Install Voidscape, optionally set your local Library, then use a key-free fixture to inspect, preview, and read evidence. No paid or remote step is implied.
The installer adds the guided Voidscape skill plus the legacy compatibility entry point.
$ .\scripts\install-skill.ps1
Review local folders and transcription defaults first. Preferences save only with explicit confirmation.
$ python skill/scripts/voidscape.py customize
The fixture needs no account, key, or copyrighted media.
$ python scripts/create-demo-fixture.py
$ python skill/scripts/voidscape.py inspect samples/build-week-demo.mp4
$ python skill/scripts/voidscape.py preview samples/build-week-demo.mp4 --tier both --backend captions
$ python skill/scripts/voidscape.py read samples/build-week-demo.mp4 --tier both --backend captions --workdir samples/build-week-output
manifest.json, transcript.txt, and frames/, then answer with [MM:SS] citations. It reads evidence instead of guessing what happened in a video.
Voidscape makes the boundary visible: what stays local, what costs, and what exists today.
Not by default. Local files, sidecar transcripts, and local transcription stay on your machine. Any cloud transcription route needs a current --allow-cloud approval; a first local model download needs its own --allow-model-download.
A work folder containing selected frames, a transcript when requested, and a manifest that maps frames to timestamps. An agent can turn those artifacts into a Markdown note; the CLI does not pretend to write a semantic note itself.
Inspect is free source discovery. Preview is the cost and privacy decision. Read only follows once the path is acceptable and prepares the evidence an agent needs.
Audio-only reads use the installed CLI. Instagram support is a repository-only URL helper and user-observed development workflow, not an installed command.
Public URLs are the baseline. For media you are permitted to access, the CLI can optionally use a local cookie export while a browser-connected agent works from tabs only after your site approval. Voidscape never extracts your browser credentials, and first-party account connections are future work.
Those are planned directions. They are not part of this installed release, and text articles are not sent through the video engine.