Dodaios is an open-source agent OS for your desktop: it runs your coding agents, browser and apps by voice or chat, on your own machine. Formerly Personal Jarvis.
Plugin authentication and end-to-end audit
RUB-94, observed 2026-09-12. Acceptance incomplete: 46 plugins attempted through the real UI, 0 full PASS, 46 BLOCKED, 0 unexplained FAIL. Every plugin has a final PASS/BLOCKED classification for the current attempt, but the complete connection and lifecycle acceptance criteria are not satisfied. Do not close the ticket on this evidence.
This inventory supersedes earlier claims that mocked DCR checks proved working logins. Source configuration is dodaios/marketplace/seed_catalog.json; the companion machine-readable audit binds each row to its current auth and execution configuration using config_fingerprint from scripts/ci/check_plugin_auth_contract.py.
Evidence boundaries
Every catalog plugin has an observed Connect or Reconnect entry. A stage-level ui: PASS means the UI attempt was observed, not that Add, installation or connection completed. A stage-level browser: PASS means an official provider page was reached, not that authorization succeeded. Google Drive, Gmail, Google Calendar, Linear, Notion and Cloudflare now have verified real read-only smoke actions using existing grants. No plugin has a verified complete clean-state callback, new connected state, disconnect/reconnect and post-restart lifecycle in this audit.
Eleven existing connections were preserved: github, gmail, google_drive, google_calendar, youtube_music, youtube_studio, x, telegram, notion, cloudflare and linear. Their Reconnect controls were exercised without revoking working credentials. They were not tested from a clean, unconnected state. Existing credentials and existing Connected labels do not prove the new flow. The remaining rows describe connection attempts, not certified fresh installations.
The real runtime was exercised on Windows. Linux/macOS behavior and clean installation, update migration, refresh/expiry, consent denial, timeout/retry, disconnect and restart remain unverified unless a later dated observation explicitly replaces this statement. A partial network sample is not a complete error-free network audit. Automated contract tests are separate evidence and cannot promote a row to end-to-end PASS.
Audit matrix
“Not verified” and “Not run” are BLOCKED stages, never implied successes. Each blocker names its owner and next action. The machine-readable artifact records all seven stages: UI, browser, callback, connected, smoke, reconnect and restart. Restart is unverified for all 46 plugins.
Shopify (added 2026-09-21, after the RUB-94 observation) has one observed UI attempt: the card rendered and Connect was clicked, but the initial DCR configuration failed before any browser page opened. It is temporarily absent from the shipped seed catalog because no publisher-shared OAuth app or completed browser journey exists. The connector manifest remains in source, and its blocked observation is archived in shopify-pending-e2e.json. Restore the built-in only after provisioning the shared app and recording a clean PASS for UI, browser, callback, connected state, a real read-only action, reconnect and restart. The historical counts above still describe the 2026-09-12 observation.
Twenty-six further hosted MCP services (Atlassian, Sentry, PayPal, Zapier and others) support the one-click DCR path and are prepared as drafts outside the shipped catalog. Their connect flow was probed up to the provider's sign-in page; no account journey has run. See quick-win-connectors.md.
| Plugin | Add works | Browser auth | Callback | Connected state | Real smoke test | Reconnect | OS/provider limitations | Result | Remaining blocker |
|---|---|---|---|---|---|---|---|---|---|
github (GitHub) |
Reconnect entry only; existing connection retained | Reached (2026-10-05) | Not verified | Existing state only; new grant not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared "Personal Jarvis" OAuth App (owned by the PersonalJarvis organisation, Device Flow on, non-expiring tokens, no client secret) is registered and its public client id ships in SHIPPED_PUBLIC_CLIENT_IDS. On 2026-10-05 a device-code request with that id succeeded and github.com/login/device showed the consent page for "Personal Jarvis by PersonalJarvis" with logo and the catalog scopes; the final authorize click was not completed because the browser tab was not visible. Owner: Project publisher. Next: Repeat the full clean in-app journey (connect, smoke, reconnect, restart). Observation: Existing connection retained; Reconnect opens publisher-pending dialog with expert fallback collapsed. Clean disconnect/reconnect blocked by missing publisher device client. |
vercel (Vercel) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Connect opened official vercel.com/oauth/authorize; provider sign-in required. No user token or client setup. |
supabase (Supabase) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Connect opened supabase.com/dashboard/sign-in via provider DCR. Account sign-in required. |
notion (Notion) |
Reconnect entry only; existing connection retained | Provider page reached; authorization incomplete | Not verified | Existing state only; new grant not verified | PASS: notion/notion-fetch; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Official provider consent page reached; a new resource access grant awaits explicit account-holder approval. Owner: Provider account holder. Next: Approve the intended workspace or cloud resource grant, then verify callback, action, reconnect and restart. Observation: Existing connection retained; Reconnect reached real Notion workspace consent. New grant awaits explicit user approval for workspace access. Continued observation: the real UI-triggered notion/notion-fetch result is_error=false, duration 790 ms. Full clean-state/lifecycle acceptance remains unverified. |
slack (Slack) |
Connect entry observed before the 2026-10-05 change; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Slack app registration is pending. On 2026-10-05 the plugin moved from Slack's hosted MCP server (which Slack opens only to Marketplace-listed or internal apps) to the native Slack Web API tool slack with eleven user scopes; that configuration has contract tests only and has not been exercised live. Owner: Project publisher. Next: The shared Slack app (PKCE, token rotation, catalog user scopes) and its token broker are wired with an HTTPS redirect via token.personaljarvis.ai/oauth/slack/callback, but the broker's SLACK_CLIENT_SECRET is not set yet, so the exchange answers 503. Set the secret, register the broker callback in the Slack app and activate public distribution, then repeat the full clean browser journey with a real read-only slack action. Observation (before the change): Connect Slack Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. |
linear (Linear) |
Reconnect entry only; existing connection retained | Provider page reached; authorization incomplete | Not verified | Existing state only; new grant not verified | PASS: linear/get_workspace; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Official provider consent page reached; a new resource access grant awaits explicit account-holder approval. Owner: Provider account holder. Next: Approve the intended workspace or cloud resource grant, then verify callback, action, reconnect and restart. Observation: Existing connection retained; Reconnect reached official mcp.linear.app authorization page for Personal Jarvis. Continued observation: the real UI-triggered linear/get_workspace result is_error=false, duration 188 ms. Full clean-state/lifecycle acceptance remains unverified. |
atlassian (Atlassian: Jira & Confluence) |
Clean connect from Not connected (dev instance, 2026-10-05) | PASS: official Atlassian sign-in and site consent via DCR | PASS | PASS: Connected - Live after tool listing | PASS: atlassian/getVisibleJiraProjects returned the site's project | PASS: disconnect, consent again, Connected; restart kept the grant | Windows only; other OSes not exercised. Needs a Jira or Confluence Cloud site: an account without one gets Atlassian's Access denied page | PASS | None. |
stripe (Stripe) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Connect opened official dashboard.stripe.com/login. Provider account sign-in required; no manual token or client setup. |
cloudflare (Cloudflare) |
Reconnect entry only; existing connection retained | Provider page reached; authorization incomplete | Not verified | Existing state only; new grant not verified | PASS: cloudflare/workers_list; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Official provider consent page reached; a new resource access grant awaits explicit account-holder approval. Owner: Provider account holder. Next: Approve the intended workspace or cloud resource grant, then verify callback, action, reconnect and restart. Observation: Existing connection retained; Reconnect reached official workers-observability approval page for Personal Jarvis; private cloud resource access requires approval. Continued observation: the real UI-triggered cloudflare/workers_list result is_error=false, duration 1829 ms. Full clean-state/lifecycle acceptance remains unverified. |
discord (Discord) |
Connect entry observed; browser-primary dialog with token fallback | Not reached (publisher client pending; /connect/start reports 409 by design) | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | No publisher-shared Discord OAuth client is provisioned yet; the real UI offers browser sign-in first and the bot-token dialog as fallback with verified-ID fill and guild-picker helpers. Owner: Project publisher. Next: Register the official shared Discord app (redirect http://127.0.0.1:3129/oauth/callback, Message Content Intent, minimal install params), provision publisher_discord_oauth_client_id/secret, then verify all seven stages with a real read-only action. Gateway messaging still needs the bot token via the fallback (documented provider exception). |
telegram (Telegram) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Local channel bot credential is required; no replacement credential was supplied. Owner: Provider account holder. Next: Provide an authorized test credential through onboarding, verify a real action and lifecycle, and retain the documented browser-standard exception. Observation: Existing bot connection; Reconnect opened token onboarding. Official Bot API requires bot token; no replacement bot credential supplied, existing connection preserved. |
asana (Asana) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect Asana Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
google_drive (Google Drive) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | PASS: real list_files, one result; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Owner: Project publisher and provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Jarvis Chat called google_drive/list_files with max_results=1; persisted tool_result is_error=false, duration 571 ms, one returned file. No file names or contents are included in this audit. |
gmail (Gmail) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | PASS: gmail/list_messages; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Working credential retained; only Reconnect entry was inspected, without a clean disconnect or completed new grant. Owner: Provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Existing connection; Reconnect entry: Connect Gmail You'll sign in with your Google account in the browser. Use your own OAuth client (advanced) Cancel Continue Continued observation: the real UI-triggered gmail/list_messages result is_error=false, duration 290 ms. Full clean-state/lifecycle acceptance remains unverified. |
google_calendar (Google Calendar) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | PASS: google_calendar/list_events; existing grant | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Working credential retained; only Reconnect entry was inspected, without a clean disconnect or completed new grant. Owner: Provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Existing connection; Reconnect entry: Connect Google Calendar You'll sign in with your Google account in the browser. Use your own OAuth client (advanced) Cancel Continue Continued observation: the real UI-triggered google_calendar/list_events result is_error=false, duration 606 ms. Full clean-state/lifecycle acceptance remains unverified. |
todoist (Todoist) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Official app.todoist.com/auth/login reached from Connect; account sign-in required. |
clickup (ClickUp) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Connect reached app.clickup.com/api provider page; see provider state. |
dropbox (Dropbox) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Add/Connect opened dropbox.com/oauth2/authorize. Real login form observed; account sign-in not supplied. |
canva (Canva) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Official canva.com login page reached from Connect; account sign-in required. |
airtable (Airtable) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Add/Connect opened airtable.com/login. Real provider sign-in observed; account sign-in not supplied. |
cal_com (Cal.com) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Add/Connect opened app.cal.com/auth/login. Real login form observed; account sign-in not supplied. |
home_assistant (Home Assistant) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Address-only browser onboarding opened, but no reachable instance address was supplied. Owner: Home Assistant administrator. Next: Supply the intended reachable instance and approve its browser login, then verify a real state read and lifecycle. Observation: Connect opens address-only browser login dialog. No instance address or reachable Home Assistant host supplied; no token requested. |
spotify (Spotify) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect Spotify Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
youtube_music (YouTube Music) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Working credential retained; only Reconnect entry was inspected, without a clean disconnect or completed new grant. Owner: Provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Existing connection; Reconnect entry: Connect YouTube Music You'll sign in with your Google account in the browser. Use your own OAuth client (advanced) Cancel Continue |
higgsfield (Higgsfield) |
Connect entry observed; completion blocked | Official sign-in page reached on retest; authorization incomplete | Not verified after fix | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Official provider sign-in page reached after the scope-selection fix; account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify callback, real action, reconnect and restart. Observation: Real UI Connect retest reached the official Higgsfield sign-in page; its DOM was inspected. Requested scopes were openid email offline_access. The earlier invalid_scope callback did not recur; sign-in and authorization remain incomplete. |
outlook (Outlook Mail & Calendar) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect Outlook Mail & Calendar Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
onedrive (OneDrive) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect OneDrive Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
teams (Microsoft Teams) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect Microsoft Teams Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
sharepoint (SharePoint) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect SharePoint Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
onenote (OneNote) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect OneNote Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
microsoft_todo (Microsoft To Do) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect Microsoft To Do Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
aws (AWS) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Official eu-central-1.signin.aws.amazon.com sign-in reached; AWS identity/account authorization required. |
azure (Microsoft Azure) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The shared Personal Jarvis sign-in is installed. A live connect start returns Microsoft's authorize address with the shared public client, the loopback redirect and this plugin's scopes, then the flow was cancelled before approval. Owner: Provider account holder. Next: Click Connect, approve Microsoft once, then verify a real read, reconnect and restart. Observation: Connect Microsoft Azure Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
google_cloud (Google Cloud) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Configured Google client launched accounts.google.com account chooser; consent/resource access not completed. |
gitlab (GitLab) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect GitLab Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Expert token alternative Cancel Continue |
agentmail (AgentMail) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The UI requests an existing-account API key; no plugin credential was supplied and the browser standard remains unmet. Owner: Provider account holder. Next: Provide an authorized test credential through onboarding, verify a real action and lifecycle, and retain the documented browser-standard exception. Observation: Connect AgentMail Access token · Access Token 1 Generate a token at AgentMail Create an API key in your own AgentMail console and paste it here. Existing skill credentials are not copied automatically. Open AgentMail tokens Copy Or copy this link and open it in your browser yourself. 2 Paste the ... |
x (X (Twitter)) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Working credential retained; only Reconnect entry was inspected, without a clean disconnect or completed new grant. Owner: Provider account holder. Next: Complete an approved reconnect and separately verify a clean installation, real action and restart persistence. Observation: Existing connection; Reconnect entry: Connect X (Twitter) You'll sign in with your X account in the browser. Use your own OAuth client (advanced) Cancel Continue |
linkedin (LinkedIn) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect LinkedIn Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
meta (Meta (Facebook & Instagram)) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Current UI still requires a token. Publisher confidential HTTPS OAuth broker and app review are missing; Meta does offer OAuth. Owner: Project publisher. Next: Provision the reviewed publisher app and confidential HTTPS broker, implement the browser default, then test Graph access and lifecycle. Observation: Connect Meta (Facebook & Instagram) Access token · Access Token 1 Generate a token at Meta (Facebook & Instagram) Create a long-lived user token for your own Meta app. Request pages_show_list, pages_read_engagement, pages_manage_posts, instagram_basic and instagram_content_publish. App review may... |
youtube_studio (YouTube Studio) |
Reconnect entry only; existing connection retained | Not reached | Not verified | Existing state only; new grant not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Working credential retained; only Reconnect entry was inspected, without a clean disconnect or completed new grant. Owner: Provider account holder. Next: 2026-10-05: the shipped Google Desktop client now connects with zero setup; code exchange and refresh go through the project token broker (token.personaljarvis.ai), which holds the client secret. Not yet verified end to end: complete a clean-state browser sign-in through the broker, a real read-only action, disconnect/reconnect and restart persistence. Observation: Existing connection; Reconnect entry: Connect YouTube Studio You'll sign in with your Google account in the browser. Use your own OAuth client (advanced) Cancel Continue |
hubspot (HubSpot) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect HubSpot Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Expert token alternative Cancel Continue |
apollo (Apollo.io) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Official app.apollo.io login reached; provider account sign-in required. |
salesforce (Salesforce) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect Salesforce Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
granola (Granola) |
Connect entry observed; completion blocked | Provider page reached; authorization incomplete | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Provider account sign-in has not been completed. Owner: Provider account holder. Next: Complete official sign-in and consent, then verify all seven stages with a real read-only plugin action. Observation: Official mcp-auth.granola.ai sign-in reached from real Connect; account sign-in required. |
zoom (Zoom) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | Publisher OAuth client is missing; the real UI displays publisher setup pending. Owner: Project publisher. Next: Provision the official shared OAuth registration and any required review, then repeat the full clean browser journey. Observation: Connect Zoom Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Cancel Continue |
figma (Figma) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | On 2026-10-08 the owner connected Figma through the shipped client and the deployed token broker; the stored grant carries a refresh token and the GET /v1/me read check passed. The app is still a draft that only its own team can authorize; reconnect and restart were not observed. Owner: Project publisher. Next: Submit the Figma app for public review, then repeat the clean browser journey with a non-team account. Observation: Connect Figma Browser sign-in is not available yet. Browser sign-in is pending publisher setup. No developer account or client registration is required from you. Use your own OAuth client (advanced) Expert token alternative Cancel Continue |
amd_gpu (AMD GPU Status) |
Connect entry observed; completion blocked | Not reached | Not verified | Not verified | Not run | Not completed | Supported Linux AMD host required | BLOCKED | Real UI reports unsupported OS: this connector needs a compatible Linux AMD host with AMD SMI. Owner: Hardware test operator. Next: Run the no-login connection and real telemetry read on a supported Linux AMD host, then verify lifecycle. Observation: Plugins Skills Plugins MCPs Plugins AMD GPU Status Unsupported on this device · Home & Devices Connect AMD GPU telemetry is unavailable on this operating system. This connector requires a compatible Linux AMD host with AMD SMI. Read AMD GPU utilization, temperature and driver data through AMD SMI... |
shopify (Shopify) |
Connect entry observed; card renders with logo, Connect fails honestly | Provider page not reached (wrong flow, now corrected) | Not verified | Not verified | Not run | Not completed | Windows UI only; other OSes not exercised | BLOCKED | The first configuration used Dynamic Client Registration, but Shopify publishes no DCR registration_endpoint, so Connect failed before any browser page opened ("provider request failed"). The entry now uses Authorization Code + PKCE loopback against the publisher-shared app (loopback http://127.0.0.1:3130/oauth/callback, RFC 8707 resource https://setup.shopify.com/mcp, comma-joined read scopes). The shared app is not provisioned yet, so the dialog reports browser sign-in pending; no store-owner sign-in has been completed either. Owner: Project publisher. Next: Register the official shared Shopify app (redirect URI above, read scopes for products, orders, customers and discounts), provision publisher_shopify_oauth_client_id/secret, then repeat the full clean browser journey with a real read-only plugin action. Until then an expert can connect with their own Shopify app client through the dialog's advanced option. Observation: Connect on the Shopify card returned the generic failure dialog on 2026-09-21; live metadata at setup.shopify.com serves OAuth discovery but no registration endpoint. |
Provider-specific interpretation and primary sources
- Vercel, Supabase and Stripe now use browser-primary hosted MCP authentication. The real UI reached official sign-in pages; this does not establish a completed grant or usable tool. See Vercel MCP, Supabase MCP, and Stripe MCP.
- Home Assistant opens an address-only dialog before the instance's browser login. An instance address is an ordinary connection prerequisite. No access token is requested by that dialog. See Home Assistant authentication API.
- Discord is browser-primary for identity (OAuth
identify/guilds/guilds.members.read/connectionsplus the official guild-picker invite) with the bot-token paste kept as expert fallback. Its gateway runtime credential and server installation remain distinct from the user OAuth login: the bot token still enables message receiving, and no user Bearer token is ever used as a bot token. See Discord OAuth2 and permissions. Telegram is likewise a Bot API channel; its token requirement is specific to this API, not every Telegram product. See Telegram Bot API. - AgentMail onboarding requests a key from the existing account console and does not copy another tool's credentials. Its quickstart documents account API keys. This is a documented integration limitation, not evidence that a browser login has been tested.
- Meta supports OAuth. The current connector's token-paste path does not meet the browser standard. The remaining publisher work is a confidential HTTPS callback/broker and required app review. The archived official OAuth client implementation demonstrates OAuth token exchange; it is historical evidence, not current approval of this project's app. Current Meta documentation could not be retrieved during investigation (HTTP 429), so unsupported-provider claims are not justified.
- Notion, Linear and Cloudflare reached official consent pages. Workspace/cloud-resource grants remain pending account-holder approval. Their pre-existing connections were preserved.
- Higgsfield initially returned
invalid_scope. The scope-selection fix uses protected-resource scopes instead of the issuer-wide scope set. A new real UI Connect run reached the official Higgsfield sign-in page, inspected in the browser DOM, withopenid email offline_access; the earlier error did not recur. This verifies the repaired sign-in entry, not successful authorization or a usable plugin. Account sign-in remains BLOCKED. - Shopify connects through the official hosted MCP at
https://setup.shopify.com/mcp. Shopify publishes OAuth discovery but NO Dynamic Client Registration endpoint, so the plugin uses Authorization Code + PKCE loopback against the publisher-shared app (loopback redirect, RFC 8707 resource indicator, comma-joined scopes) — the same shape as the other PKCE-loopback plugins. The remaining publisher work is registering that shared app with the loopback redirect URI and the four read scopes, then completing a store-owner sign-in. The connector manifest remains in source for future qualification; Shopify is not offered in the default catalog. See Shopify authentication and the Storefront MCP family.
Release and maintenance gate
Run python scripts/ci/check_plugin_auth_contract.py for configuration, matrix coverage and attestation integrity. Historical BLOCKED rows may pass this structural check only with concrete blocker evidence; that does not make them standard-ready. An unresolved FAIL is deliberately rejected. A plugin may carry acceptance: "verified" in the seed catalog only with a completed PASS row; every other plugin ships as "preview" and shows a Preview badge in the app. Run python scripts/ci/check_plugin_auth_contract.py --require-e2e-pass for release qualification; it additionally requires every PASS to ship as verified and prints how many plugins ship as preview.
A new built-in plugin must carry a complete real journey PASS before release. Record a genuine functional action for smoke evidence; discovery or listing available tools is insufficient. An auth/execution configuration change invalidates the fingerprint and requires renewed relevant observations. Never refresh a fingerprint to disguise stale successful evidence.
For closure, complete all independently achievable repairs and replace each remaining external BLOCKED row only with new observed evidence or a precisely maintained external dependency. The ticket's acceptance criteria remain unsatisfied while clean-state, functional and lifecycle verification is missing. The audit itself must never be presented as completion of those checks.
Continued functional and navigation work
The compact catalog is now the direct navigation destination, defaulting to Plugins with Plugins, MCPs, Skills ordering. This UI work does not reduce the plugin acceptance scope. Google Drive, Gmail, Google Calendar, Linear, Notion and Cloudflare each have a genuine successful safe action through Jarvis Chat; all full-plugin results remain BLOCKED until their complete required journeys are proven.
Slack now runs through the native Slack Web API tool instead of Slack's hosted MCP server, because Slack admits only Marketplace-listed or internal apps to that server. Canvas scopes were dropped with it. Only exact old default catalog configurations migrate; custom scopes, clients, redirects, servers and existing grants are preserved. Sources: Slack MCP server, PKCE for Slack apps.
Shared clients through the token broker (2026-10-05)
The app now ships two shared clients whose providers demand a client secret:
- Google. The "Personal Jarvis" Desktop client covers gmail, google_drive, google_calendar, youtube_music, youtube_studio and google_cloud.
- Slack. The distributed "Personal Jarvis" Slack app covers slack.
The app holds neither secret. For grants of these shipped clients, the code exchange and every refresh go to the project token broker at token.personaljarvis.ai, a Cloudflare Worker whose source is workers/token-broker in the website repository. The broker adds the secret server-side. Slack's browser redirect also lands on the broker's https callback, which bounces it to the loopback listener. An expert override or a publisher_<family>_oauth_* secret still talks to the provider directly, and revocation always goes to the provider. auth_standard.ready is now true for these seven plugins with zero setup.
Verified so far:
- The live Google route returns Google's
invalid_grantfor a made-up code, which shows the secret is attached. Without the secret, Google answersclient_secret is missing. - The live Google route refuses a non-loopback redirect with the broker's own 400.
- The live Slack callback bounces only
code,stateanderror. - App-side routing is covered by
tests/unit/marketplace/test_token_broker.py.
Not verified:
- No clean-state browser sign-in through the broker, no real action on a new grant, no reconnect and no restart persistence. All seven rows therefore stay BLOCKED.
- The Slack route answers 503 until its
SLACK_CLIENT_SECRETis set and the broker callback is registered in the Slack app.
Compact-window acceptance
The section opens directly into the existing compact dialog, defaults to Plugins, and orders tabs Plugins, MCPs, Skills. Direct Skills and MCP deep links select their respective tabs. Browser checks verified tab switching, default-on-reopen, Escape close and focus restoration to the Plugins navigation button. Both light and dark presentations were visually inspected with the real catalog loaded. A transient backend startup outage recovered before the final light-mode check.
The first generic GitHub read used cli_gh and is excluded as plugin proof. A strict plugin request exposed unconditional CLI suppression despite live GitHub MCP tools. Explicit registered plugin tool requests now survive that suppression, with URL/path false positives excluded. A subsequent live attempt stopped at the chat runtime provider/model mismatch before dispatch; this is not a successful plugin retest.
Worker selection and native MCP follow-up
The incompatible worker model override was removed through the product API, preserving the configured provider. After the authorized app restart and selecting the default model in the composer, a Codex turn completed without the former model rejection. It still reported the GitHub plugin unavailable.
Two producer/adapter repairs are implemented: provider switching now synchronizes one authoritative provider/model pair across TOML, current and legacy environment overrides, drift configuration and memory; native MCP export now maps valid canonical names such as github/get_me to stable portable aliases and resolves them through the current authorized catalog before safety-gated execution. Custom task/session restrictions and canonical gateway identities are preserved. These are code/test results, not live plugin acceptance.
The final browser retest is blocked by an unavailable Codex Chrome connection. Documented diagnostics found Chrome running and its extension enabled but the required native-host registration absent. Browser-plugin restoration is required; no native-host registration was manually bypassed or repaired. The existing publisher/account/hardware prerequisites and full clean-state lifecycle requirements remain unchanged.