Known Issues

This page lists major limitations in the current implementation that affect user expectations. It does not mean that any installer has completed public-release acceptance.

Releases and platforms

There is currently no verifiable public download channel, Release Notes, enabled automatic-update channel, or automatic rollback. A build version number alone does not establish a public support lifecycle.
No real publisher, official domain, Privacy Notice, EULA, Support Policy, or verified support/security contact has been established. Each is a hard gate for opening public downloads.
The macOS GA workflow makes Developer ID signing, Apple notarization, stapling, Gatekeeper verification, and artifact review mandatory gates. The repository has no production certificate, Apple-account credentials, or accepted notarization record, so it has not produced an installer for public distribution.
Windows and Linux have build entry points and component targets, but no complete public-release acceptance records.
The macOS GA engineering target is macOS 14 or later. Until final release-candidate acceptance and formal release, this remains an engineering target rather than a public support commitment.

Data and credentials

If the system credential backend is locked, access is denied, or an entry is missing, model or Tavily credentials appear as “unavailable” or “missing” and the related request fails safely. The application does not fall back to storing them in plaintext in SQLite.
There is no user-facing one-click data export, diagnostic bundle, or complete backup/recovery wizard.
Removing a project permanently deletes its in-app project conversations and attachment records; files in the project directory are not deleted.
There is currently no unified retention and cleanup policy for Automation history, events, and the notification outbox.

Models and context

Whether a compatible Provider actually supports Tools, streaming responses, and Usage must be verified for each endpoint.
Model context windows, image capabilities, and prices are configured primarily by the user; incorrect values may cause failures or inaccurate estimates.
Provider-specific continuation state is not guaranteed to migrate losslessly across Providers.
Very long tasks may still reach context, Tool-iteration, or compaction limits.

Skills and MCP

Skills are activated only for the current Run; persistent activation across conversations is not available.
Skill Scripts depend on local Python 3, have no operating-system-level script sandbox, and require approval every time they run.
External MCP Servers support only local stdio. HTTP, OAuth, environment variables/SecretRef, and MCP Resources/Prompts are not yet available.
Complete process-tree isolation for external MCP Servers on Windows is not yet guaranteed.
An MCP call may have an unknown outcome after a timeout or disconnect and cannot be retried safely automatically.

Browser and artifacts

Managed web pages cannot use the camera, microphone, location, or web notifications by default.
Browser automation does not connect to the system browser; it operates only the browser environment managed by the application.
Browser Artifacts are Run-lifecycle resources and must be exported explicitly for long-term retention.
Scanned PDFs may be unreadable without a text layer. Legacy .ppt and .xls are unsupported, and .doc reading is limited to macOS.

Scheduled Automation

It does not run as an operating-system background service after the application exits. Multiple missed times are merged into one recovery Run.
cron, one-time schedules, end dates, and an independent time-zone selector are not supported.
Pausing a task does not stop the current Run, and the interface has no separate control for cancelling an active Run.
Blocked does not clear automatically when an external resource is restored; the task must be fixed and saved again.
There is no Renderer Toast fallback for native notifications. Notifications may be delayed, absent, or duplicated once in a very small crash window.
If a notification is clicked before the interface is ready, only the most recent pending open request is retained.

For a reproducible problem not listed here, use Diagnostics and Logs to retain a minimal, redacted reproduction locally.