Preview changes with --dry-run
The syllago commands that change your library or your provider files support --dry-run: run it and syllago prints what would happen, then exits without touching anything. It’s the fastest way to build trust in a CLI that edits your AI tool configs.
Where it’s supported
Section titled “Where it’s supported”| Command | What the dry run shows |
|---|---|
syllago add | What would be imported into your library |
syllago install | Files/symlinks that would be created in the provider (also accepts -n) |
syllago remove | What would be deleted from your library |
syllago uninstall | What would be removed from the provider’s location |
syllago sync-install | The combined registry-sync-then-install plan |
syllago loadout apply goes one step further: preview is its default. Running it with no flags never modifies anything; you opt into changes with --try or --keep.
Dry run vs. real run
Section titled “Dry run vs. real run”# Preview: prints the plan, writes nothingsyllago install typescript --to cursor --dry-run
# Real: creates the symlink in Cursor's rules directorysyllago install typescript --to cursorThe dry-run output lists the same target paths and conversions as the real run — the only difference is that nothing is written. If the plan looks wrong (wrong provider directory, unexpected format conversion, an item you didn’t mean to touch), you’ve lost nothing.
When to use it
Section titled “When to use it”- Before your first use of any command — cheap way to learn what it actually does
- Before anything destructive — always before
removeanduninstall - Before bulk operations —
--alland--to-allfan out; preview the fan-out first - When a provider’s directory layout matters — confirm where files will land before writing there
Related
Section titled “Related”- Quick Start — the flows these commands belong to
- Keep rules in sync — where dry runs fit the maintenance workflow