Currently, snaps and bangs are only supported at the beginning/end of a query. This is inconsistent with other search operators, such as site:, filetype:, after:, which work in any position of the query. This limitation makes it difficult to combine multiple search operators, having to order them in a specific way for it to work.
Real world examples:
sunset !i @px doesn't work, but sunset @px !i does.@w tallest building ! redirects to first wikipedia result, but tallest building @w ! doesn't.coding model after:2026-08-01 @r works, but coding model @r after:2026-08-01 doesn't !fr sports after:2026-01-01 works, but sports !fr after:2026-01-01 doesn't
As such, power users have to learn the unintuitive ordering requirements of bangs and snaps to use them with other search operators. It also makes it impossible to use more than 2 of the special kagi operators at the same time: @(snaps), !(bangs), ? or !q(quick answer) and \ or ! (feeling lucky)
While ! and ? also have the requirement to be at the start/end of the search, they are intuitive due to being the most important component of the search query.
More examples:
- Using snaps in other search engines:
best pc @r !g
- Quick answer from specific sources
quantum theory @nasa ?
- Finding pdf files from specific website:
constitution @gb filetype:pdf
- Finding new results from a website
opencode @r after:2026-08-01 doesn't
etc
Note: these queries work when putting the snap at the beginning, but don't currently.
