Repository navigation
OpenCoven Chat 0.0.3
Pre-releaseOpenCoven Chat v0.0.3
A small update to v0.0.2: replies are easier to read, a failed run keeps its
reason in the conversation, and the desktop app can now pair with an iPhone.
Like v0.0.2, this is an early 0.x pre-release without auto-update. Download
newer versions from the Releases page.
Before you install
Nothing changed here since v0.0.2. Chat drives the coven command already on
your machine, so install the Coven CLI and finish any model-provider setup it
asks for first. Builds are for macOS and Linux. There is still no Windows build.
What's new
Easier to read
- Reply text is larger, 16 px instead of 14, with slightly looser letter
spacing.
A failed run says why, and keeps saying it
- When a run fails after it has started, Chat adds a line to the conversation
with what is known about the failure: the engine's error, what the Coven CLI printed, or Chat's
own error, in that order of preference. If Coven gave no reason, the line
says so. The line has its own Copy report control. - The line stays in the chat after the error notice is dismissed. Before, the
reason was only in the notice, and when there was none, the notice pointed
you to the Coven CLI, which keeps no record of runs started from Chat. - A report the CLI printed before a reply broke off is no longer lost.
Attaching files
- Dropping a file onto the conversation while a reply is still coming used to
do nothing. It now says "Finish or stop the current reply before attaching a
file."
iPhone pairing, desktop side
- Sidebar options (⋯, above the familiar list) has a new
iPhone companion entry. Turn on companion shows a QR code and a
private pairing link for Chat on iPhone. A paired phone can read your Chat
conversations, send messages, follow replies and stop runs. Everything still
runs through the Coven CLI on this Mac, which needs to stay awake, with Chat
open, on the same local network as the phone. - The pairing link gives access to your Chat conversations, so share it only
with your own phone. Turn off stops the connection, and
Forget paired phones makes every phone pair again. - The iPhone app isn't publicly available yet. It is in internal testing,
so for now you can leave this off.
Changed
-
The Keyboard shortcuts list at the foot of the familiar list is gone. The
shortcuts all still work:Shortcut Does Cmd/Ctrl+K Search familiars Cmd/Ctrl+[ and ] Previous or next familiar Cmd/Ctrl+\ Show or hide the familiar list Cmd/Ctrl+Shift+\ Show or hide the inspector Cmd/Ctrl+F Find in the conversation
Platforms
| Platform | Download |
|---|---|
| macOS, Apple silicon | OpenCoven Chat_0.0.3_aarch64.dmg |
| macOS, Intel | OpenCoven Chat_0.0.3_x64.dmg |
| Linux | OpenCoven Chat_0.0.3_amd64.AppImage or .deb |
GitHub replaces the spaces in these names with dots, so the files you download
are named OpenCoven.Chat_0.0.3_…. SHA256SUMS still lists them with spaces,
so shasum -c reports them missing. Check your download by hand instead, and
compare the result with its line in SHA256SUMS:
shasum -a 256 OpenCoven.Chat_0.0.3_aarch64.dmg
Known limitations
These are unchanged from v0.0.2:
- No auto-update. Download newer versions from the Releases page.
- Replies arrive whole. With the
coven-code0.8.0 engine, a reply appears
in one piece once the familiar has finished writing it, not word by word. - Familiars run read-only, with no tool-approval controls.
- Project access isn't enforced by Chat. The Access tab shows what Coven
declares. - Text files only. Images and PDFs can't be attached.
- No token, cost or timing figures.
- No Windows build. See below for progress.
Under the hood
There are 12 merged changes since v0.0.2:
- Windows groundwork. Chat can now stop a run's whole process tree on
Windows, not only the Coven CLI it started. That was the first of two things
a Windows build was waiting for. The second is Windows code signing. - Release safeguards. The release workflow now refuses to build or publish
an unsigned macOS app on the production path, even when a failed job is
re-run, and notarizes with the team's App Store Connect API key. - The iPhone connection. The phone and the Mac talk over local HTTPS pinned
to the Mac's own certificate. The phone keeps its credentials in its
Keychain, on that device only. Requests are size-limited and authenticated,
and a send the phone isn't sure went through can't be delivered twice.