Four short videos, each with its steps written out below. Installing takes about two minutes and needs no admin rights.
One zip file contains the command line tool, the VS Code extension, the Excel add-in and an installer. It copies syntax-code.exe to %USERPROFILE%\.local\bin and adds that folder to your PATH.
syntax-code-windows.zip.From the Syntax Code folder on SharePoint (button above). Sign in with your Syntax account if asked.
Extract first. Do not start the installer from inside the zip.
install.ps1 → Run with PowerShell.The script is in the folder syntax-code-windows inside the extracted folder. No admin rights needed; Windows asks once to confirm a local certificate for the Excel add-in. If VS Code is installed, the extension is installed with it.
syntax-code.It must be a new window, so the changed PATH is picked up. The first start reports that the API key is missing and names the settings file.
In PowerShell, run notepad $HOME\.syntax-code\config.toml. Change the line # api_key = "sk-...": remove the #, put your key between the quotes, save. How to create the key.
syntax-code again.The welcome screen appears. Start it in the folder of the project you want to work on.
Remove: delete %USERPROFILE%\.local\bin\syntax-code.exe and uninstall the extension SyntaxCode in VS Code. Your API key is in the folder .syntax-code in your home folder; delete that too.
One zip file contains the command line tool for Apple silicon and Intel, the VS Code extension, the Excel add-in and an install script. It copies syntax-code to ~/.local/bin.
syntax-code-macos.zip.From the Syntax Code folder on SharePoint (button above). Sign in with your Syntax account if asked.
Finder unpacks it into the folder syntax-code-macos.
⌘ + Space, type “Terminal”, Enter.
cd ~/Downloads/syntax-code-macos && bash install.sh
Please run it in Terminal, not by double-click: macOS blocks downloaded scripts. No admin password is needed; macOS may ask for your login password to trust a local certificate for the Excel add-in.
syntax-code.The first start reports that the API key is missing and names the settings file.
Run open -e ~/.syntax-code/config.toml. Change the line # api_key = "sk-...": remove the #, put your key between the quotes, save. How to create the key.
syntax-code again.The welcome screen appears. Start it in the folder of the project you want to work on.
Remove: delete ~/.local/bin/syntax-code and uninstall the extension SyntaxCode in VS Code. Your API key is in the folder .syntax-code in your home folder; delete that too.
Syntax Code talks to GenAI Studio on your behalf, with your own personal key. The key is stored in the settings file on your machine.
With your company account.
The user menu is at the top right.
For example “Syntax Code”.
It is shown only once. Put it into config.toml as described in the install steps.
The installer adds the extension SyntaxCode to VS Code. It brings its own copy of the command line tool and uses the same API key.
Click the octopus icon in the Activity Bar or press Ctrl+Shift+Y (macOS: ⌘⇧Y). After installing, reload VS Code once: Developer: Reload Window.
The agent is told which file is open; your selection and the file’s error messages are sent along. Every file read and every command appears as a card. To stop a request, click the send button, which turns into a stop button, or type /cancel.
In the settings, set syntaxCode.permissionMode to interactive, then reload VS Code (Developer: Reload Window); the setting is read at start. Each edit then shows its changed lines and waits for Apply or Reject; a card that gets no answer within 60 seconds is rejected. The default auto applies changes without asking.
Select it, right-click, Send Selection to Chat: the selection is placed in the message box. Add to Syntax Code Chat, in the same menu and in the Explorer, attaches the whole file.
Download syntax-code-linux.zip from the same SharePoint folder, then run:
unzip syntax-code-linux.zip cd syntax-code-linux bash install.sh
It installs to ~/.local/bin for x64 and arm64. The API key goes into ~/.syntax-code/config.toml, as on macOS.
install.ps1 does not startOpen a terminal in the extracted folder and run powershell -ExecutionPolicy Bypass -File install.ps1.
syntax-code is not foundClose the terminal and open a new one, so the changed PATH is picked up. On a Mac without a ~/.zshrc the installer cannot add the folder: run echo 'export PATH="$PATH:$HOME/.local/bin"' >> ~/.zshrc once and open a new Terminal window.
The installer needs the code command. Install by hand: Ctrl+Shift+P → Extensions: Install from VSIX… → the .vsix file from the extracted folder.
In a running session, type /update. It shows what changed and asks before it installs.