Install & updates

Aktualisiert 16. August 2026 · geschrieben neben dem Code, den sie beschreibt
Diese Anleitung ist noch nicht übersetzt — sie wird auf Englisch angezeigt.

Before you install

Helmry drives the Claude Code CLI. It does not call the Anthropic API itself and has no API key of its own — every agent is a local claude process running as whichever Claude account is signed in on this machine. So install Claude Code first and sign in, then install Helmry.

You can check the sign-in later from inside the app: Preferences → Claude account shows which Claude login the fleet runs as, and can sign out or sign in again.

Windows

Run Helmry-Setup-<version>.exe.

  • It is a per-user install under %LOCALAPPDATA%\Programs, so Windows never asks for admin rights.
  • The wizard lets you change the install directory and creates Desktop and Start Menu shortcuts.
  • SmartScreen will warn (“Windows protected your PC”) because the build is not code-signed. Choose More info → Run anyway if you trust the source you downloaded it from.
  • Smart App Control blocks it outright. If Windows 11’s Smart App Control (Интеллектуальное управление приложениями) is on, it refuses unsigned installers and — unlike SmartScreen — offers no “run anyway”. Auto-update hits the same wall: the download succeeds and Windows then declines to launch the installer. There is no per-file exemption; the choices are to turn Smart App Control off (Windows Security → App & browser control → Smart App Control — note it cannot be turned back on without reinstalling Windows) or to wait for signed builds.

A repository inside a WSL distribution is opened as an execution environment — chosen per repository, not once for the app. See Windows & WSL.

macOS

Open the .dmg and drag Helmry into Applications.

The build is not signed or notarized, so Gatekeeper refuses the first launch with “Helmry cannot be opened because the developer cannot be verified”. Two ways past it:

  • Right-click the app → Open → Open in the dialog, or
  • System Settings → Privacy & Security, find the blocked-app notice, click Open Anyway.

macOS asks for extra permissions the first time a feature needs them: Screen Recording for the built-in “screenshot an area” button (grant it to Helmry, then restart the app), and Notifications for the fleet alerts.

Linux

chmod +x Helmry-<version>.AppImage
./Helmry-<version>.AppImage

No installation step and no root. The AppImage carries its own runtime.

Where Helmry keeps things

Path What
~/.helmry/helmry.db SQLite: sessions, events, accounts, chat metadata, saved prompts, per-account preferences
~/.helmry/config.json Server configuration (see Settings)
~/.helmry/token Local ingestion token, mode 0600
~/.helmry/logs/main.log Diagnostics — metadata and decisions only, 1 MB with one previous generation
~/.helmry/archive/ Transcripts you explicitly archived
~/.claude/projects/… Claude’s own transcripts — the source of truth for every conversation. Not written by Helmry.
Shell settings %APPDATA%\Helmry (Windows), ~/Library/Application Support/Helmry (macOS), ~/.config/Helmry (Linux) — window/server choice and the update token

Set HELMRY_DATA_DIR to move the first group somewhere else.

Updates

The app checks once per launch and again whenever you pick Help → Check for updates… (press Alt to reveal the menu bar).

Helmry releases live in a private repository, so downloading one needs a GitHub token — an unconfigured install simply never finds an update. The first time you use Check for updates… without a token, Helmry creates a pre-commented file for you and offers to reveal it:

<shell settings dir>/update-token

Paste a token on its own line, save, and restart Helmry. A fine-grained token is enough:

  • Resource owner: the Helmry repository’s owner
  • Repository access: only the helmry repository
  • Permissions: Contents → Read-only (nothing else)

The file is mode 0600, is read only by the desktop shell, and is deliberately not put into the environment — the app spawns claude, git and your terminal, and all of them would inherit it. HELMRY_UPDATE_TOKEN, GH_TOKEN or GITHUB_TOKEN in the environment work too and take precedence.

How an update lands. A found update downloads in the background; you get a dialog when it starts and another when it is ready, offering Restart now or Later. Either way it installs when you quit the app. Restarting stops the agents driven from that window — sessions running in your own terminals are unaffected.

Development builds report “This is a development build” and check nothing.

Uninstall
Windows Settings → Apps → Helmry → Uninstall
macOS Drag Helmry from Applications to the Trash
Linux Delete the AppImage

Uninstalling does not remove your data. To erase everything Helmry stored:

rm -rf ~/.helmry                              # DB, config, token, logs, archive
rm -rf ~/.config/Helmry                       # Linux shell settings (+ update token)
# macOS:   rm -rf ~/Library/Application\ Support/Helmry
# Windows: rmdir /s "%APPDATA%\Helmry"

Your Claude conversations are not Helmry’s to delete — they stay in ~/.claude/projects.

If you also installed hooks for observed sessions, remove those from ~/.claude/settings.json as described there.