Set up your coding agent without touching the terminal
This guide walks you from the download to your first conversation with your agent on Windows 10 or 11. You will see what the app does, what you decide and what each button changes.
What IA Olympus Agent Installer is and is not
IA Olympus Agent Installer is a desktop application that installs and connects coding assistants to your IA Olympus account. You choose the agent; the app prepares the dependencies, writes the configuration and checks that everything responds.
What you can expect
- Detects which agents are already installed and which can be installed.
- Installs npm agents in a private folder inside your user profile.
- Writes the configuration so the agent uses IA Olympus.
- Checks the connection and the available models.
- Lets you reconfigure, repair and uninstall from the interface.
What not to expect
- It does not install, update or uninstall Node.js.
- It does not disable Defender, SmartScreen or the firewall.
- It does not run code produced by an agent.
- It does not send telemetry or usage data.
- It does not make an unsupported product installable, such as Qoder.
The app is not a chat. It is the installer and control panel that gets your agent ready to use on its own, from its own window or terminal.
Who it is for and what an “agent” is
An agent is a program that understands natural-language instructions and works with your project: it reads files, proposes changes and performs tasks when you ask. Some live in their own window and others in the terminal.
This tutorial is written for people who have never installed a coding agent. You do not need to know what an environment variable is or edit configuration files: the app does it for you and explains each step in plain language.
Beginners
You want to try an assistant without learning commands. Follow the guide in order and use the app buttons.
Windows users
You already work on Windows 10 or 11 and prefer a graphical installation without administrator rights for npm agents.
Small teams
You need to leave an agent configured in a repeatable way and know how to repair or remove it later.
Real requirements
| Requirement | Details | Required? |
|---|---|---|
| Operating system | Windows 10 or 11, 64-bit (x64). | Yes |
| Internet | Needed to download the agent, validate the key and check the models. | Yes |
| IA Olympus account | An active key with balance. Without it you can install, but not validate the connection. | Yes, to use the agent |
| Free disk space | Depends on the agent. The details panel shows the estimate before installing. | Per agent |
| Node.js and npm | Only for agents that need them. The app checks the version and blocks only the affected agent. | Per agent |
| WSL2 | Only for Hermes. Without WSL2, Hermes is not installed or simulated. | Hermes only |
| Administrator rights | Not requested for npm agents. Some guided flows or WSL2 may ask separately. | Case by case |
The app checks these requirements before installing and shows the result in each agent panel. A missing requirement does not block the other agents.
Download the installer
NSIS installer for Windows x64 · 121,546,387 bytes · SHA-256 verified
The Authenticode status of this version is NotSigned. That does not mean the file is malicious, but Windows cannot confirm who created it. Before running it, check the SHA-256 and make sure you downloaded it from IA Olympus.
Always download from a source you control. If someone sends you the file through a messaging app or you find it on a third-party site, verify the hash before opening it. The Verify the download section has the exact command.
SmartScreen and Windows warnings
Because the installer is not signed, Windows may show a SmartScreen warning. That warning is a normal protection and you should not turn it off. These are the options you may see:
| What you see | What it means | What to do |
|---|---|---|
| “Windows protected your PC” | Windows does not recognise the file signature. | Check the hash. If it matches and you downloaded from IA Olympus, you may continue knowingly. |
| “More info” | Expands the options in the warning. | Read them before deciding. Do not run the file if you do not trust its origin. |
| “Run anyway” | Allows a file Windows could not verify. | Use it only after verifying the SHA-256. |
Do not disable Defender, SmartScreen or the firewall to “avoid the warning”. If the file comes from an unknown source, do not run it even if the hash looks correct: the hash only confirms the file is the expected one, not that the source is legitimate.
Per-user installation
The installer is NSIS-based and is designed to install for your user only. It does not need administrator rights for the application or for npm agents, and it does not change the system for other users on the computer.
Open the downloaded file
Double-click
IA-Olympus-Agent-Installer-Setup-x64.exe. If SmartScreen appears, follow the previous section.Follow the wizard
The graphical wizard shows the installation path and progress. Do not use an undocumented silent mode.
Wait for it to finish
Shortcuts are created at the end and the application opens. The installation does not download agents by itself.
Check the version
The app must show 1.0.4. If you see another version, close it and run the correct installer again.
The app warns before any elevation. npm agents are installed in a private folder in your profile. WSL2 and some guided installers may ask for administrator rights on their own; in that case you will see why before continuing.
Open the application
When the installation finishes, the app opens automatically. From then on you can open it from the Start menu or the desktop shortcut. The first screen is the welcome page:
The welcome screen installs nothing. It only introduces the flow and reminds you that the app does not silently install Node.js or send telemetry. You can close it and reopen it whenever you want.
Switch between Spanish and English
The header has two buttons: Español and English. The active language is highlighted and the preference is kept after closing and reopening the app. The change affects the whole interface, not only the headings.
If you are reading this guide in English but your app is in Spanish, press “English”. If you prefer Spanish, press “Español”. Agent and model names are not translated.
The eight agents and their states
The list on the left shows eight agents. Above it you have a search box, a status filter and the fixed This computer: Windows indicator, which confirms the detected system.
What each state means
| State | What it means | What you can do |
|---|---|---|
| Available | The requirements are met and the agent can be installed. | Press “Install”. |
| Requires Node.js | Node.js is missing or the detected version is below the agent minimum. | Open the official Node.js page and check again. The app does not install it. |
| Requires WSL2 | The agent runs inside a Linux environment and WSL2 is unavailable. | Read the explanation and open the official guide. |
| Requires guided installation | There is no reliable silent installer; follow the vendor’s official flow. | Open the official download and check again afterwards. |
| Already installed | The app detected the program with a valid version. | Reconfigure, repair, test the connection or uninstall. |
| Not available | The current product cannot be configured against IA Olympus. | Nothing: it is not installed or configured. |
| Requires administrator rights | The flow needs elevation and the app warns first. | Review the reason and decide whether to continue. |
The eight agents
| Agent | What it is for | State observed in the capture |
|---|---|---|
| Codex | Reads your project, proposes changes and runs coding tasks. | Already installed · 0.164.0 |
| Claude Code | Conversational agent for coding with context in the terminal. | Available with Node.js 24.22.1 |
| OpenCode | Terminal agent to talk to your project and change code. | Available |
| OpenClaw | Memory and channels on your own computer, with a local service. | Available when Node.js is in range |
| Hermes | Persistent memory and reusable skills inside WSL2. | Requires WSL2 |
| Reasonix | Works from the terminal with providers you declare. | Available |
| WorkBuddy / CodeBuddy | Application and CLI with custom models. | Requires guided installation |
| Qoder | Assistant that does not support a custom base URL in this version. | Not available |
The state depends on your computer. With another Node.js version, Claude Code or OpenClaw may appear blocked while the rest remain available.
Choose an agent and install
Select an agent in the list. On the right you will see its details: a beginner explanation, what it is for, what you need, what will be installed and where. If everything is in order, the Install button becomes active.
The summary installs nothing. “Install now” is the final confirmation. If you cancel in the summary, nothing is written. If the installation fails, the app shows the error and lets you retry without leaving the agent half-installed.
On a computer where the agent already exists, the app does not duplicate the installation: it shows Already installed and offers Reconfigure, Repair, Test connection and Uninstall. That is the case for Codex in this capture.
Your IA Olympus key
To connect the agent to your account you need a IA Olympus key. It starts with sk-iaolympus-. The app asks for it in a dialog with a password field, a Paste button and a Show/Hide control.
How your key is handled
- The app trims surrounding spaces before validating.
- A key with the wrong prefix is rejected locally, without sending it to the network.
- The validation result never reveals the key or its contents.
- The key is stored in the system secure store, not in the agent configuration files.
- You can delete it from the interface at any time.
Do not paste it into chats, emails, screenshots, reports or repositories. If you suspect it has been exposed, revoke or rotate it from your account and save a new one.
When an agent supports environment variables, its configuration stores a reference to IAOLYMPUS_API_KEY and the key is injected only into the agent process. The only documented exception is Reasonix’s private file, protected with user permissions.
Installed, configured and connection validated
These are three different things and the app shows them separately. Do not call an agent “ready” just because its configuration file exists.
| State | What it proves | What it does not prove |
|---|---|---|
| Installed | The program is present and reports a version. | That it is connected to IA Olympus. |
| Configured | The app wrote the IA Olympus configuration to the right path. | That the account works or the key is valid. |
| Connection validated | The key works and /v1/models returns the expected models. | That the agent has held a conversation. |
The 09-success.png capture was not obtained because it requires a real key and a validated connection, and this run used no real key and started no simulated service. No image was fabricated. The final screen shows the three states above separately; you can check them in your own installation after validating the key.
Connection test and models
The Test connection button sends a GET /v1/models request to IA Olympus. If the key is valid and the network works, the response is HTTP 200 and contains exactly two public models:
iaolympus-lowiaolympus-pro
The test does not spend conversation tokens: it only checks that the account responds and which models are available. It sends no prompts and runs no code.
If there is no connection, the app shows a specific network message, different from “invalid key”. That helps you tell whether the problem is your Internet or the credential. If the key is correct but has no balance, the message is different too.
Connection validated, both models and the time of the last check. If you delete the key, that mark disappears and the agent asks for a key before testing again.
Qoder: not available in this version
Qoder appears in the catalogue so you know it exists, but it is marked Not available. The current product does not allow a custom base URL, so the app cannot connect it to IA Olympus.
Do not try to force its installation or change its configuration by hand to point it at IA Olympus. If the product later supports a custom base URL, the app will say so in a new version.
WorkBuddy / CodeBuddy: guided installation
WorkBuddy / CodeBuddy has no reliable official silent installer. That is why the app does not pretend to install it automatically: it offers the official download, explains the steps and then checks whether the program appears installed.
Open the official download
The app opens the vendor page. Download from there, not from a mirror.
Complete the vendor installer
Follow its steps. It may ask for administrator rights; that is its own installer, not IA Olympus’s.
Return to the app and check
Press “Check again”. If the app detects the program, it enables the IA Olympus configuration.
Configure and test
Only then is the configuration written and the connection test available.
If the vendor changes its installer, the app may not detect it. In that case certification stays “guided” and not as a verified automatic installation.
Hermes and WSL2
WSL2 lets Windows run a small Linux environment, like a separate window. Hermes is installed inside that environment, so it cannot work without WSL2. The app does not pretend it is installed just because a configuration file exists.
How to prepare it
Open the official guide
The “Open WSL2 guide” button leads to Microsoft’s documentation. Read it before running commands.
Install WSL2 with permission
The process may ask for administrator rights and restart Windows. Do it only if you agree and have a VM snapshot or backup.
Check again
After the restart, open the app and press “Check again”. If WSL2 and a distribution are available, Hermes installation is enabled.
Install Hermes inside WSL2
The app writes the configuration and checks that the program really responds. It is not marked installed just because the configuration exists.
On this capture machine WSL2 was not available. Hermes is therefore documented and pending a live test, not certified.
Node.js: the app does not touch it
Several agents are written in JavaScript and need Node.js, the program that runs them. The app never installs, updates, reinstalls or uninstalls Node.js. It only detects it and checks the version.
| Situation | What the app does | What you do |
|---|---|---|
| Node.js is not installed | Marks “Requires Node.js” only on the agents that need it. The others remain available. | Open the official Node.js page from the app, install the recommended version and check again. |
| The version is old | Shows the detected version, the required minimum and blocks that agent. | Update Node.js from the official site and check again. |
| The version is in range | Shows the detected version and allows installation. | Continue with the agent installation. |
Minimums depend on the agent. For example, Claude Code requires Node.js 22 or newer and OpenClaw requires a specific range: >=24.22.1 <25 or >=26.12.1. If it is not met, OpenClaw stays blocked and is not installed by force.
The app installs npm agents in a private folder in your user profile and does not request administrator rights for that. If an agent needs another method, it says so before continuing.
Maintenance: reconfigure, repair, test and uninstall
When an agent is already installed, its panel changes from “Install” to a set of maintenance actions. The existing installation is not duplicated.
Reconfigure
Writes the IA Olympus configuration again. It does not duplicate blocks or lines: it replaces what the app wrote before. Use it if you changed your key or model.
Repair
Fixes a damaged or incomplete configuration. It preserves configuration that was already there and creates a backup first if needed.
Test connection
Checks the key and the models with GET /v1/models. It does not spend tokens and does not run the agent.
Uninstall
Removes the package managed by the app, its IA Olympus configuration and its shortcut. It does not remove a global installation that existed before and was not created by the app.
If an agent has unrelated configuration — for example, another provider you declared — Repair does not delete it. The app only touches the block it manages.
Security and privacy
- HTTPS: communication with IA Olympus is encrypted. The app does not disable certificate validation.
- Secure store: the key is stored in the system-protected store, not in plain text inside the project.
- No telemetry: the app sends no usage data or analytics.
- Sanitised logs: logs do not include the key, authorization headers, cookies, full prompts or full responses.
- Minimal configuration: agents point only to IA Olympus and reference
IAOLYMPUS_API_KEY, except Reasonix’s private file. - No generated code: the app does not run code produced by an agent.
Do not share the key, store it in repositories or paste it into screenshots. If it is exposed, revoke or rotate it and validate a new one from the app.
Troubleshooting
| Problem | What you see | What to do |
|---|---|---|
| SmartScreen blocks the installer | “Windows protected your PC”. | Verify the SHA-256 and the origin. Do not disable the protection. If you do not trust it, do not run it. |
| No Internet | A specific network message when validating the key. | Check the connection, try again and tell this error apart from an invalid key. |
| Node.js is missing | “Requires Node.js” in the agent panel. | Open the official page from the app, install Node.js and press “Check again”. |
| Node.js is old | A detected version below the minimum. | Update from the official site. Do not force the agent installation. |
| WSL2 is unavailable | “Requires WSL2” on Hermes. | Read the explanation, open the official guide and check again after installing it. |
| Invalid key or no balance | A clear error, without showing the key. | Check the prefix, paste the key again and check your account balance. |
| The installation fails | An error with the phase and the reason. | Retry from the app. If it persists, use Repair or uninstall and start again. |
| The app does not open | The window does not appear. | Close any leftover process, reopen from Start and, if it still fails, reinstall the app. |
Check that no window is left open in the background. Reinstalling does not delete your agents or unrelated configuration, but it is better to close the app properly.
Frequently asked questions
Do I need to know how to code to use this?
No. The app installs and configures for you. Coding is what you will do later with the agent, if you want; this tutorial only covers getting started.
Is the app a chat?
No. It is the installer and control panel. Once configured, you open the agent separately from its shortcut or terminal.
Can I use several agents at once?
Yes. Each one is installed and configured separately. The key is the same and the app checks each panel independently.
Is the key stored in the agent files?
No, except Reasonix’s private file, which is the documented exception. Other configurations reference IAOLYMPUS_API_KEY and the key is injected only into the process.
What happens if I delete the key?
The app removes it from the secure store and clears the validation marks. Agents remain installed and configured but cannot authenticate until you enter a new key.
Does uninstalling an agent delete unrelated configuration?
No. The app removes only what it manages. If you had other configuration or a previous global installation, it is preserved.
Can I use Qoder?
Not in this version. The product does not support a custom base URL and the app keeps it as Not available.
Why is the installer not signed?
That is the state of this build: Authenticode NotSigned. Verify the SHA-256 and download only from IA Olympus. Do not disable SmartScreen.
Does the app send data anywhere?
It sends no telemetry. It contacts IA Olympus only to validate the key and check the models when you ask.
Verify the download
The SHA-256 is a fingerprint of the file. If it matches the expected value, the file is exactly the published one. You can compute it in PowerShell:
Get-FileHash -LiteralPath .\IA-Olympus-Agent-Installer-Setup-x64.exe -Algorithm SHA256Expected value for version 1.0.4:
4eef6a0737ba443dca8f8882b51fcb07fef55c5fbf58161db7d6d549c192cc41
| Item | Expected value |
|---|---|
| File | IA-Olympus-Agent-Installer-Setup-x64.exe |
| Version | 1.0.4 |
| Size | 121,546,387 bytes |
| SHA-256 | 4eef6a0737ba443dca8f8882b51fcb07fef55c5fbf58161db7d6d549c192cc41 |
| Authenticode signature | NotSigned |
Download and checksum links:
Limitations and uncertified states
- No real key: this run used no real key. Account validation and the final success screen were not captured;
09-success.pngdoes not exist and was not fabricated. - No simulated service: the hosts file was not changed, no local certificate was installed and TLS validation was not disabled.
- Installation not completed: the progress capture is real, but “Install now” was not pressed. No end-to-end agent installation is certified.
- Codex preinstalled: the capture machine already had Codex 0.164.0. The guide documents the “Already installed / Reconfigure / Repair” flow, not a from-scratch installation.
- Hermes: with no WSL2 available, it remains documentation and pending a live test.
- WorkBuddy / CodeBuddy: installation is guided and was not completed in the capture; it remains a guided flow, not a certified automatic installation.
- Qoder: unavailable by design. It is not installed, configured or redirected.
- Conversation: no conversational agent tests were run; this tutorial does not certify them.
These limitations do not affect what is shown: the real 1.0.4 interface, the real states of the capture machine and the flows the app offers.