Unison shows your project as a visual canvas on the Unison website: every file is a block, laid out like
your folders. You keep editing in VS Code.
This extension is the link between the two. It connects a folder on your computer to a Unison project, and
opens a file in VS Code when you click it on the canvas.
Preview. Unison is in early preview, and things will change. In this version the canvas shows the
folder as it was when you connected it; updating it live as you save is coming next.
How to use it
Connect a folder. On the Unison website, click New project, then choose the folder in VS Code.
The canvas opens on the website. The first time only, your browser and then VS Code ask to allow the link,
and VS Code asks you to confirm your Unison account.
Open a file. Click a file on the canvas and choose Open in VS Code. The file opens as a tab here.
Your files stay on your computer, where they are. Unison never writes its own files into your folder.
Commands
Unison: Connect folder - connects a folder with a code from the website, if the link from the
website did not open VS Code.
Unison: Sign out - signs this VS Code out of Unison. The website stays signed in.
Privacy
When you connect a folder, Unison uploads the names and the text of your project files. Some things are
never uploaded:
Secrets. Files such as .env, .npmrc, private keys and certificates, and folders such as .ssh
and .aws, are never read and never uploaded, not even their names. No setting can change this.
Files your .gitignore leaves out. Without a .gitignore, the usual generated folders such as
node_modules and dist are left out.
The content of binary files and of files over 1 MB. They appear on the canvas by name and size only.
Before anything is uploaded, you choose the folder yourself. After the upload, Unison lists what it left out.
