In the editor

aimo for VS Code

An agent inside the editor, on your Bosphorus platform. It reads and changes your code, runs your commands and reaches your organisation's tool servers — signed in as you, asking before it changes anything, and under the same policy, quota and audit trail as everyone else.

aimo for VS Code 1.2.1

Download the extension

File: aimo-1.2.1.vsix
Size: 192 KB
Version: 1.2.1
Requires: VS Code 1.85 or later
Published: 15 October 2026
SHA-256 checksum: 5e02b1489e2f3ffd26e46cf9a0e482a0bf61707ee7fe729d8d3f91b4abad207c

The extension works with a Bosphorus installation: you need your organisation's gateway address and your corporate account. Your administrator can give you both.

What it does

A coding agent that plays by the platform's rules

An agent in the editor

It reads, searches and edits the files in the open folder, runs commands there and reads the problems the editor reports. The open file and your selection travel with your question, and you can paste or drop a screenshot for a model that reads images.

Nothing changes behind your back

An edit is shown as a diff before it is applied, and a command before it runs. Afterwards you can review the files a turn changed and put them all back in one step.

Signed in as you

It signs in with your corporate account and receives a personal key of its own. Every model request counts against your quota and rate limits, follows your model profile and is recorded under your name.

Tool servers on demand

Your organisation's tool servers are reached through the platform's governed relay, which keeps their addresses and credentials. The model looks up the tool it needs, so a large catalogue costs nothing; pin the one or two you use all day.

Your keys stay yours

Where your installation keeps people's keys in OpenBao, the extension signs you in to your own vault. Tool servers, terminals and the commands it runs receive the values; the model is given their names, and a value a command prints as it is reaches the model as `[vault:NAME]`.

A repository cannot redirect it

Where it signs in, where your key goes and whether it asks first can be set only in your own settings, never in a project's. In Restricted Mode automatic approval is switched off, so every edit and command is asked about, and no command receives a vault value.

Before you install

What you need

VS Code 1.85 or later.
Your organisation's gateway address, for example https://ai.corp.example. Your administrator gives it to you.
Your corporate account on the identity provider the platform uses — Microsoft Entra ID, or an OpenID Connect provider such as Keycloak.
A network path to the gateway. Many installations answer only on the company network or over VPN.

Install

Install it in VS Code

The extension is a single file. Install it from inside VS Code, or from a terminal.

From VS Code

Download aimo-1.2.1.vsix with the button above.
Open the Extensions view: Ctrl+Shift+X, on macOS Cmd+Shift+X.
At the top of the view, open … (Views and More Actions) and choose Install from VSIX… in that menu.
Choose the file you downloaded. When VS Code reports that the installation is complete, the AIMO icon appears in the activity bar. If VS Code asks you to reload the window, do so.

From a terminal

In the folder you downloaded it to:

code --install-extension aimo-1.2.1.vsix

If you use VS Code profiles, name yours. Extensions are installed per profile, and the command above installs into the Default profile only, so a window that opens in another profile will not show AIMO. Installing from VSIX inside a window uses that window's profile.

code --install-extension aimo-1.2.1.vsix --profile "My Profile"

On macOS, if code is not found, first run Shell Command: Install 'code' command in PATH from the Command Palette.

Check the file (optional)

The SHA-256 checksum the command prints must equal the one shown beside the download button. PowerShell prints it in capitals; letter case does not matter.

macOS, Linux

shasum -a 256 aimo-1.2.1.vsix

Windows (PowerShell)

Get-FileHash .\aimo-1.2.1.vsix -Algorithm SHA256

First run

Connect, sign in, ask

After installing, AIMO offers a short walkthrough — Show me around — that follows the same steps.

Connect to your gateway

Open the Command Palette (Ctrl+Shift+P, on macOS Cmd+Shift+P), run AIMO: Set Gateway URL and enter the address your administrator gave you. It is kept in your own user settings.

Sign in

Click the AIMO icon and choose Sign in. A short code is copied to your clipboard and the sign-in page opens in your browser: paste the code and finish signing in. The extension then receives your personal key and keeps it in VS Code's secret storage.

Pick a model — or don't

Left alone, the extension uses the model the platform recommends for you. AIMO: Select Model lists every model you may use, what each is confirmed to do and the size of its context window.

Ask

Open the chat with Ctrl+Alt+A (on macOS Ctrl+Cmd+A) and ask it to explain, build or fix something. To hand it a piece of code, select it and choose AIMO ▸ Explain This or Fix This from the editor's context menu.

Connect your vault, if you have one

Where the platform keeps people's keys in OpenBao, run AIMO Vault: Sign in to the Vault. Your browser signs you in and hands back to the extension on localhost:8250. The vault's address is worked out from the gateway's; set aimo.vault.address if yours is elsewhere.

Governance

Governed like every other client

Every model request crosses the same six gates as the chat workspace and every agent: identity, policy, quota, rate limit, fair-share admission and audit.
Administrators see the extension's requests on the same activity and usage pages, each chat grouped as one session.
Tool calls go through the platform's relay, which records each one: the extension never learns a tool server's address or credentials, and your vault values go to tools and commands rather than into the conversation.
Files that usually hold credentials — .env, private keys, *.tfvars and the like — are read only after you agree.

Updates

Updating and removing it

VS Code does not update an extension installed from a file. When a newer version appears on this page, install it the same way: it replaces the old one and keeps your settings and your sign-in.
AIMO: Sign out removes your personal key from this machine and signs you out of the vault too.
To remove the extension, sign out first, then choose Uninstall on AIMO in the Extensions view, or run code --uninstall-extension morten.aimo.

Troubleshooting

If something does not work

What you see	What to do
No AIMO icon after installing	The window uses another VS Code profile than the one you installed into, or it is a remote window (SSH, WSL, a container), where the extension runs on the remote side. Install again from that window with Install from VSIX…, or add `--profile` to the command.
`could not reach …/api/identity/config`	The gateway address is not set, is mistyped, or cannot be reached from here. Run AIMO: Set Gateway URL again and check that you are on the company network or VPN.
The sign-in page refuses the code, or the sign-in never completes	Ask your administrator whether the platform's identity provider allows device sign-in for the editor extension.
`port 8250 is busy` when signing in to the vault	Another vault sign-in is waiting on that port. Finish or cancel it, then try again.
The vault sign-in page opens, but nothing happens afterwards	You are in a remote window (SSH or a container). Forward port 8250 to your machine, or sign in from a local window.
A tool server is missing	You have not been granted it, or your team may not use it. Ask your administrator.
Anything else	Run AIMO: Show Log: the log says what the extension tried and what came back.

No Bosphorus installation yet?

The extension needs a platform to talk to. A proof of concept stands Bosphorus up on your own cluster, with your identity provider and your rules, and hands you the evidence at the end.

Request a PoC Talk to us