Repository navigation
feat: add code mode connection recovery - #8215
ThomasRooney wants to merge 4 commits into
Conversation
Keep connection status and browser sign-in inside the Python host API. Recovery does not grant member tool access or replace client catalogue consent. Runner protocol 2 carries the new helpers; deploy the matching runner image with the server.
|
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
All reported issues were addressed across 39 files
This PR changes authentication, authorization, or input validation. Ultrareviews find 2.4x more serious bugs than standard reviews. Comment @cubic-dev-ai ultrareview to run one.
View guided diff | Turn on auto-fix | Re-trigger cubic
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
All reported issues were addressed across 17 files (changes from recent commits).
Requires human review: Auto-approval blocked because this review re-detected 1 unresolved issue already reported by Cubic.
View guided diff | Turn on auto-fix | Re-trigger cubic
There was a problem hiding this comment.
All reported issues were addressed across 19 files (changes from recent commits).
Reply with feedback, questions, or to request a fix.
View guided diff | Turn on auto-fix | Re-trigger cubic
ThomasRooney
added
preview
Summary
Enrich
tools.servers()with separate consent and authentication state plus recovery instructions. Addtools.connect(server=...)to return a short-lived browser URL bound to the requesting user and member. Theexecutedescription shows how to discover a blocker and obtain its link in one Python execution; no separate status helper or native MCP tool is added.Inventory reports known metadata without upstream probes or credential refresh. Connection changes preserve pagination cursors. Visible members needing approval remain discoverable with an empty tool allowlist or expired catalogue; business-tool authorization remains enforced separately. Renewing catalogue consent still requires reconnecting the gateway in the MCP client.
The runner protocol moves to version 2. Deploy the matching runner image with the server.
Private Reflow review app contains the synthetic end-to-end walkthrough, retained test reports and rollout notes.
Motivation
An agent encountering
consent_requiredneeds an actionable recovery path. Including connection metadata in normal server discovery removes a separate status lookup, andconnectsupplies the user handoff without replaying a program or widening tool permissions.🚀 Preview Environment (PR #8215)
Preview URL: https://pr-8215.dev.getgram.ai
Gram Preview Bot