New Kagi Assistant not all threads accessible

[gergan]

Hi, there is probably a solution to this, or I need to use the tool in a different way. I have some assistant threads that are accessible, but the new ones return an error. They have changed the URL recently for the assistant, so it is probably relevant in some way. This is the error returned for the new threads: "parse error: assistant thread open response did not include a thread.json frame"

[Microck]

sorry for the delay answering this. for next time please open an issue instead of a discussion, i see those much faster.

this is a real bug, not something you're doing wrong. kagi changed the assistant backend recently and new threads return a different stream format that doesn't include the thread.json frame the parser expects. old threads still work because they respond with the legacy format.

i'm pushing a fix now that adds a fallback to parse thread metadata from the thread.html frame (which kagi still sends for new threads). same kind of breakage as the expires_at thing a while back. will link the PR here once it's up. @gergan

[Microck]

fixed in v0.14.1: https://github.com/Microck/kagi-cli/releases/tag/v0.14.1

run kagi upgrade or reinstall to get the fix.

[gergan]

Hi @Microck thank you for your work and for your help.
The new assistant's chats have export feature and I use it now instead of the cli, but giving Kagi-Threads through your cli to llms is godsend :)
Probably better to open a bug, but as you posted here and the fact that the original problem still exists for me - I'll report it here:
the newest version (0.14.1) somehow still is not working for me:

kagi assistant thread get yyyyy-xxxx-yyyy-zzzz-abcdxxxxxxxx
parse error: assistant thread open response did not include a thread.json or thread.html frame (received tags: hi, tags.json, error.json)

where yyyyy-xxxx-yyyy-zzzz-abcdxxxxxxxx is the id from the url https://assistant.kagi.com/chat/yyyyy-xxxx-yyyy-zzzz-abcdxxxxxxxx
Moreover I think kagi assistant thread list still lists the old threads before their migration to folders and away from the tags.

[Microck]

fixed in v0.14.2: https://github.com/Microck/kagi-cli/releases/tag/v0.14.2

you were right - this was still on the old thread backend. thread get/list/export/delete now use the current assistant.kagi.com/api conversation endpoints, and thread get/export/delete accept the full https://assistant.kagi.com/chat/<uuid> URL too.

I also covered the paginated messages case so long threads export fully instead of stopping at the first page. run kagi upgrade, reinstall, or update kagi-cli to 0.14.2.

thanks for the precise repro.