Product Features Security Docs
Download ClaurixTerm

Documentation

Get ClaurixTerm running, wire up Claude Code, OpenAI Codex and Google Gemini, and ship work with agentic mode — in a few minutes.

1. Quick install

ClaurixTerm ships as a signed NSIS installer for Windows. Linux .AppImage / .deb and macOS .dmg builds are on the roadmap.

Download for Windows View all releases
  1. Download ClaurixTerm-Setup.exe from the button above (always the latest release).
  2. Run the installer. SmartScreen may warn on first install — choose "More info" → "Run anyway" (signed builds are coming).
  3. Launch ClaurixTerm from the Start menu. You'll land on the host list with the top agent bar empty until you add a key.
Verify the version from Help → About or by visiting claurix.com/latest.json in a browser.

2. Choose your AI agent

ClaurixTerm bundles three agents. Each tab keeps its own context and uses an API key you provide. Paste keys under Settings → AI Agents; they're stored encrypted on your machine and never leave it except to call the provider you've selected.

Claude Code Anthropic

Best for code review, refactors, long-context reasoning. Strong at following careful instructions.

Get an API key →
Codex OpenAI

Fast scripting, one-shot fixes, terse command generation. Great default for "just do it" prompts.

Get an API key →
Gemini Google

Long-context wins — paste big logs, configs or full files. Generous free tier for getting started.

Get an API key →

Switch agents from the dropdown in the top bar. The active agent's logo + name appears in the AI panel header, so it's never ambiguous which model is answering.

3. Connect via SSH

Add hosts from the left sidebar. Two auth methods supported: password (with optional save to OS keychain) and key-based (recommended).

Password auth

  1. Click + New Host, fill in host / port / username.
  2. Tick "Save password" if you want the keychain to store it — otherwise you'll be prompted at every connect.

Key-based auth (recommended)

  1. Open Host Details and switch the auth method to Private key.
  2. Paste your private key directly, or point to a file on disk (~/.ssh/id_ed25519 on Linux/macOS, %USERPROFILE%\.ssh\id_ed25519 on Windows).
  3. If the key is encrypted, the passphrase prompt appears at first connect; you can opt to cache it in the OS keychain.
Key fingerprints are verified on first connect and stored locally. Mismatches block the connection and require manual confirmation — same behaviour as OpenSSH's known_hosts.

4. Agentic mode

Agentic mode lets the active AI run multi-step work on its own — read files, run probes, propose commands, execute them, evaluate the output, then plan the next step.

When to use it

  • Investigations ("find what's eating disk on /var")
  • Mechanical refactors across files
  • Repeatable ops with a known shape (cert renewal, package upgrades)

When not to

  • Anything destructive on production without a review step
  • One-shot questions ("which port is nginx on") — that's chat, not agentic

Switching agents mid-run

Each agent keeps its own session. If Claude Code is being too cautious, flip to Codex from the top bar — your shell, working directory and connected host stay live. The session history travels with the tab.

5. Encrypted history & credentials

Everything sensitive is encrypted at rest. Nothing leaves your device except SSH traffic to your hosts and AI requests you initiate.

Where things live

  • Windows: %APPDATA%\com.claurix.ClaurixTerm\
  • macOS: ~/Library/Application Support/com.claurix.ClaurixTerm/
  • Linux: ~/.config/com.claurix.ClaurixTerm/

What's stored there

  • SSH host list (passwords/keys encrypted by the OS keychain where available)
  • AI provider API keys (same encryption)
  • Command history (encrypted blob)
  • UI preferences, snippets, groups, the last active agent

Reset

To wipe everything, quit ClaurixTerm and delete the app-data directory above. Next launch starts fresh.

6. Auto-updates

ClaurixTerm checks for new versions automatically by polling our update manifest.

If the app reports "no update available" but a newer version is listed on GitHub, the server hasn't synced yet — give it up to ~15 min.

7. Troubleshooting

"Authentication failed" connecting to a host

  • Verify the host accepts your auth method (some lock down to keys only).
  • For keys: confirm the key is in ~/.ssh/authorized_keys on the host and that file permissions are 600.
  • For encrypted keys: the passphrase prompt may have been dismissed — reconnect and watch for it.

"Agent key invalid" or "401 Unauthorized"

  • The pasted key may have a leading/trailing space — re-paste from the provider's dashboard.
  • Keys can be revoked or rate-limited at the provider; verify in your provider console.

Update keeps offering the same version

  • The current installed version may be ahead of the published manifest. Compare Help → About against /latest.json.
  • If you ran a local dev build, version numbers may collide — reinstall from /dl/ClaurixTerm-Setup.exe.

SmartScreen blocks the installer

Click "More info" → "Run anyway". Code-signing for the Windows build is on the roadmap and will remove this prompt.

Bug or surprise? Open an issue at github.com/srggaming/ClaurixTerm/issues. Security issues — please use the disclosure channel instead.