You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/capability-auth.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ The device code flow works identically across all providers.
31
31
1. Auth flows work on any deployment: headless server, SSH session, Telegram bot.
32
32
2. No browser or public URL is required on the machine running Ash.
33
33
3. Users complete consent on their own device — phone, laptop, or any browser.
34
-
4. Existing `auth_begin`/`auth_complete`(authorization code) flows continue to work unchanged.
34
+
4. Existing caller-facing `auth_begin`/`auth_complete` flows continue to work; auth completion normalization is centralized in host capability manager.
35
35
5. Skills detect flow type from `auth_begin` response and adapt UX accordingly.
36
36
37
37
## Device Code Flow
@@ -325,7 +325,8 @@ Update `src/ash/integrations/skills/capabilities/google/SKILL.md` auth section t
325
325
326
326
-`flow_type` defaults to `"authorization_code"` — existing bridges and skill flows keep working.
327
327
-`auth_poll` is handled by the manager delegation wrapper: when the provider is missing or doesn't implement it, raises `CapabilityError("capability_invalid_input", "auth polling not supported by this provider")`.
328
-
- Existing `auth_complete` with `code`/`callback_url` continues to work for redirect-based flows.
328
+
- Existing caller-side `auth_complete` with `code`/`callback_url` continues to work for redirect-based flows.
- New fields in `auth_begin` return dict (`flow_type`, `user_code`, `poll_interval_seconds`) are nullable/defaulted — callers that don't check them are unaffected.
0 commit comments