Integration Compatibility
This page describes the current implementation scope. It is not a certification list for arbitrary third-party products. Compatibility may also change when third-party services are updated.
Model Providers
| Capability | Current status |
|---|---|
| OpenAI-compatible Chat and Tool Calls | Supported through the corresponding generic adapter |
| Anthropic-compatible Messages and Tool Use | Supported through the corresponding generic adapter |
| DeepSeek V4 Chat reasoning continuation | Supported through a dedicated configuration |
| Arbitrary OpenAI/Anthropic gateways | Not guaranteed; each endpoint must be verified |
| Automatic model and price discovery | Not supported; users configure model information |
Skills
| Capability | Current status |
|---|---|
| Project Workspace Skills | Supports .agents/skills/<name>/SKILL.md |
| Built-in and user-installed Skills | Can be managed from Settings |
| Installation from GitHub and authorized local directories | Supported after inspection |
| references/assets/templates/scripts | Supported as validated package resources |
| Arbitrary online Skill Registries | Not yet available |
| Persistent activation across Runs | Not supported |
Skill Scripts currently support only Python 3 scripts and require high-permission prerequisites plus approval for every execution.
MCP
| Capability | Current status |
|---|---|
| Local stdio MCP Server | Supported |
| Tool discovery and invocation | Supported for complete, validated Catalogs |
| Prompt / Auto / Deny invocation policies | Supported by the backend; the UI mainly offers per-call confirmation and automatic execution |
| Streamable HTTP / HTTP Server | Not supported |
| OAuth / PKCE | Not supported |
| User environment variables, SecretRef, and headers | Not supported |
| Resources, Prompts, Sampling, Elicitation, Tasks, and MCP Apps | Not yet connected to the Agent usage path |
Built-in Managed Playwright uses a managed MCP channel, but this is not a general-purpose transport available for third-party reuse.
Documents and artifacts
- Attachment reading supports common formats including PDF, DOCX, PPTX, XLSX, CSV, and TSV.
- Legacy
.docfiles can be read through system capabilities only on macOS;.pptand.xlsare not currently supported. - Whether a scanned PDF can be read depends on whether the file contains a text layer.
- Generating Word documents, spreadsheets, presentations, PDFs, and images depends on managed components bundled with the application. Availability also depends on package validation for the platform and on the required Provider configuration.
Platform differences
macOS, Windows, and Linux all have native packaging entry points, and the managed component manifests list x64/arm64 resources for those platforms. The current packaging commands do not independently prove that every combination has been built and accepted. macOS remains the primary tested platform. See Platform and Build Status for the evidence boundary; a build target does not constitute public release support.