I think I understood the points mentioned here https://github.com/aws/nova-act?tab=readme-ov-file#authentication-cookies-and-persistent-browser-state and also read this from #26 (comment).

Note: I think exposing your system level profile path is not a good option at all as mentioned in the docs but (i may be wrong here, feel free to correct) what if a bug comes in via the sdk and it wipes down the system level profile dir for that user or modifies a file even if the flag to "not wipe" is correctly passed. Because of this reason I'm leaning towards having a new context for whatever I do using the sdk.

In my understanding of this authenticated session for a website example.com (here the context is for a new profile):

• One has to create a /tmp/new-nova-profile dir
• Point nova to this new dir and then follow https://github.com/aws/nova-act?tab=readme-ov-file#entering-sensitive-information for putting in the login information
• and based on this nova.page.keyboard.type(getpass()) and considering my website's login system uses TOTP after entering the email

So, considering these points^, will I be able to let the system wait and get the TOTP from my email and then enter via command line prompt and then can have successful user session? and then from there further actions on new runs can use that save session from this new /tmp/new-nova-profile dir ? (i believe that wipe not flag can be passed here).

Next, I think the way the sdk is expecting the session saving can be improved by letting the end user use a saved session from (for example):
npx playwright codegen "$BASE_URL" --save-storage=.auth/user.json and then let the sdk use this saved session.

Another thing to add here, what if there is a team of 5 people working on writing code for a project, with the proposed setup in the docs, it seems like they all have to create their respective "new chrome profiles" on their systems else one with the authenticated session user has to share the whole dir to other 4, I don't think that will work or is a feasible approach.

I want to know whether something like this is currently possible or not or if the team has future plans to adapt this?