connect_status
Tier: read-only · Tags: connect, read
Check whether the current user has an active ish connect tunnel
registered with the Ish backend. Works in hosted MCP mode (read-only;
unlike the local-only connect verb, it just reads backend state).
Call before dispatching study_run / ask_run against
locally-served iterations (platform="code" or a localhost /
RFC1918 URL): a missing tunnel makes the run fail fast rather than
stalling on a connection refused inside the cloud browser. See
docs_get("guides/mcp-add").
Other backend errors (auth, network, 5xx) propagate as the normal
IshApiError envelope.
Returns {"active": True, "tunnel_url", "local_port", "last_heartbeat", "created_at"} when a tunnel is registered, else
{"active": False}.
No parameters.