AutoClaw international build: Google/M365 integration cards hidden; Feishu replies blocked by long turns; skills onboarding

Feedback for AutoClaw (Zhipu) — International Build

From: John F. (AutoClaw desktop user, macOS, international build v1.12.0 / gateway 2026.6.8)

1. Google/Microsoft integrations missing from Settings → Integrations

The Gmail / Google Calendar / Google Drive / Google Workspace / Microsoft 365 cards are not visible in the international build's integrations page. Digging into the app bundle, connectorStorage defines OVERSEA_VISIBLE_CONNECTOR_IDS as ["notion","github",...[],"vercel","cloudflare"] — the Google IDs (gmail, google-calendar, google-drive, google-workspace) exist in OVERSEA_CONNECTORS but are filtered out, while a second Set in the code (domestic build path) does include them.

The entire backend is present and running (the local productivity MCP at 127.0.0.1:19681 serves gmail_list_emails, google_calendar_list_events, etc., and the startIntegrationOAuth main-process handler fully supports Google providers via the connected-apps backend). The only missing piece is the visible Connect card.

Request: enable the Google + Microsoft 365 integration cards in the international build. Users are falling back to third-party gateways (maton.ai) or manual Google Cloud MCP setups because the official path appears to not exist.

2. Feishu/Lark UX: replies blocked by long-running turns

Agent replies to the Feishu channel only deliver when the turn completes. When the agent runs long jobs inside a chat turn (CI waits, builds — observed 20–45 min turns), the user's phone receives nothing for the entire duration. Diagnostics show messages queued 20+ minutes behind an active run ("lane wait exceeded ... waitedMs=1466252").

Requests:

• Consider streaming/partial delivery to chat channels for long turns, or auto-flushing an interim reply at a threshold (e.g. 5 min).
• Expose diagnostics.stuckSessionAbortMs / stuckSessionWarnMs in the desktop Settings UI — they're currently Hermes-protected control-plane paths, so power users can't tune them even via the gateway tool.
• A first-class "abort active turn" button in the desktop app (sessions.abort RPC exists but requires manual WebSocket + device-signature auth to reach).

3. Community skills have no onboarding

Store-installed skills (e.g. the gmail skill by "maton") drop a folder with a SKILL.md requiring MATON_API_KEY and an external OAuth flow, with no setup instructions in the app. A short "this skill requires X" prompt at install time would prevent confusion.

Filed via Claw (OpenClaw agent) on John's behalf, with his permission. He's happy to be contacted for follow-up.

Start by tracing connectorStorage's OVERSEA_VISIBLE_CONNECTOR_IDS and OVERSEA_CONNECTORS, then inspect the startIntegrationOAuth handler. Separately review the Feishu delivery path, diagnostics settings, sessions.abort RPC, and installed SKILL.md flow. Done would require agreed scope and verification for integration visibility, long-turn replies or controls, and skills setup guidance.