CLI Reference

The slasha binary is both the server and the client. Every command below communicates with a remote Slasha instance over HTTP. Before running any command, authenticate with slasha login and tell the CLI where your server is.

Connecting to your server

The CLI needs to know the base URL of your Slasha instance. Set it once withset-url and it is persisted to the global config file (typically ~/.config/slasha/config.toml on Linux or ~/Library/Application Support/slasha/config.toml on macOS):

slasha set-url https://slasha.example.com

You can also pass --url on any command to override it for that invocation:

slasha --url https://slasha.example.com status

Global flags & Environment Variables

These flags and environment variables are accepted by every command:

  • --url <URL> — override the server base URL for this invocation
  • --output <human|json> — switch output format. Default is human (coloured terminal output). Use json for scripting or piping to jq
  • --diagnostic — print diagnostic information useful for bug reports, then exit
  • SLASHA_TOKEN — authenticate via a token instead of the system keychain (ideal for CI/CD)
  • NO_COLOR — disable colored terminal output (e.g. NO_COLOR=1 slasha list)

App context and slasha.toml

Many commands require an app identifier. You can always pass --app <slug>explicitly. Alternatively, run slasha link inside your project directory to write aslasha.toml file that pins the current directory to an app slug.

The slasha.toml file is simple and looks like this:

app = "my-slug"

Any command run in that directory (or a subdirectory) will then pick up the app automatically.

# explicit
slasha info --app my-app

# after linking, the --app flag can be omitted
slasha link
slasha info

Authentication

# log in (prompts for email and password)
slasha login

# show the currently authenticated user
slasha me

# remove the stored token
slasha logout

On first login, if no admin account exists yet, the CLI will prompt you to create one instead of logging in. The token is stored in the system keychain unless SLASHA_TOKEN is used.

Checking server health & Version

# Check basic health and version
slasha status

# Print the CLI version
slasha version

# Print detailed version and build information
slasha version --verbose
Server Configurationapps