← Commit history

Publish 0.8.10

John Lauer ·6944df7a7c ·3mo ago ·parent 8f563e3
4 files changed +12−8
SKILL.md+9−5
@@ -69,7 +69,8 @@ adom-google auth ```  This grants full Workspace scopes (`gmail.modify, contacts, drive, spreadsheets, documents,-presentations, calendar, tasks, chat.messages, chat.spaces.readonly`) plus the generic+presentations, calendar, tasks`, plus Chat: `chat.messages, chat.spaces, chat.memberships,+chat.delete, chat.customemojis, chat.users.*`) plus the generic `adom-google api <url>` passthrough for **any** Google API. It prints a Google consent URL; the user clicks **Allow** once. @@ -80,9 +81,12 @@ user clicks **Allow** once. > (`adom-desktop nbrowser_open_window '{"sessionId":"gauth","url":"<URL>"}'`), or single-quote the > whole URL. The `adom-google auth` output prints the ready-to-paste safe command for you. -> ⏱ **The user has ~10 minutes to click Allow.** The gateway keeps the sign-in session alive-> with a WebSocket heartbeat, so there's no rush. If they ever see a "Session Expired" page, just-> re-run `adom-google auth`.+> ⏱ **The user has ~60 minutes to click Allow — do NOT rush them.** The gateway keeps the+> sign-in session alive for the full hour, and since v0.8.6 the session also SURVIVES a dropped+> WebSocket: the CLI reconnects and claims the result, so a wifi blip, a sleeping laptop, or the+> ingress killing an idle socket no longer costs the user their sign-in. (Before that fix a+> disconnect silently destroyed the session and Allow showed "Session Expired" minutes in.) If a+> "Session Expired" page ever does appear, just re-run `adom-google auth`.  *(Advanced/rare: `adom-google auth --safe` grants narrower create-only scopes — only the Drive/Sheets/Docs/Slides files this app makes, no "delete all". Do NOT prompt for it; use it@@ -91,7 +95,7 @@ only if the user explicitly asks to minimize scopes.)* ## Auth — one consent, long-lived refresh token  ```bash-adom-google auth            # authorize (FULL Workspace access — the default; ~10 min to approve)+adom-google auth            # authorize (FULL Workspace access — the default; ~60 min to approve) adom-google auth --safe     # advanced: narrower create-only scopes (no delete-all) adom-google auth --manual   # fallback: desktop-client paste flow adom-google auth-code '<code>'   # finish --manual
VERSION+1−1
@@ -1 +1 @@-0.8.9+0.8.10
package.json+1−1
@@ -1,6 +1,6 @@ {   "slug": "adom-google",-  "version": "0.8.9",+  "version": "0.8.10",   "type": "app",   "license": "MIT",   "description": "Drive your whole Google Workspace from the terminal \u2014 Gmail, Contacts, Drive, Sheets, Docs, Slides, Calendar, Tasks, Google Chat, plus a generic `api` passthrough to hit ANY Google API. Connect a personal @gmail (or another org's Google account) with ZERO setup via Adom's hosted Connector (`adom-google connect-personal`), or bring your own token-broker gateway (`provider set`) \u2014 Adom staff use the private adom-google-adom provider. One-click OAuth, no client secret on your machine.",
page.json+1−1
@@ -4,7 +4,7 @@   "slug": "adom-google",   "title": "Adom Google",   "brief": "Drive your whole Google Workspace from the terminal — Gmail, Drive, Sheets, Docs, Slides, Calendar, Tasks, Chat + any Google API.",-  "version": "0.8.9",+  "version": "0.8.10",   "visibility": "public",   "install": {     "binary_name": "adom-google"