Yeah, it's an interesting concept. The downside is that even if the user does sign in via oauth 2, there's no way that the model can persist the access token fo

Yeah, it's an interesting concept. The downside is that even if the user does sign in via oauth 2, there's no way that the model can persist the access token for subsequent calls (unless, idk, OpenAI/Gemini/others built persistence for access tokens obtained like this in their own tool calling infra, i guess it's possible) What you could do is maybe create and host your own token storage, include a tool to retrieve it from within each kodec.txt file based on some reference id cookie in the browser, and see how far you get there