sui-install
Skill20 starsChanged 15 days agoApache-2.0View on GitHub
Installing, updating, and managing Sui CLI versions with suiup. Use this skill when the user needs to install Sui, update to a newer version, switch between network-specific versions, resolve "command not found" or version mismatch errors, install additional toolchain components (Walrus, MVR, Move Analyzer), or troubleshoot suiup commands. Also use when the user sees "client/server api version mismatch" warnings or asks about suiup install, update, switch, or show.
- Pipes a download into a shell
- Installs packages
In this repository30 other files it gives its agents.
- accessing-dataSkill
- composable-move-functionsSkill
- deepbook-marginSkill
- deepbook-moveSkill
- deepbook-overviewSkill
- deepbook-predictSkill
- deepbook-sdkSkill
- frontend-appsSkill
- generate-sui-agent-configSkill
- kioskSkill
- modern-move-syntaxSkill
- move-securitySkill
- move-unit-testingSkill
- naming-conventionsSkill
- sui-object-modelSkill
- onchain-randomnessSkill
- ptbsSkill
- sui-bridgeSkill
- sui-buildSkill
- sui-clientSkill
- sui-for-ethereumSkill
- sui-move-projectSkill
- sui-moveSkill
- sui-networks-gasSkill
- sui-overviewSkill
- sui-publishSkill
- sui-sdksSkill
- sui-ts-sdk-backendSkill
- walrus-sitesSkill
- zkloginSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 38
After installing suiup, install the Sui CLI targeting a specific network.
- Distinctive: line 45
Update to the latest version:
- Very specific: line 89
If the command returns "sui not found", run suiup switch sui@testnet to set the active default.
- Distinctive: line 110
Check your version against the network:
- Distinctive: line 117
If the version is out of date, update and switch:
- Distinctive: line 138
After installing, switch each tool to make it the active default:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setup & Installation
MCP tool: When available in your environment, also query the Sui documentation MCP server (
https://sui.mcp.kapa.ai) for up-to-date answers. Use it for verification and for details not covered by these reference files.
Source constraint: All information sourced exclusively from docs.sui.io.
System requirements
Sui supports:
- Linux: Ubuntu 22.04 (Jammy Jellyfish) or newer
- macOS: Monterey or newer
- Windows: Windows 10 or 11
Installing Sui
suiup (recommended)
suiup is the official installer and version manager for the Sui toolchain. It supports installing and switching between different versions of the Sui CLI and other Sui Stack components (Walrus, MVR).
curl -sSfL https://raw.githubusercontent.com/MystenLabs/suiup/main/install.sh | shWindows note: The curl | sh command requires a Unix shell. On Windows, use WSL (Windows Subsystem for Linux) to run the command above, or install through Chocolatey instead (see alternative methods below).
After installing suiup, install the Sui CLI targeting a specific network. The CLI version must match the target network — each network runs a specific protocol version, and a mismatched CLI can cause build failures, transaction errors, or unexpected behavior:
suiup install sui@testnet # install the Testnet-compatible version
suiup install sui@mainnet # install the Mainnet-compatible versionUpdate to the latest version:
suiup update sui@testnetImportant: suiup update downloads the new version but does not automatically make it the active default. After updating, you must switch to the new version:
suiup switch sui@testnet # set the latest installed testnet version as defaultTo verify which versions are installed and which is active:
suiup show # list all installed binaries and their default statussuiup command reference
| Command | Syntax | What it does |
install | suiup install sui@testnet | Download and install a binary for a network |
update | suiup update sui@testnet | Download the latest version (does NOT switch to it) |
switch | suiup switch sui@testnet | Set the latest installed version for a network as the active default |
show | suiup show | List all installed binaries with versions and defaults |
status | suiup status | Show which installed binaries have updates available and the command to update them |
self update | suiup self update | Update suiup itself |
The switch command takes a binary@network argument (for example, sui@testnet, walrus@testnet, move-analyzer@testnet). It does not accept separate positional arguments like suiup switch sui testnet v1.70.2.
Alternative methods
- Homebrew (macOS/Linux):
brew install sui - Chocolatey (Windows):
choco install sui
These alternatives do not support installing additional Sui Stack components like Walrus or MVR and might take several minutes if prerequisites are not already installed.
Verify installation
sui --versionIf the command returns "sui not found", run suiup switch sui@testnet to set the active default. Do not suggest manual PATH manipulation (export PATH=...) or reinstalling — suiup switch is the correct fix.
Version management
Keeping Sui up to date
The CLI version should match the target network — each network runs a specific protocol version, and a mismatched CLI can cause build failures or transaction errors. Use the @network suffix to update to the correct version:
suiup update sui@testnet # update to latest Testnet version
suiup update sui@mainnet # update to latest Mainnet versionVersion mismatches
The CLI version must match the network you are targeting. Common symptoms of a mismatch:
- Build errors mentioning "old dependencies"
- Transaction failures on publish
- Unexpected behavior after network upgrades
Check your version against the network:
sui --version # your installed version
sui client active-env # which network you are targetingIf the version is out of date, update and switch:
suiup update sui@testnet # download the latest version
suiup switch sui@testnet # make it the active default
suiup show # verify which version is now activeThe client/server api version mismatch warning in CLI output means your local CLI is older than the network. Do not ignore this warning — version mismatches can cause build failures and unexpected behavior. Update and switch to fix it.
Optional additional tools
Install these only when the user explicitly asks for the tool. They are not part of default setup.
suiup install move-analyzer # Move Language Server
suiup install mvr # Move Registry CLI (onchain package manager)
suiup install walrus # Walrus CLI for decentralized storage
suiup install site-builder # Walrus site builderAfter installing, switch each tool to make it the active default:
suiup switch move-analyzer@testnet
suiup switch walrus@testnetDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

