What your agent does on your machine
Every file the setup writes, what leaves your machine and when, how to check it and how to take it back out.
Every file the setup writes, what leaves your machine and when, how to check it and how to take it back out.
The line you hand your agent does five things on your machine, in this order, and uploads only because you asked for a link.
Record a demo video of this app with vosso. The steps are at https://vos.so/agent.md. Give me the vos.so link when it's done.The steps are a short file you can read first: vos.so/agent.md. It opens by telling the agent the only things it may ask for, and to stop and tell you if anything asks for more.
| What | Where it lands |
|---|---|
Installs one dev dependency, @vosjs/cli | package.json, your lockfile, node_modules |
| Adds the vos skills | Your agent's skills folder in the repo: .claude/skills, .cursor/skills, .codex/skills, .github/copilot/skills or .agents/skills |
| Writes one marked block | AGENTS.md, or CLAUDE.md when that is the file your repo keeps |
| Records your app | A take folder in the repo: the footage, the cursor track, the click script and doc.json |
| Uploads the take, because the line asks for a link | Your account on vos.so, private until you publish it |
Nothing here adds a hook, changes a settings file or registers an MCP
server. The block in AGENTS.md sits between two comment lines marked
vos:begin and vos:end, and a second run replaces its own text and never
yours.
Until the upload, nothing about you or your app goes anywhere. The CLI sends no telemetry.
127.0.0.1 to the studio page in your
browser. Chrome asks once to let vos.so reach your local network. The
studio reads the files from your machine and uploads nothing until you
save.assets.vos.so.doc.json and the click
script. Your prompt is shown on the watch page in your words, and you can
take it off there. The upload lands private, and a key can never publish.vos login, you
approve a code on vos.so, and one key is stored in
~/.config/vos/credentials. The agent never sees a password.Leave the last sentence off the line and the agent stops after opening the take. Nothing is uploaded.
A machine with no browser at all is the one exception: there the agent can
ask vos.so's own recorder to visit a public page, with
vos record --hosted. It sends the page's address and the click script.
npm view @vosjs/cli dist.attestations
npm audit signaturesThe first shows the signed record of where the package was built. The second checks every package in your install against the registry's signatures. The package has no install scripts, and neither does anything it depends on.
The source is public: the CLI and the engine at github.com/vosjs/vos, the skills at github.com/vosjs/skills. A signed record says where a package came from. It is not a promise about what the code does, which is why the source is there to read.
Your agent tells you its plan before it starts. To see exactly what setup would write, without writing anything, install the package and ask it:
npm i -D @vosjs/cli
npx vos setup --planIt prints the skills folders and the skills it would copy into each, the
command it would run if there is no browser, and the exact block for
AGENTS.md. Then run npx vos setup yourself and give your agent the task:
Record a demo video of this app with the product-video skill. Give me the vos.so link when it's done.vos setup ends with a list of every path it created or changed.
--no-browser keeps it from downloading Chromium, --no-rules leaves
AGENTS.md alone and --no-skills copies no skills. The steps your agent
reads at vos.so/agent.md are also in the package: npx vos guide prints
them.
npx vos setup --removeIt removes the vos skills it copied and the marked block, and leaves the
rest of AGENTS.md exactly as it was. A skill folder with one of those
names that is not the vos skill is kept, and so is a skill that is a link
to somewhere else. npx vos setup --remove --plan shows the list first.
It never removes a browser, the package or a sign-in. It prints the two
commands that do, for you to run: npx vos logout, then
npm rm @vosjs/cli.
A video you pushed is deleted from its menu on vos.so. Deleting moves it to Trash, where it can be restored for a while.
Your agent tells you what happened and asks before it reports anything.
With your yes it runs npx vos feedback, which prints the address and
every word it is about to send, and sends no sign-in with it.
npx vos feedback --dry-run prints and sends nothing.
The plugin is another way in, and Claude Code shows what it will install before you accept. It carries the same skills, one command and two hooks. Both hooks are plain Node files that read your repo, print one line and never use the network:
media/, it says
what the demo is and the command that records it again.Their source is in the plugin's scripts folder.
vosso uses vos.so and its subdomains, the @vosjs scope on npm, and
github.com/vosjs. A line that names anything else did not come from
vosso. Report a security problem to the address in
security.txt.