With your agent

Hand your coding agent one line, in any project folder:

Read https://vos.so/agent.md and do what it says.

The address is the whole procedure. Your agent installs the vos CLI into the repo and runs vos setup, which puts the vos skills into its own directories and checks the machine, finds the product (the repo's dev server, or it asks you for a URL), writes a click path, rehearses it, records a take with the camera planned from the cursor, and opens the take in the studio for you. Every zoom it planned is draggable there. The first time, Chrome asks to let vos.so reach your local network; allow it. No account is needed for any of it.

What happens next

• Edits are patches. Ask for a change and the agent edits take/doc.json and re-renders. The browser never runs again.
• Hosting is asked for, never assumed. A link, a watch page or your shelf means vos push, and only then does the agent need a credential: vos login prints a code and a page for you to approve, and the agent never sees the key.
• The line is on every door. The same line sits beside Record on Home, beside the sample take on the studio's first screen, and in the paste block on the agent page, so you can hand it over from wherever you are.

Behind a login? The agent settles a session before it records, from the project's own test auth first, and never types a real password; the ladder is in the CLI contract. Taking turns with the agent on one version chain is Push and pull.