Google kills your refresh tokens every 7 days while your OAuth app is still in 'Testing'. I built my own command-line tool for Gmail, Drive and Sheets. gcloud couldn't do the job. Its token carries only Google Cloud scopes, and its OAuth client isn't even allowed to request Gmail or Drive scopes. I skipped a Claude connector on purpose, because it holds one account at a time and the whole point was covering more than one. So now my tool does the usual mail actions from list to trash, plus Drive find/download/upload and Sheets read/append. The part I care about most is what it can't do. Every outbound action (send, reply, draft-send, trash, sheets append) shows a preview and refuses to act without --yes. Plain drafts are exempt, a draft isn't outbound. It also can't permanently delete mail at all. The scopes are gmail.modify plus gmail.send instead of full mail access, so trash stays recoverable for 30 days and purge is impossible. I published the app to production to get rid of the 7 day expiry. Setup was finished on 2026-08-03 with both accounts verified on live data. Small gotcha: Drive's 'contains' search matches word prefixes, not substrings. --name "Guestlist" finds the file, --name "uestlist" misses it. My lesson is to put the safety limits into the permissions themselves, so I don't have to trust myself to be careful later. When you wire your own tools into email or Drive, do you lock them down with narrow OAuth scopes and confirm-before-send, or do you rely on being careful?