The cb_sessionid cookie for Codeberg, like most session cookies, typically expires when the browser session ends—that is, when you close your browser. Session cookies do not have a set expiration date and are stored in volatile memory, meaning they are deleted as soon as the browser is closed. Additionally, the server may invalidate the session after a period of inactivity, which can also cause the cookie to expire even if the browser remains opencookieyes.com+1.

If you notice the cookie expiring while the browser is still open, it is likely due to server-side session timeout settings, which are often set to 30 minutes of inactivity by default in many systemsibm.com. However, Codeberg's specific server-side session timeout may vary.

Would you like help checking Codeberg's official documentation or support for their exact session timeout policy?