Feedback links from agent break session

ChristianBod

Firstly, I am inside the app on an android device

the agent provided me a link to your feedback pages which tried to open in the app and errored and messed up my session with the agent (AI)

I believe the problem is as simple as the agent providing the wrong feedback address - it should not be an URL handled by the app but one on the kagifeedback.org domain allowing the feedback to open outside the app not interrupting current workflow.

I didn't expect it to take me to an error page and break my AI session.

Thibaultmol

Is it possible to link the assistant thread because I can't seem to be able to reproduce it

ChristianBod

You'll havee to guide me through how to do that idiot style (,as in I'm the idiot not you!)

Thibaultmol

ChristianBod if you're on mobile, open the thread from the sidebar and press the kagi logo at the top middle

If you're on desktop, open the sidebar and press the ... menu and press share

ChristianBod

Hmm . I'm with you I can't reproduce it right now either - that said I'm pretty sure when I clicked on the link before it opened a link in a webview inside the app rather than (as it has today) opened the link in chrome outside the Kagi app

(sorry it took so long I didn't get notified / emailed there was a response,)

RoxyRoxyRoxy

Can I ask how the session broke? Even if you navigate to another page it shouldn't mess up.

ChristianBod

RoxyRoxyRoxy

Sorry you'll need to treat me like an idiot.

RoxyRoxyRoxy

Right well the session breaking thing is a general (non) issue I think. Firstly I used the term session incorrectly I think (newbie sorry).
I probably should describe it as a thread but I'm struggling to nail down my terminology it's a basic Confusion in my head between session, thread, and context.

Basically in a few places in the app if I make a change and press back rather than close buttons (submit?) then the change seems to get accepted but if it's a change that has an impact on the current thread the current thread display state will jump to an earlier state losing a few interactions and effecting the scroll position within that thread. The actual thread itself is still intact on your end I'm just being displayed a cached version of it I suppose. If I ask the agent to restore context it can and if I reclick on the thread it updates. If it was a pure web interface in browser the browser would stick up a modal dialog about leaving the page and losing data or saving changes or similar. But as it's a hybrid interface theres no such dialog if I exit using back rather than close.

That's my take on my "session" breaking comment anyway. Not a bug just an issue which caused me some confusion until I found the workaround / changed my behaviour to try to use close+submit buttons rather than back when in the app interface.

Hope that helps rather than hinders!