kagi bang
Manage custom Kagi bangs from the terminal.
Synopsis
Authentication
Required:KAGI_SESSION_TOKEN
Custom bang management uses Kagi’s authenticated settings pages.
Subcommands
kagi bang custom list
List custom bangs.
kagi bang custom get <ID_OR_NAME>
Fetch one custom bang by id, exact name, or trigger. Triggers may be supplied with or without the leading !.
kagi bang custom create <NAME> --trigger <TRIGGER>
Create a custom bang.
Supported options:
--template <URL>--snap-domain <DOMAIN>--regex-pattern <REGEX>--shortcut-menu/--no-shortcut-menu--open-snap-domain/--no-open-snap-domain--open-base-path/--no-open-base-path--encode-placeholder/--no-encode-placeholder--plus-for-space/--no-plus-for-space
kagi bang custom update <ID_OR_NAME>
Update a custom bang.
kagi bang custom delete <ID_OR_NAME>
Delete a custom bang.
Output Contract
list returns an array of summaries:
get, create, and update return full bang details:
delete returns:
Examples
Create a bang and verify it:Notes
- Targets may be the bang id, exact name, or trigger.
- The CLI normalizes bang targets so
rustdocsand!rustdocsresolve to the same bang. snap_domainand thefmt_*fields map directly to Kagi’s current custom-bang settings form.
See Also
- search - combine bangs with search workflows
- redirect - manage redirect rules alongside custom bangs
- auth-matrix