v0.4.0 · MAY 2026

Iris Code

The god of sub-messaging — packaged as a calm, fast Windows desktop app. Free, MIT licensed, no account required.

Download for Windows (x64) Download for Windows (ARM64) Install instructions

≈ 90 MB · Windows 10 / 11 · NSIS installer · v0.4.0 on x64 and ARM64

Not sure? Press Win+Pause — if "System type" says ARM-based PC, choose ARM64; otherwise choose x64.

Other platforms

Mac & Linux coming soon

Native builds for macOS and Linux are landing in v0.4. Sign up on GitHub for release notifications.

Windows 10 / 11 · x64 Available · NSIS installer
macOS v0.5 · signed DMG
Linux v0.5 · AppImage / deb

Before you install

Iris Code drives the official Claude Code CLI under the hood. You'll need it installed and authenticated before first launch. From a terminal, run: 

npm install -g @anthropic-ai/claude-code
claude auth login

Full instructions are in the Claude Code documentation. Iris Code detects the CLI automatically on first launch.

Installation

Two ways to install. Pick whichever feels easier.

Hand the install to Claude Code and let it do the work, or follow the five‑step guide yourself.

Option A · Recommended

Let Claude Code install it for you

Copy the prompt below, paste it into a fresh Claude Code session, and Claude will detect your CPU, fetch the right installer, verify the SHA‑256, run a free VirusTotal cloud scan, run the setup, and walk you through the first‑run wizard. It uses your machine — no remote actions. 

Please install Iris Code (a desktop GUI for the Claude Code CLI) on this Windows machine. Work step-by-step on my system and ask before any destructive action.

1. Detect my CPU architecture in PowerShell:
     (Get-CimInstance Win32_Processor).Architecture
   9 = x64, 12 = ARM64. Tell me which you found.

2. Verify prerequisites:
   - node --version  (need Node.js >= 18; if missing, point me to https://nodejs.org/)
   - claude --version  (if missing, run: npm install -g @anthropic-ai/claude-code, then ask me to run `claude auth login` interactively in my own terminal)

3. Fetch the release manifest to learn the current version and download URL:
     Invoke-RestMethod https://iris-code.pages.dev/latest.json
   Pick windows.x64 or windows.arm64 based on step 1.

4. Download the installer to my Downloads folder:
     Invoke-WebRequest -Uri  -OutFile "$env:USERPROFILE\Downloads\Iris-Code-Setup.exe"

5. Verify the SHA-256:
     (Get-FileHash "$env:USERPROFILE\Downloads\Iris-Code-Setup.exe" -Algorithm SHA256).Hash
   It must match the sha256 in the manifest. If it doesn't match, STOP and tell me.

6. Cloud-scan the installer before running it (recommended, since v0.4 isn't code-signed yet). Upload the file to VirusTotal so 70+ antivirus engines scan it in the cloud:
     Start-Process "https://www.virustotal.com/gui/home/upload"
   Tell me to drag the .exe from my Downloads folder into the upload box. Wait for me to confirm the report is clean (a few harmless heuristic flags on unsigned NSIS installers are normal — but any real malware signature means STOP). Alternatively, query the report by hash without uploading:
     Start-Process "https://www.virustotal.com/gui/file/$((Get-FileHash "$env:USERPROFILE\Downloads\Iris-Code-Setup.exe" -Algorithm SHA256).Hash.ToLower())"

7. Launch the installer:
     Start-Process "$env:USERPROFILE\Downloads\Iris-Code-Setup.exe"
   Warn me first that Windows SmartScreen will show a blue prompt — I should click "More info" then "Run anyway", accept the UAC prompt, and keep the default install location.

8. After the installer closes, confirm install by checking:
     Test-Path "$env:LOCALAPPDATA\Programs\iris-code\Iris Code.exe"
   If true, offer to launch it for me.

9. Walk me through the first-run wizard: it auto-detects the `claude` CLI, lets me store an API key in the encrypted vault, and shows a keyboard-shortcut tour.

Do not skip the hash verification. Do not skip the cloud scan. Do not run the installer silently — I want to see the UI.

Don't have Claude Code yet? Install it first with npm install -g @anthropic-ai/claude-code, then claude in your project folder and paste the prompt.

Option B

Install it manually — five quiet steps

Prefer to do it yourself? Follow the steps below.

  1. Pick the right installer for your CPU

    Most Windows laptops and desktops are x64 (Intel / AMD) — click the gold button to download Iris Code Setup 0.4.0.exe. If you're on a Surface Pro X, a Copilot+ PC, or another Snapdragon / ARM machine, use the ARM64 button instead — that downloads Iris Code Setup 0.4.0 (ARM64).exe.

  2. Run the installer

    Double‑click the .exe. Windows will ask for permission to make changes — accept.

  3. Pass the SmartScreen warning

    Because v0.4.0 isn't code‑signed yet, Microsoft Defender SmartScreen may show a blue prompt. Click More info, then Run anyway. Signed builds are scheduled for v0.5. If you'd like extra reassurance before clicking through, jump to Cloud scan below — you can have 70+ antivirus engines verify the installer in under a minute.

  4. Choose an install location

    The default is fine. Iris Code installs into your user profile, so admin rights aren't required.

  5. Launch & complete the first‑run wizard

    On first launch, the wizard checks for the claude CLI, lets you store an API key in the encrypted vault, and offers a tour of the keyboard shortcuts. Two minutes and you're in.

Extra peace of mind

Cloud-scan the installer in under a minute

Because v0.4.0 isn't code‑signed yet, Windows SmartScreen will warn you. If you'd like independent confirmation that the file is clean, run it past VirusTotal — a free service that scans your upload with 70+ antivirus engines in the cloud.

Option 1 — Scan by hash (no upload)

If someone else has already uploaded the same installer, VirusTotal will show the existing report instantly. Open one of these direct links:

VirusTotal report — x64 installer
VirusTotal report — ARM64 installer

If the report says "File not found", nobody has scanned this build yet — use Option 2 to upload it (which also helps everyone who comes after you).

Option 2 — Upload & scan

Drop the downloaded .exe straight into VirusTotal's upload box and wait ~30 seconds for the verdict.

Open VirusTotal upload

A small number of heuristic flags on unsigned NSIS installers is normal. What you're looking for is the absence of named malware signatures (e.g. anything from Microsoft, Kaspersky, BitDefender, ESET). If you see real detections, don't run the file — open a GitHub issue and we'll investigate.

Looking for the full scan report at a glance? Open the Safety page — it's a built-in dashboard that shows the latest VirusTotal verdict, file sizes, and live links.

Verify your download

Checksums

Confirm the installer hasn't been tampered with. Compare against these published hashes.

Artifact Algorithm Hash
Iris Code Setup 0.4.0.exe x64 SHA‑256 7a309187c2c17d0dab58c7a6c9c80563c9a20b17e07de764e679c013c9c184a7
Iris Code Setup 0.4.0 (ARM64).exe arm64 SHA‑256 c271fd687c2f1a5f807b83963a7e506445c3fe54883580fef4a2ecff11c77d4d

To verify locally on Windows: Get-FileHash .\"Iris Code Setup 0.4.0.exe" -Algorithm SHA256. Hashes are also published in SHA256SUMS.txt alongside the installer on the GitHub release page.

Release notes

What's new in v0.4.0 — Telegram Remote Agent

One headline feature: DM your personal Telegram bot to drive Claude Code on your desktop, from anywhere.

added

Telegram Remote Agent

Bring-your-own-bot — one user, one bot, no shared infrastructure. Token encrypted at rest via Electron safeStorage with an AES-GCM fallback.

added

6-digit pairing flow

No copy-pasting chat IDs. Type one code in Telegram and the bridge locks to your account.

added

Per-chat allowlist

Inbound messages from any other chat are dropped silently. Enforced on every single update.

added

Auto-reconnect

Exponential backoff on network or Bot API failures. Survives flaky hotel Wi-Fi and Telegram outages.

added

MarkdownV2 replies

Agent output is properly escaped and chunked at Telegram's 4096-character ceiling — no broken formatting, no truncated messages.

added

Slash commands

/new resets context, /stop cancels the current run. The bot speaks the same language as the desktop UI.

Under the hood

  • New module — lib/telegram/ (index.js, api.js, markdown.js). Pure Node https; zero new runtime dependencies.
  • Token at rest — its own telegram-token.json (chmod 600 on POSIX) so encryption-backend changes can't corrupt unrelated settings.
  • New settings key — telegram (enabled, botUsername, allowedChatId, chatAgentId). The bot token itself never touches settings.json.
  • New IPC surface — telegram:status, telegram:set-token, telegram:start-pairing, telegram:test-message, plus a ui:telegram-status push event for live panel updates.
  • New onboarding step — "Set up with Telegram for easy agent access (optional)" — deep-links to the panel.
  • 15 new tests — tests/telegram.test.js covers MarkdownV2 escaping, chunking, pairing, allowlist, agent routing.
  • New doc — docs/telegram.md.

Compatibility

  • v0.3.0 settings auto-upgrade. The telegram block defaults to disabled, no token, no paired chat — existing users see no behavior change until they enable the bridge.

Known limitations

  • Installer is not yet code‑signed. SmartScreen will warn — signing is scheduled for v0.5.
  • Both x64 and ARM64 are available for v0.4.0 — pick the one that matches your CPU.
  • macOS and Linux native builds are scheduled for v0.5.

Ready when you are.

v0.4.0 is the most reachable version yet — your desktop, in your pocket. Try it for an hour.

Download for Windows (x64) Download for Windows (ARM64) Read the docs