LibraOS for VS Code 0.4.1 (preview)

Preview release for installing by hand. Not on the Marketplace yet.

Install

Download libraos-0.4.1.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.4.1.vsix.

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

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

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

New in 0.4.1

Click an example to run it

• Examples marked ▶ run in one click on the Runtime this extension manages. The extension downloads only that example (11 files for First Agent, not the whole cookbook) and creates the Python environment if needed. It starts the Runtime if it is stopped, then runs the example in a terminal with a one-hour setup token, with the Runtime Log beside it.
• No folder dialog, no .env, no passwords. You confirm once the first time, or choose Always Run Without Asking.
• First Agent comes in three entries: Python, TypeScript and Bash. Each runs its own script directly.
• Async Jobs runs submit and resume in one go.

Smaller changes

• Examples that need the cookbook's own setup show what they need when clicked. The inline buttons are Run, Get Example and What It Needs. The tutorial and GitHub links are in the right-click menu.
• Marketing Team and Mission Console show strong model in the sidebar. The mission is planned as one JSON object with at least 10 tasks, which small local models fail; Claude Sonnet completed it in about 14 minutes. Kernel side: libraos/libraos#1752.
• For contributors: press F5 in this repository to run the extension from source, without building a .vsix.

LibraOS for VS Code 0.4.0 (preview)

Preview release for installing by hand. Not on the Marketplace yet.

Install

Download libraos-0.4.0.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.4.0.vsix.

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

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

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

New in 0.4.0

Watch the runtime

• Runtime Explorer. A new view shows the local runtime's agents: their bound knowledge collections, tool scope, calls (count, errors, latency, tokens) and memory. It also shows collections with their documents and bound agents. Debug Retrieval shows which chunks a question would retrieve, with scores.
• Runtime Log in a terminal. One line per agent or model call while your app runs, with latency, tokens and errors, plus server warnings.

Run cookbook examples on this extension's runtime

• Copy Setup Token. The project API key cannot create agents or ingest documents, so most cookbook examples need a setup token. This command gets a one-hour admin token for the local runtime. Its secret stays in SecretStorage.
• Run and Debug in the examples folder. Turn on Examples' Run and Debug and VS Code's Run button and debugger run First Agent (Python), Ticket Routing, Document Q&A and HTTP Async Jobs against this runtime.
• Configure Embedding Model. Knowledge search needs embeddings. Point the runtime at Ollama or another endpoint. The command checks the model and sets the vector size to match.
• Reset Local Runtime Data. Starts the runtime's data over, after you confirm. Changing the embedding size on an existing runtime needs this.

Build an app

• FastAPI starter. For Python projects, Initialize LibraOS Project can create a FastAPI backend with POST /ask, plus a Run and Debug entry that starts it under uvicorn.

Smaller changes

• The Developer section lists your Personal licence first, then the optional Sign In.
• Example cards now say what each example needs on Runtime v0.2.2. All 16 examples were run end to end before this release.

Known issues (Runtime v0.2.2)

• The cookbook's Tools recipe cannot call its webhook. App-installed agents don't get their custom tools (libraos#1737).
• Changing the embedding size after the runtime's first start needs Reset Local Runtime Data (libraos#1738).
• Developer Licence benefits and instance registration still need a Console update that is not live yet.

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.

LibraOS for VS Code 0.3.1 (preview)

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

Install

Download libraos-0.3.1.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.1.vsix.

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

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

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

New in 0.3.1

• Cookbook v2 navigation. Browse Cookbook and the sidebar's Examples follow the cookbook's learning paths: Learn Step by Step, Explore by Capability and See Complete Applications, with SDK examples listed separately. New: Python First Agent, Tools, Memory and User Isolation, HTTP Async Job & Recovery, Personal Assistant, Marketing Team and Mission Console.
• See what an example needs before you open it: versions, Runtime settings, app folders, callback setup, users or sign-in clients, which Runtime to run it on, and how far it has been validated. A listing is not a compatibility certification.
• Open Tutorial opens an example's README. View Source opens a single-file example in an editor, or the GitHub folder for an example with several files.
• Cookbook setup or this Runtime? explains when to use the cookbook's own setup. The extension's Runtime is unchanged (v0.2.2).
• Sign-in prompt now says to paste or type the code in the browser to approve, matching the Developer Console's approval page.

Not yet

• Sign In works against the live Developer Console. Developer Licence benefits and instance registration still need a Console update that is not live yet; until then, registration reports that it is not available.
• Inference credits and Cloud Deployment are still marked as coming.

LibraOS for VS Code 0.3.0 (preview)

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

Install

Download libraos-0.3.0.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.0.vsix.

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

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

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

New in 0.3.0

• Personal licence by default. Personal use is free, needs no account and no sign-in, and the runtime never checks a licence. The sidebar shows Licence: Personal (default).
• Sign In is optional. It is only for claiming the free Developer Licence and its benefits. The Developer Licence covers personal use and non-production development inside an organization, and does not expire.
• Benefit-registered instances. With a Developer Licence, register up to 5 local runtimes for online benefits, and remove them from the sidebar. Registration is something you run; the runtime never calls out, and registering or removing never affects running it.
• Icons show up in the activity bar and the Extensions view (they had a solid white background).

Not yet

• The Developer Licence and instance registration need the updated Developer Console and runtime, which are not live yet. Until then, Sign In will fail, and registration reports that it is not available. Everything else (install, run, configure a model, initialize a project, examples) works without signing in.
• Inference credits are shown as coming. Cloud Deployment is still marked as coming.

LibraOS for VS Code 0.2.0 (preview)

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

Install

Download libraos-0.2.0.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.2.0.vsix.

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

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

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

New in 0.2.0

• Sign In / Sign Out to your LibraOS developer account with device sign-in: VS Code shows a one-time code and you approve it in the browser. VS Code never asks for a password; the session is kept only in VS Code's secret storage.
• Developer License in the sidebar, and Claim Developer License, which shows the terms and asks for confirmation first. A license is a record of rights; the runtime does not check it.
• Inference credits show "Account not linked", with a link to the MegaNova console. No balance is shown until accounts can be linked.
• Open Console opens the Developer Console.
• Runtime pinned to v0.2.2 (security release) by digest.

Not yet

• Sign-in and the license need the Developer Console, which is not live yet. Until it is, Sign In will fail. Everything from 0.1.0 (install, run, configure a model, initialize a project, examples) works without signing in.
• Cloud Deployment is still marked as coming.

LibraOS for VS Code 0.1.0 (preview)

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

Install

Download libraos-0.1.0.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.1.0.vsix.

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

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

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

What works

• Install, run and stop the LibraOS Runtime locally with Docker Compose. Images are pinned by digest.
• Configure the model endpoint: list its models, pick one, and test-call it before saving.
• Initialize a TypeScript, JavaScript, Python or Go project. This adds libraos.json, a quickstart file and a project API key.
• New VS Code terminals get LIBRA_OS_URL and LIBRA_OS_API_KEY.
• Cookbook and SDK examples, a sidebar and a status bar item.

Not yet

Sign-in, the Developer License and Cloud Deployment appear in the sidebar but are marked as coming.