Long queries don't work with bangs

Thibaultmol

I don't THINK it's a firefox limitation because i'm also getting it if i type it in the search bar on kagi.com

but if you have a long query (which i do sometimes, def went i want to !ai to ask the assistant something. bangs stop working at some point

Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. !ai

for example doesn't work, it just stays kagi.com and searches instead of going to Assistant.

doing !ai first does work, but yeah.

Thibaultmol

it also cuts off when sending to assistant for example:

miicat_47

Ohhh, I had similar problem with custom !t bang, which opens the Kagi Translate

In my case, I put the !t bang first and then quite long text to translate and it just opened the translate page without any text in the translating field

The cuts off bug happens with the above text as well ^

Thibaultmol

Btw, I have noticed a change on this. With the most recent deployment from last week, it no longer cuts off the text;

so !ai Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. does work

it's purely now the issue of a bang being at the end; it no longer gets detected.

archpareto

If I type a long search query in the address bar of my browser and decide at the end that I want to use Kagi assistant instead of Kagi search, I add the suffix !chat as documented on the bangs help page. Instead of redirecting my query to Kagi Assistant, my query is instead truncated and then sent to Kagi search with the message: Your query was trimmed because we limit queries to 32 words and 1024 characters.

This can easily be reproduced by entering something like this into Kagi search:

This is a very long question. It has a lot of words and fills my search bar to type. Only at the end do I specify that I want it to go to kagi assistant instead of kagi search. Does this work? !chat

It can also be reproduced with this link:

https://kagi.com/search?q=This+is+a+very+long+question.+It+has+a+lot+of+words+and+fills+my+search+bar+to+type.+Only+at+the+end+do+I+specify+that+I+want+it+to+go+to+kagi+assistant+instead+of+kagi+search.+Does+this+work%3F+%21chat

I would like trailing bangs to be applied prior to query trimming.

Thibaultmol

if you have a long query with a bang at the end, should just go to the bang directly. But because they first get trimmed, search doesn't see the bang and doesn't go to the bang destination.
This can happen if you ask long questions meant for !ai or !ki for example

holdenr

I'm having this same issue with using the "!ai" bang. Sometimes, I start typing a query and realize it's better formulated as a question to an LLM because I don't have exact keywords, so I write a long explanation into the Kagi box and throw a "!ai" at the end.

But if it's longer that 1024 characters, Kagi removes the ending bits and doesn't forward it to !ai at all, which is a pretty annoying behavior.

pbronez

Summary

Kagi truncates queries, which can cause it to miss bangs that would re-route the query away from the standard search experience. When bangs escape truncation, long prompts are routed with truncation. The main Kagi search result page warns about truncation, but other interfaces (including the Assistant) do not.

Background

I have Kagi set as my default search and usually query Kagi from my browser's search/address bar. I frequently use !bangs to define how Kaqi processes my query. When I intend to start an Assistant session (With !quick or !research) my queries frequently get truncated with the error "Your query was trimmed because we limit queries to 32 words and 1024 characters."

This truncation may be appropriate for web search, but it's limiting for assistant sessions. I want to provide extensive context and instructions to maximize the value of Assistant's long processing time.

Examples

Truncated With no Routing

If you put !research at the end of a long query, Kagi misses it entirely.

Query

Red Bull recently published a video showing a team of several professional bicyclists towing a glider down a runway. While it managed to get airborne, this seems unimpressive since longer flights have been achieved in several instances by human-powered ultralight aircraft with a single person driving a propeller via foot pedals. Why was the Red Bull performance so poor despite using more cyclists? !research

Result

Loads kagi.com/search. Query is truncated to:

The following warning appears at the top of the search page:

Your query was trimmed because we limit queries to 32 words and 1024 characters.

Truncated and Routed

If the !research is placed early in the query, it is routed correctly but silently truncated.

Query

!research Red Bull recently published a video showing a team of several professional bicyclists towing a glider down a runway. While it managed to get airborne, this seems unimpressive since longer flights have been achieved in several instances by human-powered ultralight aircraft with a single person driving a propeller via foot pedals. Why was the Red Bull performance so poor despite using more cyclists?

Result

Loads kagi.com/assistant with a truncated initial prompt. It actually preserves less of the prompt that the search does:

Red Bull recently published a video showing a team of several professional bicyclists towing a glider down a runway. While it managed to get airborne, this seems unimpressive since longer flights

In this case, there is no warning that the prompt has been truncated.

I expect Kagi to utilize my full prompt regardless of what interface I submit it to. When my query is truncated, I expect Kagi to warn me that it manipulated my query.