DevelopersCommands
capabilities, actions, templates, validate and resolve. Requests come from --json, --file or stdin, bounded to 32 KiB.
Ursly CLI · Rust · Independent of the SDKs
One binary.
Pure Rust.
A single native executable, its own product, never tied to an SDK. You don't type install commands: copy a prompt and your agent downloads, verifies and runs it.
ursly capabilitiesGET /api/v1/capabilities// The response payload appears here.Download, verify and place the native binary.
Install the Ursly CLI on this machine. 1. Read https://ursly.io/downloads/manifest.json and pick the file whose kind is "cli" for this operating system and CPU. 2. Download it from https://ursly.io followed by its path. Compute its SHA-256; if it differs from the manifest, delete the file and stop. 3. Extract ursly (ursly.exe on Windows) into a user-writable directory on my PATH and make it executable. 4. Run ursly --version, then ursly --url https://ursly.io capabilities --pretty, and show me the 200 response. Do not use administrator rights without asking me. Keep TLS verification on.
Paste it into your coding agent. That is the whole install.
Compare, verify and replace in place.
Update the Ursly CLI on this machine. 1. Run ursly --version and compare it with release.version in https://ursly.io/downloads/manifest.json. 2. If they match, tell me it is current and change nothing. 3. Otherwise download the matching "cli" archive, verify its SHA-256 against the manifest and replace the existing binary in the same location. 4. Run ursly --version and ursly --url https://ursly.io capabilities to confirm the 200 response.
Paste it into your coding agent. That is the whole install.
Validate and resolve a voice rule.
Use the Ursly CLI to try a voice rule. 1. Run ursly --url https://ursly.io templates --pretty and save the "voice-home" request as rule.json. 2. Change the phrase or the action only if I ask; keep navigation targets application-relative. 3. Run ursly --url https://ursly.io validate --file rule.json, then ursly --url https://ursly.io resolve --file rule.json --pretty. 4. Show me the returned intents and explain them. The CLI only returns intents; never execute them from the shell.
Paste it into your coding agent. That is the whole install.
Native builds
Four platforms. One checksum each.
The install prompt picks the right archive for the machine it runs on and refuses anything whose SHA-256 differs from the published manifest.
- macOSApple siliconChecking release…
- macOSIntelChecking release…
- Linuxx64Checking release…
- Windowsx64Checking release…
Under the hoodFor your agent, not for you.
Commands, flags and exit codes still exist. Your agent reads them here and in the manual; you never have to.
Configuration
--url or URSLY_URL (always explicit), --timeout or URSLY_TIMEOUT (10 s default), --pretty. TLS stays on; redirects and retries are off.
Exit codes
0 success, including an unmatched rule · 2 usage or input · 3 API rejection · 4 network, timeout or invalid response.
Output
API JSON goes to stdout; structured errors go to stderr. The CLI never executes an intent, opens a URL or runs a shell command.