Open your Koda sessions in Visual Studio Code. Every save goes to Koda, and edits made on the web, by you or your classmates, show up in VS Code straight away.
Getting started
Install Koda Sessions.
Click Koda: Sign in in the status bar (bottom left), or run Koda: Sign in from the Command Palette (⇧⌘P / Ctrl+Shift+P).
Your browser opens trykoda.dev. Click Connect VS Code. This works whether you sign in to Koda with Google, Microsoft or a password.
Back in VS Code, pick a session. Its files open as a folder.
Edit and save as usual. Each save uploads to Koda.
If your browser can't open VS Code links (some school computers block them), the page shows a code instead. Paste it into the box VS Code is showing.
What you get
Status bar. The bottom-left item shows the session you're in and whether your saves have reached Koda: saved, saving, offline or a problem. Click it for the Koda menu.
Open in the browser. Jump to the same session on trykoda.dev to run your code, ask Bit or see the lesson.
Live updates from the web. Changes made on Koda appear in your files as they happen. If you have unsaved edits to the same file, VS Code asks before replacing anything.
Reload files from Koda. This replaces your files with Koda's copy. It tells you first which files would change, including any unsaved edits.
One editor at a time. While you have a session open in VS Code, nobody else can open it in theirs.
Commands
Command
What it does
Koda: Sign in
Sign in through your browser
Koda: Sign in with email and password
Sign in without the browser (password accounts only)
Koda: Open session…
Pick a session to open in this window
Koda: Open this session in the browser
The same session on trykoda.dev
Koda: Save this file to Koda now
Upload the current file without saving it again
Koda: Reload files from Koda
Replace your files with Koda's copy
Koda: Sign out
Sign out here and end this login
School and district Wi‑Fi
Many schools decrypt HTTPS for filtering. VS Code extensions use their own connection, so signing in can fail with fetch failed even when the website works.
Ask IT for the root CA certificate used for inspection. Save it as a PEM file and set Koda: Extra Ca Certs File to its path.
If traffic must go through a proxy, set Koda: Https Proxy to the same address your browser uses.
On slow networks, increase Koda: Request Timeout Seconds.
As a last resort, and only if IT approves, Koda: Allow Insecure Tls turns off certificate checks.
Settings
Open Settings and search for Koda.
Setting
What it does
Api Base Url
https://trykoda.dev. Change it only if your school runs its own Koda server.
Sync On Save
Upload files when you save them (on by default)
Sync Remote From Web
Bring in edits made on the web as they happen (on by default)
Acquire Cursor Lock
Stop others opening a session in their editor while you have it open (on by default)
Request Timeout Seconds / Network Max Attempts
For slow or unreliable networks
Extra Ca Certs File / Https Proxy / Allow Insecure Tls
For school networks (see above)
Privacy
Your login is kept in VS Code's secret storage. Signing out ends it on Koda as well. Settings → Account → Sign out other devices on trykoda.dev signs VS Code out the next time it checks in, which happens when VS Code starts or you open a session. Session files are kept in the extension's own storage folder. All traffic goes to trykoda.dev over HTTPS.
Questions or problems: use the Issues link on this page.
