By default, the session created by supertokens expires only due to inactivity equal to the refresh token's lifetime. So by default, the users can be logged in for a long period of time, if they are active. That being said you can implement this feature by storing another token (a JWT for example) in the cookies which can be used has a fallback auth method in case the refresh token of the current session has expired. Is there anything else you were looking for?

I'm thinking about this feature now that we're live. I intend to implement it with a custom formField on at least the signIn custom form we have. Probably would also make sense on our email verify or signup, but one thing at a time. Is there a way to allow custom formFields on the signIn form similar to how it's done for the signUpFeature? I'm using the ThirdPArtyEmailPassword recipe. Maybe I'm going about this wrong though 🤔