WhatsApp connection process could crash when a request timed out
Timeouts now reconnect instead of exiting, and a crashed worker is restarted with backoff.
Issues
Known issues and their status, updated 2026-10-07. To report a problem, use the form below. In the app, Settings → Diagnostics → Export diagnostics makes a redacted bundle you can mention in the report.
Report an issue
Known issues
Messaging log contained full phone numbers and was readable by other programs
Identifiers are masked, the log and WhatsApp keys are owner-only, and debug chatter is off by default.
Some incoming WhatsApp messages failed to decrypt and were lost silently
Failed messages are retried, broken sessions are reset, and you are told when a message could not be read.
Reconnecting after a drop retried every second
Reconnects back off from 2 to 60 seconds, and connection health is shown in Settings.
Explore mode blocked read-only commands the agent was told to use
More read-only commands are allowed, hints are accurate, and other commands ask (Allow once) instead of failing.
Scheduled automations failed without telling anyone
Failures notify you after two runs, pause after five, and show in Mission Control's Failing jobs.
An app update during a running chat lost work in progress
Updates wait until the app is idle, and interrupted tool calls are marked clearly after restart.
grep was replaced by a stricter tool and folder listings were compressed
The standard grep and find are used, and directory listings are never compressed.
Tool output over about 30 KB was moved to a file too often
Up to 100 KB is shown inline, with an excerpt for larger output.
The automation event log was mostly clock ticks
Only ticks that run an automation are logged.
No general application log for troubleshooting
The app keeps rotating main and window logs, error codes with Copy details, and a redacted Export diagnostics bundle.
Guarded mode was undocumented and hard to reach
The mode cycle includes Ask/Guarded and all four modes are documented.
Internal permission mode names showed up in settings and views
Views and docs accept the names you see in the app (Explore, Execute).
An internal engineering note shipped in the bundled docs
Removed, with a build check that keeps internal notes out.
Website showed an old version and had broken links
The version comes from the live release, links are checked on every deploy, and this changelog, roadmap and issue page are public.
Databricks sign-ins expired without warning
Sign-ins refresh automatically, expiry is shown a day ahead, and Reconnect is one click.
"Session recovery triggered" appeared during long thinking
Long thinking and model retries keep the session alive; the app checks with the server before declaring a turn interrupted.
GitHub Copilot models showed the wrong context limit and no thinking
Fabric uses the limit Copilot enforces and reads thinking support from Copilot.
Connection lost after the computer slept
The app reconnects immediately on wake and keeps events from before the sleep.