Research before you act.
Read subnet and metagraph information, inspect wallets and stake, and turn chain data into a useful next question.
MINERVA · YOUR PERSONAL BITTENSOR AGENT
Your personal agent.
Built for Bittensor.
Explore subnets, understand metagraphs and stake, and get help with your Bittensor workflow. Minerva works on your machine, with your keys, and asks for your approval before btcli signs a transaction.
Minerva product release v0.25.3. Get Minerva →
MORE THAN A CHAT WINDOW
A personal agent for your Bittensor workflow.
For miners, validators, subnet owners, and people finding their way around Bittensor. Start with a question. Keep useful workflows as skills. Return with the context you have built.
Explore the Bittensor tools →Your machine. Your keys.
Read-only chain tools do not sign transactions. When your workflow reaches btcli signing, Minerva asks for your approval.
Make useful work repeatable.
Use skills, tools, and scheduled jobs to support your own workflow. Review what runs and which credentials it can use.
YOUR AGENT, WHERE YOU NEED IT
Bittensor work. Your way.
Reach your personal agent from your terminal, editor, desktop, or local dashboard. Your profiles, skills, and stored conversations stay with the same engine.
Terminal
Ask about subnets, metagraphs, wallets, and stake. Work interactively or automate a repeatable research task.
minervaInstall the engine →Editor
Keep your conversation beside your code. Select the same installed engine in the extension settings.
Minerva: Refresh Engine and ConnectionVS Code installation →Desktop
A Tauri companion with Quick Chat, messaging connections, scheduled jobs, MCP servers, and engine discovery.
Select engine → ConnectDesktop downloads and setup →Dashboard
Your local control room for conversations, profiles, messaging connections, skills, MCP servers, schedules, and updates.
minerva dashboardDashboard guide →ONE RELEASE, EVERY WORKSPACE
Update Minerva.
Keep everything together.
One command updates the engine, TUI, bundled dashboard, and detected desktop and VS Code installations. Finish active work first. Required permissions, pending packages, and older windows remain visible until confirmed.
Read the update guide →01 / Check availability
minerva release status --force02 / Update all detected interfaces
minerva update03 / Or use the local update screen
minerva dashboardYOUR ACCOUNT, YOUR ACCESS
A home for your connected devices.
Create an account, connect your terminal or editor with device sign-in, and disconnect devices whenever you need. Administrators can manage users from the account portal.
Your Minerva account is separate from your model provider credentials. Account sign-in does not upload local conversations or synchronize profiles between machines.
Keep each package current
Every interface shares one product release version. Update Minerva coordinates detected packages and records components that still need installation or a restart. Version checks distinguish installed packages from older running windows. Downloads show progress and transfer speed, and interrupted transfers retry with resume support.
Engine & dashboard
Use minerva update or the local dashboard’s update screen. The dashboard ships with the engine.
If Windows 0.24.1 stops before downloading the update, follow the Windows recovery steps.
Desktop app
Install a published package for your operating system. Update Minerva stages the checksum-verified installer from the signed release and records any required OS permission or restart.
Published desktop packages →VS Code extension
Update Minerva installs the checksum-verified VSIX through the editor CLI, even while VS Code is closed. Reload an open window to activate it. A missing CLI leaves an explicit pending result.
Install the extension →Release availability
Download Windows and Linux desktop installers and the VS Code extension from this website. The Windows installer is an unsigned preview; macOS packaging is pending. Each download includes its checksum.
Check available packages →Install, update, or remove.
Does minerva update only update the CLI?
No. It updates the shared engine, TUI and dashboard, then coordinates detected desktop and VS Code packages. Finish any installer or permission prompt. Reload older windows to activate the installed release.
Can I run the install command again?
Yes. The default Linux/macOS installer detects an existing engine and runs its coordinated updater. Your settings and conversations remain in place. For explicit installation options or a broken runtime, follow the installation guide.
How do I uninstall Minerva?
Preview the changes with minerva uninstall --dry-run. Run minerva uninstall to choose whether to keep your local settings and conversations. The --full option removes local data. Remove the VS Code extension through Extensions, and packaged desktop applications through Windows Installed apps or your Linux package manager (sudo apt remove minerva-desktop for the Debian package).
Do the dashboard and this website update automatically?
The dashboard files update with your engine; reload an open tab when prompted. This website updates when a new server deployment is published. Updating a local installation does not deploy the public website.