Autogen Studio 0.4.2 runs and authentication issue

[dominiclachance]

@victordibia One more question that I think will be interesting. I am about 99% done with overhauling my app for AGS 0.4.2 and everything works great when using [email protected] to create sessions, runs and connect using websocket.

Now when I create the session using another user such as [email protected], it creates the session, creates the run, but when the websockets opens, it return a: User [email protected] is not authorized to access the run created by [email protected]. The trick is that at no time I am using [email protected]. My guess is that AGS is looking at the logged-in user which there isnt any and reverts to [email protected].

AGS BackEnd messages:

[2025-03-24 00:30:55 +0000] [65960] [INFO] ('15.157.201.134', 57544) - "WebSocket /api/ws/runs/743?token=null" [accepted]
[2025-03-24 00:30:55 +0000] [65960] [INFO] connection open
2025-03-24 00:30:55.863 | WARNING | autogenstudio.web.routes.ws:run_websocket:87 - User [email protected] not authorized to access run 743

If only GITHub authentication is in place and I dont use that for my clients but use Gmail authentication, is there any way to allow anyone to use a run even if they are unauthenticated. Otherwise, I could use [email protected] for the sessions and runs but the all the sessions are store under [email protected] and wont work long term.