← ClaudeAtlas

nativewright-login-bootstraplisted

Use when a site requires manual human login for the first time in the NativeWright Chrome profile, or when a previously logged-in session has expired — specifically bootstrapping Google / Microsoft / GitHub / SaaS sessions that automation cannot complete on its own. Establishes persistent login that future NativeWright runs will reuse.
barongoj3693/nativewright · ★ 0 · AI & Automation · score 72
Install: claude install-skill barongoj3693/nativewright
# NativeWright Login Bootstrap A one-off ritual that establishes a persistent logged-in session in the NativeWright Chrome profile. After this runs once per site, every future NativeWright run can drive the site as an authenticated user without re-entering credentials. ## When to use - The target site returns a login page when NativeWright navigates there. - A previously working logged-in flow suddenly bounces through login (session expired — Google typically re-auths every ~14 days). - You are setting up a fresh machine and need to seed the profile with accounts. ## When NOT to use - The site accepts API tokens or service accounts — use those instead. - The site supports SSO and your profile already has the SSO provider logged in — just navigate; SSO should auto-complete. ## The procedure This requires the human partner at the keyboard. You cannot log in on their behalf. The goal: open the login page in the visible Chrome window, let the human log in, confirm it worked, stop the daemon cleanly. The profile now holds the cookies. ### 1. Confirm no Chrome is already using the profile The profile is locked exclusively. Check: ```bash nativewright status # Windows: tasklist | findstr chrome # Unix: pgrep -fl chrome ``` If `status` shows `running: true`, reuse it — skip to step 3. If a regular Chrome window is open against the same profile directory, close it first. ### 2. Start the daemon in a background task ``` Bash(command='nativewright start', run_in_backgrou