OSuite Docs

Claude Desktop Extension

Primary OSuite rollout path for Claude Desktop with a packaged MCP server, hardened defaults, and a bundled behavior layer.

What this package is

Use this guide when you want Claude Desktop to stay as the working surface while OSuite becomes the authority layer for:

  • runtime sessions
  • approvals
  • replay
  • proof export
  • buyer-facing verification

This package is the primary distribution path for non-technical users. It avoids repo-local hook editing and instead ships one MCP server plus a behavior layer.

If your goal is public connector distribution inside Claude rather than desktop-only rollout, use Claude Connectors Directory.

What ships

  • .mcp.json
  • server/osuite_desktop_mcp.py
  • skills/osuite-governed-operator.md
  • manifest.json

Security defaults

The packaged distribution defaults to:

  • OSUITE_HOOK_MODE=strict
  • OSUITE_GUARD_FAILURE_MODE=block
  • OSUITE_SIGNATURE_MODE=required
  • assumption capture before irreversible work
  • governance posture is fixed in the public extension package

Install

  1. Fetch the package from GET /api/runtimes/claude-desktop/bootstrap.
  2. Add the .mcp.json server entry to Claude Desktop.
  3. Bind:
OSUITE_BASE_URL=https://studio.osuite.ai
OSUITE_API_KEY=<workspace-api-key>
OSUITE_AGENT_ID=claude-desktop-runtime
OSUITE_RUNTIME_ADAPTER_ID=claude_desktop_extension
OSUITE_RUNTIME_FAMILY=framework_sdk
OSUITE_ADAPTER_MODE=gateway
OSUITE_HOOK_MODE=strict
OSUITE_GUARD_FAILURE_MODE=block
OSUITE_SIGNATURE_MODE=required
OSUITE_INSTALL_CHANNEL=desktop_extension
OSUITE_SETTINGS_SCOPE=managed
  1. Apply the bundled behavior layer so consequential actions call OSuite first.

For a one-step local materialization flow, run:

npm run runtime:install:claude-desktop -- --target ./output/runtime-installs/claude-desktop-extension

This writes the packaged files, a managed .env.osuite, and INSTALL.md into the target folder.

Behavior model

The extension does not pretend to be a repo hook. Instead it exposes OSuite governance tools over MCP:

  • begin session
  • preflight action
  • record assumption
  • wait for approval
  • complete action

This keeps Claude Desktop conversational while making consequential work buyer-auditable.

Privacy

OSuite privacy policy: osuite.ai/privacy

Verify it

Advanced lane

If your team specifically wants repo-owned hook files, use Claude Code hooks.

Cookie settings

Essential cookies keep sign-in and workspace routing stable. You can separately choose Analytics cookies and Preference cookies.