Save aliases locally
Add aliases from the CLI and keep the canonical source in Aliaz instead of scattering edits across shell profiles.
Aliaz stores aliases in SQLite, writes shell integration for zsh, bash, and fish, and syncs encrypted records between machines only when you opt in.
The release installer downloads the matching macOS or Linux
binary, verifies checksums when possible, installs Aliaz to
~/.local/bin, and can configure shell integration
during install.
$ curl -fsSL https://raw.githubusercontent.com/oshabana/aliaz/main/install.sh | sh
$ aliaz add gs "git status"
$ aliaz list
$ aliaz register --username ada
$ aliaz sync
ALIAZ_INSTALL_SHELLS,
ALIAZ_INSTALL_SYNC, ALIAZ_VERSION,
or ALIAZ_INSTALL_DIR to customize installs.
cargo install --path .
Aliaz treats aliases as small records: readable locally, printable as shell-safe alias definitions, and encrypted before optional sync.
Add aliases from the CLI and keep the canonical source in Aliaz instead of scattering edits across shell profiles.
Register or log in to a sync account, then push and pull
encrypted alias records with aliaz sync.
Generate stdout output with aliaz generate, or
write managed zsh, bash, and fish files with
aliaz init. zsh and bash startup files are
configured once.
The first workflow is local alias management. Sync, recovery, and self-hosting are available when you need multiple machines.
shells
Generate shell-specific alias files while keeping one portable alias source.
sync
Register once, save the recovery phrase, log in on another machine, and run sync to pull encrypted alias records.
recovery
Aliaz stores the phrase in the OS credential store and prints it once during registration. Without it, encrypted aliases cannot be recovered.
self-host
register and login accept
--sync-url, and the repository includes the
Worker and D1 migrations for the sync service.
weight
The core workflow is local: add, list, edit, delete, migrate
from .zshrc, import/export JSON, and check
setup with status or doctor.
The examples mirror the current CLI output: local commands work
without an account, while sync starts after
register or login.
$ aliaz register --username ada
Registered ada
Recovery phrase: ...
$ aliaz add gl "git log --oneline --decorate"
Added gl
$ aliaz list
gs git status
gl git log --oneline --decorate
dc docker compose
$ aliaz sync
Synced: pulled 0, pushed 3, latest version 3
$ aliaz init zsh
Wrote ~/.config/aliaz/aliases.sh
Configured ~/.zshrc
The docs preview follows the current command set: install, quickstart, shell integration, migration, import/export, sync, logout, status, and doctor.
Aliaz stores aliases locally in SQLite. You can print
shell-safe definitions with generate, or write
managed shell integration files with init.
Add an alias, inspect the local list, then initialize the shell integration for the current environment.
$ aliaz add gs "git status"
$ aliaz list
$ aliaz init fish
$ aliaz doctor
Aliaz keeps every operation available from the CLI, including shell generation, migration, JSON import/export, status, and doctor checks.
Aliases are stored in SQLite under the operating system's standard data directory.
generate prints definitions; init
writes managed files for zsh, bash, and fish.
JSON export can print to stdout or write a file. Import upserts aliases by name.
status reports local and sync state.
doctor checks the database, integration files,
sync config, and secret storage.
Aliaz is an MIT-licensed open-source project. The GitHub repository includes the Rust CLI, the installer, a Cloudflare Worker sync API, D1 migrations, and tests.
Support helps cover release work, documentation, sync hosting, and maintenance.
The important behavior is explicit: what sync encrypts, which shells work, and what happens when recovery material is lost.
Yes. Aliaz keeps one alias source and exports the file format your shell expects.
Alias names and commands are encrypted before upload. Sync is optional and requires registration or login.
Yes. The repository includes Cloudflare Worker code and D1 migrations for the sync service.
Aliaz cannot recover encrypted aliases without it. Keep the phrase somewhere durable before depending on sync recovery.
No. Aliaz can complement dotfiles, but the primary workflow is a local SQLite-backed alias source plus generated shell files.