LibraOS for VS Code 0.3.2 (preview)

Fifth preview, for installing by hand. Not on the Marketplace yet.

Install

Download libraos-0.3.2.vsix, then either:

• in VS Code, open the Extensions view, choose … › Install from VSIX… and pick the file; or
• run code --install-extension libraos-0.3.2.vsix.

Cursor and other VS Code–based editors install it the same way.

Check the download: sha256sum -c libraos-0.3.2.vsix.sha256

Requires VS Code 1.95 or later and Docker with Compose v2.

New in 0.3.2

• Examples open and run in VS Code. Click an example in the sidebar. The first time, choose where to keep the examples; the whole cookbook is downloaded once into a libraos-cookbook folder there, so files shared between examples are in place. You get the source file from disk, its README beside it, and a terminal with the run command typed in, not run.
• Python is set up for you. For a Python example, LibraOS offers to create a .venv with the examples' pinned packages (including libraos-sdk 2.0.0), using Python 3.10 or newer. This fixes ModuleNotFoundError: No module named 'libraos'. Run and Debug in the examples folder use that .venv.
• First Agent in Python, TypeScript or Bash. TypeScript runs with npx tsx and needs no Python.
• get-started/.env from the template, which the cookbook's examples read for the local Runtime's settings.
• Updating the cookbook copy keeps your .env, .venv and your own files.

Not yet

• Most cookbook examples create agents, so they run against the cookbook's own local Runtime with its setup token, not the Runtime this extension manages. Each example's What This Example Needs says which.
• Developer Licence benefits and instance registration still need a Console update that is not live yet. Inference credits and Cloud Deployment are still marked as coming.