Connections

A role gives focus. A connection needs permission.

AI provider access, business-service authorization, and technical integrations are separate choices. Know what each one enables and where your information goes.

01 · AI providers

Bring your supported AI tools.

Codex

Preview

Purpose: Generate AI contributions through a separately installed command-line tool. Supplied-context, tool-free drafting has genuine-provider test evidence.
Prerequisites: An installed, authenticated tool and any required provider account or subscription. Versions and workflow compatibility require release validation.
Information & permissions: Selected instructions and context reach the provider. Local tool workflows can have separate file, shell, and network permissions. Review the configuration before use.
Setup: Set up the provider tool separately, then select it in a CrewParley agent profile. This website does not authenticate your AI account.

Claude Code

Preview

Purpose: Generate AI contributions through a separately installed command-line tool. Supplied-context, tool-free drafting has genuine-provider test evidence.
Prerequisites: An installed, authenticated tool and any required provider account or subscription. Versions and workflow compatibility require release validation.
Information & permissions: Selected instructions and context reach the provider. Local tool workflows can have separate file, shell, and network permissions. Review the configuration before use.
Setup: Set up the provider tool separately, then select it in a CrewParley agent profile. This website does not authenticate your AI account.

02 · Business services

Gmail is a local preview foundation.

Gmail

Preview · unavailable to agents

Current purpose: Owner-initiated account testing and a small read-only mail preview in the desktop. Real Google validation and public release remain pending.
Requested permission: gmail.readonly. The foundation cannot send mail, create drafts, organize messages, or download attachments through the managed policy.
Setup & credentials: Owner configuration is required. Without a configured CrewParley Google client, connection setup is unavailable. The implemented Windows flow protects the refresh token with user-scoped DPAPI.
Content & recipients: The documented native preview reads from Google into the desktop window. It does not forward messages to an AI provider. No Gmail agent execution bridge is available.
Disconnect: The desktop blocks local use, attempts Google revocation, and removes the local credential. If revocation fails, use Google account permissions to revoke access.

Planned

Other business services

Email, calendars, storage, messaging, and Custom API catalog entries do not establish working integrations. They are not advertised as available here.

03 · Advanced technical configuration

Custom MCP
needs its own review.

Preview · real-server validation pending

An advanced profile path can configure MCP servers for external Codex or Claude tools. Authentication, read/write capabilities, and data handling depend on the selected server and tool configuration.

Configuration tests are not proof of a working production integration or per-action isolation. A role profile and an internal approval do not substitute for service authorization.

Read about data & permissions

A clearer way to work

Your direction.
More perspectives.

Explore a desktop workspace built around the work you want to move forward.

Request Access Read the getting-started guide