Connections · In development
Vynce’s proposed connections bring useful context and actions into the conversation. Every platform has its own permissions and limits; we’re designing around those boundaries from the start.
Connect with intention
Choose what is available, understand what a connection permits, and review actions that change something. A planned integration is not a live connection or permission to read an entire account.
Proposed connection map
Availability depends on implementation, platform review, account eligibility, and policy checks. No integration on this page is currently active.
Workspace messaging
Connect a workspace through Slack OAuth with the scopes needed for a defined workflow.
Channel and history access depend on scopes and app membership. Sending as the app needs a write scope and Vynce's action approval.
Slack OAuth documentationBot conversations
Use a dedicated Telegram bot in conversations where you choose to involve it.
A bot sees messages addressed to it and permitted group messages. The Bot API does not connect your full personal message history.
Telegram bot visibilityBusiness messaging
Explore eligible business messaging workflows through the WhatsApp Business Platform.
Requires a business setup, recipient opt-in, and applicable message-template rules. General-purpose agent eligibility needs further policy review. This is not a personal inbox connection.
WhatsApp messaging policyLocal companion research
Investigate an explicitly configured Mac-based companion for supported Messages workflows.
Apple's public Messages framework does not establish a general personal-inbox cloud API. Compatibility, permissions, and platform terms need validation.
Apple Messages frameworkSelected repositories
Review code and prepare changes through an installation scoped to repositories you choose.
Start with the minimum GitHub App permissions. Write actions and permission increases require the appropriate approval.
GitHub App permissionsTime and planning
Use explicitly granted calendar access to understand availability and propose changes.
The implementation must separate reading from creating or editing events, disclose requested access, and verify OAuth requirements before launch.
Google Calendar authorizationSelected home entities
Connect your own authenticated, reachable Home Assistant instance and choose the entities Vynce may use.
Vynce must enforce device and action limits; the instance token does not itself guarantee granular device scopes. No safety-critical automation is proposed.
Home Assistant authenticationLocal execution
A local companion would use selected files and applications under your operating system's permission controls.
Screen and computer permissions are separate from approval for a specific action. Selected context may still be processed by cloud model services.
macOS accessibility accessA local companion
Computer assistance is planned through software you choose to install and operating-system permissions you explicitly grant.
A local executor may interact with selected files and applications, but that does not make all processing on-device. Audio and transcripts would go to the configured OpenAI voice service; selected context and screenshots may go to Claude for reasoning.
The implementation must disclose what leaves the device, let you stop the task, and keep secrets out of model inputs. Publishing a concrete data-flow and retention policy is a prerequisite for a live pilot.
Read the current privacy noticeIn development
Select the tools you use when joining the waitlist. We’ll use that interest to help prioritize a focused pilot.