Connect Corvio to WorkBuddyConnect Corvio to WorkBuddy

Install or upload the official corvio-operate-workspace Skill through WorkBuddy's Skills surface. Then add https://api.corvio.ai/mcp in Connector or MCP settings and complete Corvio OAuth. WorkBuddy currently owns these as separate installation receipts.

Start a fresh conversation after either change. MCP-only installation can expose tools without reliably teaching the Agent when Corvio should enter an ordinary planning, research, or deliverable task; Skill-only installation has no live Corvio authority. Corvio supplements the same task: keep WorkBuddy's native files and deliverables, then preserve valuable results beside them.

Current WorkBuddy MCP configuration supports defer_loading at both server and tool level. Keep the Corvio server deferred, but override search and ask_corvio to false so the Agent sees the two first-decision semantic entries before it commits to a native-only path. Search is the bounded prior-work read; ask_corvio is the delegated synthesis and durable-result entry. The remaining continuation, upload, table, and lifecycle tools can stay deferred.

This is a WorkBuddy-owned host setting; Corvio's Anthropic alwaysLoad metadata cannot configure it. Merge the official workbuddy-mcp.json Corvio entry into the MCP configuration that WorkBuddy actually loads, preserve unrelated servers, then start a fresh conversation. A visible bare server name or a successful OAuth connection is not proof that either entry schema reached the model.

Until Corvio reports a reviewed WorkBuddy marketplace listing, an uploaded Skill is an unmanaged manual install. WorkBuddy sync can copy that account or local version, but it cannot pull a newer Corvio package that is not registered in its marketplace. A filesystem mtime such as 02:43 is not a version or freshness receipt.

Run corvio collaboration status --provider workbuddy --json --no-input from a local terminal to compare the discoverable ~/.workbuddy/skills/corvio-operate-workspace/SKILL.md copy with Corvio's current release, content hash, compatibility family, and minimum revision. The command is read-only and cannot prove which bytes an already-running conversation loaded. needs_skill and stale_skill are local CLI result states, not push events from Corvio.

First call list_workspaces, then call search without workspace_id and inspect workspace_routing; Corvio should use the account selection, personal default, or only authorized candidate without making the Agent invent IDs. Next use a natural task that does not name Corvio and provides no prior material, then confirm the Agent reads before planning. If results conflict, confirm WorkBuddy asks which authority to use.

For the write case, ask for a non-sensitive substantive deliverable without requesting Corvio. WorkBuddy should keep its native result and ask once before saving the specific result. Approve the proposal, then verify a durable Corvio object and current readback. Also test an explicit Corvio upload request, which should not trigger a duplicate confirmation, and a sensitive or explicitly local-only task, which should make no Corvio call. Tool visibility and OAuth alone are setup receipts, not write consent or proof that WorkBuddy chooses Corvio correctly.

Corvio's remote server cannot dereference a WorkBuddy-local path. When WorkBuddy can read the generated file and issue an HTTP PUT, call prepare_file_upload, PUT the exact bytes with the returned short-lived URL and headers, then call finalize_file_upload. The final Asset ID, hash, policy, and link are the upload receipt.

If the current question depends on that file, pass the finalized Asset ID in the same ask_corvio call's asset_ids and poll get_question. A retained Asset is not automatically an input to an unrelated question. If the host cannot perform the byte PUT, use corvio ask --file or ask the user to attach/upload the file. Do not send base64 through MCP, expose the signed URL in chat, or call preparation a completed upload.

After finalize, choose the next value deliberately: pass a supported Markdown Asset as source_asset_id to create an editable Page, or call organize_files for a coherent source set that needs reader-ready structure and future retrieval. Poll get_file_operation to terminal and inspect output_document, source_reconciliation, and skills_evaluation. Stable facts/preferences belong in Memory; only qualifying reusable methods become Project Skills, and evaluated_no_qualifying_skill is a valid result.

If Corvio says the request was approved but WorkBuddy never becomes connected, Corvio consent succeeded and the remaining host callback or token exchange did not complete. The authorization URL and code are single-use; refreshing or reopening the old Corvio link cannot finish the connection.

Return to WorkBuddy's Connector or MCP settings and start a new Corvio connection. Keep WorkBuddy running, use only the newest authorization page within its 10-minute window, and leave the registered http://127.0.0.1 callback unchanged. A successful run ends on WorkBuddy's authentication-success page and shows the Connector as connected; do not copy an authorization code or replace the loopback callback with a shared URL.

A 401 response means the OAuth connection is missing or expired. A missing Workspace or document usually means current membership or document ACL does not allow it. A 403 insufficient_scope on Asset tools means an older connection must be reauthorized with assets:read/assets:write; do not switch to a shared secret.

WorkBuddy configuration changes over time. If the UI does not match this guide, search Corvio Product Guidance or WorkBuddy's current official help using the goal 'add a remote HTTP MCP', while preserving the same OAuth and ACL boundaries.