1
Download and Install

Download the Windows installer from the releases page.

NeuralShell.Setup.2.1.36.exe
Windows x64 · 305 MB
Verify before running: Open PowerShell in the repo root and run .\VERIFY_RELEASE.ps1 to confirm the installer hash matches SHA256SUMS.txt.

If Windows SmartScreen warns you — click "More info" → "Run anyway". Verify the installer hash against SHA256SUMS.txt before running.

↓ Download v2.1.36
2
Connect a Model Provider

NeuralShell works with local and cloud providers. Choose one to start.

Fully offline: Install Ollama, then go to Settings → Model Provider → Ollama. Models auto-detect. No API key needed.

For cloud providers (OpenAI, OpenRouter, Groq):

  1. Get your API key from the provider's dashboard
  2. Open Settings → Model Provider
  3. Paste key → click Test Connection
3
Create Your First Thread

Press Ctrl+Shift+P to open the Command Palette, then click + New Thread in the left rail. Start typing — each thread is isolated and independently recoverable.

ActionShortcut
Command PaletteCtrl+Shift+P
New ThreadCtrl+N
SettingsCtrl+,
Close ThreadCtrl+W
4
Run the Hardware-Binding Proof Flow

Before trusting NeuralShell with sensitive work, verify its core claim yourself. This takes about 3 minutes.

Hardware binding verification · ~3 minutes
1
Create a thread, send a few messages, do some work
2
Click Export Session → save backup.enc somewhere outside the app folder
3
Close NeuralShell completely
4
Delete %APPDATA%/NeuralShell entirely — this simulates a reinstall
5
Reopen NeuralShell → Import from Backup → select backup.enc
Expected result: session restores on this machine. If you copy backup.enc to another machine and attempt the same restore, it fails with a hardware mismatch error.
All 7 trust-state scenarios are documented with screenshots in the Proof page.
5
Validate Offline Operation

If you're using Ollama, disconnect from the network and confirm that local workflows still execute with no errors. NeuralShell should not attempt any cloud calls.

Network monitoring: watch your system firewall or use netstat during an offline session to confirm no outbound connections are made.

Troubleshooting

App won't start
Delete %APPDATA%/NeuralShell/state and restart. If that fails, run as Administrator once to initialize permissions.
No AI responses
Verify API key in Settings. For cloud providers, check your internet connection. Switch to Ollama for fully offline operation.
Session restore fails
Expected if you're restoring on different hardware — that's the hardware-binding working correctly. Restore must happen on the original machine.
🔬
Verification Proof
All 7 hardware-binding scenarios with screenshots and fingerprint data.
📖
Documentation
Full operator reference, architecture, and audit documentation.
🧪
Beta Program
Join the beta tester cohort and report findings.
💳
Pricing
Free for individuals. Pro and Enterprise for teams and compliance.