Integration Capabilities Overview
Open Integration Architecture
DesireCore connects to external systems through several layers: built-in tools provide core capability, MCP connects external services, CUA Driver / HostAgent serve different device-automation scenarios, and skills package specialized workflows.
MCP lets you connect services that expose APIs. Computer Use covers selected applications that have no suitable API, subject to platform, accessibility, permission, and UI limitations.
Installed apps and plugins share the Apps entry, with peer tabs for use and configuration. Discover new products in Marketplace and manage service connections and runtime diagnostics in Resources. See Apps, Plugins, and Services.
Capability Map
| Integration | Description | Documentation |
|---|---|---|
| Built-in tools | Files, search, command execution, network requests, user questions, and workflows | Built-in Tools |
| MCP services | Connect external APIs and services through Model Context Protocol | MCP Integration |
| Skills | Package tools and instructions into reusable workflows | Skill Packs |
| Computer Use | Local GUI control through HostAgent on macOS and temporarily through bundled CUA Driver on Windows; other HostAgent platforms are still evolving | GUI Desktop Automation |
| Manage Gmail, Outlook, and IMAP accounts | Email Management | |
| Workflows | Compose triggers, code, LLM, Agent, and human-confirmation nodes | Task Orchestration |
| Apps, Plugins, and Services | Distinguish app use, plugin contribution management, and service connection diagnostics | Apps, Plugins, and Services |
Email Integration
DesireCore supports Gmail, Outlook, and IMAP/SMTP accounts with a unified inbox, AI-assisted classification and summaries, drafting and replies, rules, offline cache, and incremental synchronization. See Email Management.
Code Repository Integration
Through MCP and supported services, Agents can participate in repository workflows such as pull requests, issues, and code search. Review the requested target and external side effects before approving writes, comments, merges, or releases. See MCP Integration.
Object Storage Integration
MCP services can connect S3-compatible and other object-storage systems for upload, download, listing, search, deletion, and batch organization. Credentials and external writes remain subject to the service's permissions and DesireCore approval policy.
Desktop and Mobile Devices
When no suitable API or tool exists, Computer Use can operate local graphical interfaces on macOS and Windows. On macOS, connect HostAgent and grant the required system permissions. On Windows, CUA Driver is bundled and enabled by default.
- Local macOS applications: operated by HostAgent through native macOS capabilities and applicable system permissions
- Local Windows applications: operated by the bundled CUA Driver through accessibility elements, mouse, and keyboard
- Linux, other desktops, and mobile devices: GUI automation is not yet available
- Screen awareness: screenshots and accessible UI text may enter model context and can contain sensitive data
Computer Use is not reliable for every interface. Custom-drawn controls, the UAC secure desktop, locked screens, elevated applications, and protected content may be unavailable. External effects such as sending, payment, deletion, or publication should remain user-confirmed. See GUI Desktop Automation.
Observability and Audit
DesireCore records supported tool calls, approvals, and external operations so users can review what was requested and executed. The exact detail depends on the tool and service; logs may contain sensitive metadata and should be protected. See Audit Trail.
Custom Integrations
Choose the extension path that matches the task:
- Build an MCP service for a stable internal or external API.
- Create a skill for reusable instructions, scripts, and workflows.
- Use Computer Use for occasional local Windows UI tasks without an API.
- Create a workflow for repeatable trigger, code, LLM, Agent, and human-confirmation sequences.