Repository navigation
Releases
v0.2.2
Fixes from the first days of use.
- Scrolling a chat with a finger no longer selects message text; mouse and touchpad can still
select it (#464). - The long-press menu of a message is one compact row of icon buttons that fits a phone-width
window (#465). - The background service takes over receiving at once after a crash or restart instead of waiting
about 90 seconds (#399). - The sidebar no longer shows a cut-off "Conversations" title in a narrow window (#468).
- The welcome screen's Delta Chat page without a mail account no longer leaves a large gap (#479),
and Terms of Service links name their messenger instead of being cut off (#480). - The Flatpak no longer warns about GNOME Online Accounts on start when they are reachable (#478),
andcheckno longer reports GNOME as failed there for the missing Evolution Data Server (#422).
v0.2.1
A packaging release; the app itself is unchanged from 0.2.0.
- Every package now ships with its release record, so the download page shows the macOS
.dmgand
.zipas signed and notarised (they already were in 0.2.0; the page could not tell). - Screenshots keep the window's rounded corners and shadow and come in a light and a dark variant.
v0.2.0
The first public release.
What Curlew does
- One list for your mail and your chats from Telegram, Signal, WhatsApp, Matrix and XMPP. A person
you reach on several messengers is one contact, with a default messenger you can change. - Read and reply in the same window: text, pictures, videos, voice messages and files, sent and
received the same way on every protocol, with reactions, edits, deletions and replies where the
chat supports them. - Mail threads that carry the
Chat-Versionmarker show as email chats in the Delta Chat style.
Sending the marker is a setting of each mail account and off by default. - One search across chats and mail.
- A background service keeps receiving while the window is closed, so Signal and WhatsApp, which
keep no server archive, miss nothing. - A welcome screen walks through the protocols and accounts on the first start. Every setting is
in the window; nothing needs the command line. - AI assistants can use your messages over MCP only after you turn AI on, and then only per
account and contact as you allow. AI and read receipts are off by default. - English and German.
Packages
- Linux: Flatpak,
.deband.rpm(x86_64). Mail accounts from GNOME Online Accounts work in
every Linux package. - macOS (Apple silicon and Intel):
.dmgand.zip, signed and notarised. Preview, chat only. - Windows (x64):
.msiand.zip, not signed yet, so SmartScreen warns on first start. Preview,
chat only.
Known limits
- Signal, WhatsApp and XMPP groups can be read but not written to yet (#448); Telegram and Matrix
groups can. - Matrix sends to unencrypted rooms only; encrypted rooms are read.
- WhatsApp is an unofficial client and can get the account banned; Signal does not license
third-party clients. Both show their terms before you enable them. - Compatibility with Delta Chat itself is not confirmed against a live peer yet.
- Not on Flathub yet.
The development changelog up to this release:
docs/project/history-before-0.2.0.md.
v0.2.0-rc.5
Added
telegram.send: send one plain-text message (≤ 4096 characters) to a granted Telegram chat with
curlew sendorsend_message.messaging_capabilitieslists Telegram.matrix.send: send one plain-text message (≤ 32000 UTF-8 bytes) to a granted Matrix room with
curlew sendorsend_message. The target is<account>/<room id>, the room id as
conversations_listshows it. An end-to-end encrypted room is refused — curlew decrypts but
does not encrypt, and it sends no cleartext there.messaging_capabilitieslists Matrix.whatsapp.send: send one plain-text message (≤ 65536 UTF-8 bytes) to a granted 1:1 WhatsApp
chat withcurlew sendorsend_message. The target is<account>/<chat jid>, the JID as
conversations_listshows it; a bare phone number, a device address, a group and a status
update are refused. A send takes the receive lease, so it is refused while the daemon holds
the account — WhatsApp allows one connection per linked device.
messaging_capabilitieslists WhatsApp.send_messagetakes an optionalformat(plainby default, ormarkdown). Markdown is
rendered as XEP-0393 for XMPP, and texts over 7000 characters are split into several
messages. The answer then carriespartsandoriginIds.xmpp_wait_replytakes an optionalstrip_quotes(defaultfalse) that removes quoted
reply lines from the message text.- Agent access is enforced (ADR 0009): every agent send and every read of a message body is
checked againstagentAccessper account and contact — in the MCP tools and in the CLI's
agent commands. Onask,curlew daemonshows a notification (Allow once, For this
session, Always, Deny); no answer in 2 minutes, a dismissal or Deny refuses. New bus
methodRequestAccessoneu.jumplink.curlew.Daemon1. Searches that span contacts return only
the hits you allowed and reportwithheld. - The access notification names the contact —
Name (address)— for Signal, WhatsApp, Matrix
and mail, where the address alone is an ID nobody recognises. The daemon looks the name up in
its own index; a name in the request is ignored, and none known shows the address as before. - New read-only MCP tool
messaging_capabilities: per protocol the maximum message length,
formats, image support, maximum wait timeout and splitting.
Changed
-
Grants restrict agents, not the person (ADR 0008). The daemon follows every enabled XMPP
account without anxmpp.sendgrant, and the daemon's bus send service checks no grant.
curlew sendandsend_messagestill need a grant, except a message to the account itself,
which every backend recognises in its own spellings (Signal ACI, WhatsApp JID and LID, XMPP
JID with any resource, mail address, Telegram Saved Messages, Matrix user id) and which needs
no grant.send_messageis now always listed. -
Agents now need access to read message bodies. With no rule a body is
ask, so an agent
that read freely before is asked per contact (or refused when no daemon runs). The old
<backend>.sendgrants keep working as rules allowing read and write for that pair. A grant
for one backend's send now also covers the same account and address of another backend,
because rules are per account. Your own CLI and the GTK app are not affected. -
OMEMO is decrypted for every enabled XMPP account (ADR 0009 §9); the
xmpp.omemogrant is
gone and an old config that lists it still loads, the entry ignored. The daemon no longer
watches the config for grant edits, so it never exits with code 3 to restart.
Fixed
- The
curlew-daemon.servicedescription names XMPP.
Calls that omit the new inputs behave exactly as in 0.1.0.
v0.2.0-rc.4
Added
telegram.send: send one plain-text message (≤ 4096 characters) to a granted Telegram chat with
curlew sendorsend_message.messaging_capabilitieslists Telegram.matrix.send: send one plain-text message (≤ 32000 UTF-8 bytes) to a granted Matrix room with
curlew sendorsend_message. The target is<account>/<room id>, the room id as
conversations_listshows it. An end-to-end encrypted room is refused — curlew decrypts but
does not encrypt, and it sends no cleartext there.messaging_capabilitieslists Matrix.whatsapp.send: send one plain-text message (≤ 65536 UTF-8 bytes) to a granted 1:1 WhatsApp
chat withcurlew sendorsend_message. The target is<account>/<chat jid>, the JID as
conversations_listshows it; a bare phone number, a device address, a group and a status
update are refused. A send takes the receive lease, so it is refused while the daemon holds
the account — WhatsApp allows one connection per linked device.
messaging_capabilitieslists WhatsApp.send_messagetakes an optionalformat(plainby default, ormarkdown). Markdown is
rendered as XEP-0393 for XMPP, and texts over 7000 characters are split into several
messages. The answer then carriespartsandoriginIds.xmpp_wait_replytakes an optionalstrip_quotes(defaultfalse) that removes quoted
reply lines from the message text.- Agent access is enforced (ADR 0009): every agent send and every read of a message body is
checked againstagentAccessper account and contact — in the MCP tools and in the CLI's
agent commands. Onask,curlew daemonshows a notification (Allow once, For this
session, Always, Deny); no answer in 2 minutes, a dismissal or Deny refuses. New bus
methodRequestAccessoneu.jumplink.curlew.Daemon1. Searches that span contacts return only
the hits you allowed and reportwithheld. - The access notification names the contact —
Name (address)— for Signal, WhatsApp, Matrix
and mail, where the address alone is an ID nobody recognises. The daemon looks the name up in
its own index; a name in the request is ignored, and none known shows the address as before. - New read-only MCP tool
messaging_capabilities: per protocol the maximum message length,
formats, image support, maximum wait timeout and splitting.
Changed
-
Grants restrict agents, not the person (ADR 0008). The daemon follows every enabled XMPP
account without anxmpp.sendgrant, and the daemon's bus send service checks no grant.
curlew sendandsend_messagestill need a grant, except a message to the account itself,
which every backend recognises in its own spellings (Signal ACI, WhatsApp JID and LID, XMPP
JID with any resource, mail address, Telegram Saved Messages, Matrix user id) and which needs
no grant.send_messageis now always listed. -
Agents now need access to read message bodies. With no rule a body is
ask, so an agent
that read freely before is asked per contact (or refused when no daemon runs). The old
<backend>.sendgrants keep working as rules allowing read and write for that pair. A grant
for one backend's send now also covers the same account and address of another backend,
because rules are per account. Your own CLI and the GTK app are not affected. -
OMEMO is decrypted for every enabled XMPP account (ADR 0009 §9); the
xmpp.omemogrant is
gone and an old config that lists it still loads, the entry ignored. The daemon no longer
watches the config for grant edits, so it never exits with code 3 to restart.
Fixed
- The
curlew-daemon.servicedescription names XMPP.
Calls that omit the new inputs behave exactly as in 0.1.0.
v0.2.0-rc.3
Added
telegram.send: send one plain-text message (≤ 4096 characters) to a granted Telegram chat with
curlew sendorsend_message.messaging_capabilitieslists Telegram.matrix.send: send one plain-text message (≤ 32000 UTF-8 bytes) to a granted Matrix room with
curlew sendorsend_message. The target is<account>/<room id>, the room id as
conversations_listshows it. An end-to-end encrypted room is refused — curlew decrypts but
does not encrypt, and it sends no cleartext there.messaging_capabilitieslists Matrix.whatsapp.send: send one plain-text message (≤ 65536 UTF-8 bytes) to a granted 1:1 WhatsApp
chat withcurlew sendorsend_message. The target is<account>/<chat jid>, the JID as
conversations_listshows it; a bare phone number, a device address, a group and a status
update are refused. A send takes the receive lease, so it is refused while the daemon holds
the account — WhatsApp allows one connection per linked device.
messaging_capabilitieslists WhatsApp.send_messagetakes an optionalformat(plainby default, ormarkdown). Markdown is
rendered as XEP-0393 for XMPP, and texts over 7000 characters are split into several
messages. The answer then carriespartsandoriginIds.xmpp_wait_replytakes an optionalstrip_quotes(defaultfalse) that removes quoted
reply lines from the message text.- Agent access is enforced (ADR 0009): every agent send and every read of a message body is
checked againstagentAccessper account and contact — in the MCP tools and in the CLI's
agent commands. Onask,curlew daemonshows a notification (Allow once, For this
session, Always, Deny); no answer in 2 minutes, a dismissal or Deny refuses. New bus
methodRequestAccessoneu.jumplink.curlew.Daemon1. Searches that span contacts return only
the hits you allowed and reportwithheld. - The access notification names the contact —
Name (address)— for Signal, WhatsApp, Matrix
and mail, where the address alone is an ID nobody recognises. The daemon looks the name up in
its own index; a name in the request is ignored, and none known shows the address as before. - New read-only MCP tool
messaging_capabilities: per protocol the maximum message length,
formats, image support, maximum wait timeout and splitting.
Changed
-
Grants restrict agents, not the person (ADR 0008). The daemon follows every enabled XMPP
account without anxmpp.sendgrant, and the daemon's bus send service checks no grant.
curlew sendandsend_messagestill need a grant, except a message to the account itself,
which every backend recognises in its own spellings (Signal ACI, WhatsApp JID and LID, XMPP
JID with any resource, mail address, Telegram Saved Messages, Matrix user id) and which needs
no grant.send_messageis now always listed. -
Agents now need access to read message bodies. With no rule a body is
ask, so an agent
that read freely before is asked per contact (or refused when no daemon runs). The old
<backend>.sendgrants keep working as rules allowing read and write for that pair. A grant
for one backend's send now also covers the same account and address of another backend,
because rules are per account. Your own CLI and the GTK app are not affected. -
OMEMO is decrypted for every enabled XMPP account (ADR 0009 §9); the
xmpp.omemogrant is
gone and an old config that lists it still loads, the entry ignored. The daemon no longer
watches the config for grant edits, so it never exits with code 3 to restart.
Fixed
- The
curlew-daemon.servicedescription names XMPP.
Calls that omit the new inputs behave exactly as in 0.1.0.
v0.2.0-rc.2
Added
telegram.send: send one plain-text message (≤ 4096 characters) to a granted Telegram chat with
curlew sendorsend_message.messaging_capabilitieslists Telegram.matrix.send: send one plain-text message (≤ 32000 UTF-8 bytes) to a granted Matrix room with
curlew sendorsend_message. The target is<account>/<room id>, the room id as
conversations_listshows it. An end-to-end encrypted room is refused — curlew decrypts but
does not encrypt, and it sends no cleartext there.messaging_capabilitieslists Matrix.whatsapp.send: send one plain-text message (≤ 65536 UTF-8 bytes) to a granted 1:1 WhatsApp
chat withcurlew sendorsend_message. The target is<account>/<chat jid>, the JID as
conversations_listshows it; a bare phone number, a device address, a group and a status
update are refused. A send takes the receive lease, so it is refused while the daemon holds
the account — WhatsApp allows one connection per linked device.
messaging_capabilitieslists WhatsApp.send_messagetakes an optionalformat(plainby default, ormarkdown). Markdown is
rendered as XEP-0393 for XMPP, and texts over 7000 characters are split into several
messages. The answer then carriespartsandoriginIds.xmpp_wait_replytakes an optionalstrip_quotes(defaultfalse) that removes quoted
reply lines from the message text.- Agent access is enforced (ADR 0009): every agent send and every read of a message body is
checked againstagentAccessper account and contact — in the MCP tools and in the CLI's
agent commands. Onask,curlew daemonshows a notification (Allow once, For this
session, Always, Deny); no answer in 2 minutes, a dismissal or Deny refuses. New bus
methodRequestAccessoneu.jumplink.curlew.Daemon1. Searches that span contacts return only
the hits you allowed and reportwithheld. - The access notification names the contact —
Name (address)— for Signal, WhatsApp, Matrix
and mail, where the address alone is an ID nobody recognises. The daemon looks the name up in
its own index; a name in the request is ignored, and none known shows the address as before. - New read-only MCP tool
messaging_capabilities: per protocol the maximum message length,
formats, image support, maximum wait timeout and splitting.
Changed
-
Grants restrict agents, not the person (ADR 0008). The daemon follows every enabled XMPP
account without anxmpp.sendgrant, and the daemon's bus send service checks no grant.
curlew sendandsend_messagestill need a grant, except a message to the account itself,
which every backend recognises in its own spellings (Signal ACI, WhatsApp JID and LID, XMPP
JID with any resource, mail address, Telegram Saved Messages, Matrix user id) and which needs
no grant.send_messageis now always listed. -
Agents now need access to read message bodies. With no rule a body is
ask, so an agent
that read freely before is asked per contact (or refused when no daemon runs). The old
<backend>.sendgrants keep working as rules allowing read and write for that pair. A grant
for one backend's send now also covers the same account and address of another backend,
because rules are per account. Your own CLI and the GTK app are not affected. -
OMEMO is decrypted for every enabled XMPP account (ADR 0009 §9); the
xmpp.omemogrant is
gone and an old config that lists it still loads, the entry ignored. The daemon no longer
watches the config for grant edits, so it never exits with code 3 to restart.
Fixed
- The
curlew-daemon.servicedescription names XMPP.
Calls that omit the new inputs behave exactly as in 0.1.0.
v0.2.0-rc.1
Added
telegram.send: send one plain-text message (≤ 4096 characters) to a granted Telegram chat with
curlew sendorsend_message.messaging_capabilitieslists Telegram.matrix.send: send one plain-text message (≤ 32000 UTF-8 bytes) to a granted Matrix room with
curlew sendorsend_message. The target is<account>/<room id>, the room id as
conversations_listshows it. An end-to-end encrypted room is refused — curlew decrypts but
does not encrypt, and it sends no cleartext there.messaging_capabilitieslists Matrix.whatsapp.send: send one plain-text message (≤ 65536 UTF-8 bytes) to a granted 1:1 WhatsApp
chat withcurlew sendorsend_message. The target is<account>/<chat jid>, the JID as
conversations_listshows it; a bare phone number, a device address, a group and a status
update are refused. A send takes the receive lease, so it is refused while the daemon holds
the account — WhatsApp allows one connection per linked device.
messaging_capabilitieslists WhatsApp.send_messagetakes an optionalformat(plainby default, ormarkdown). Markdown is
rendered as XEP-0393 for XMPP, and texts over 7000 characters are split into several
messages. The answer then carriespartsandoriginIds.xmpp_wait_replytakes an optionalstrip_quotes(defaultfalse) that removes quoted
reply lines from the message text.- Agent access is enforced (ADR 0009): every agent send and every read of a message body is
checked againstagentAccessper account and contact — in the MCP tools and in the CLI's
agent commands. Onask,curlew daemonshows a notification (Allow once, For this
session, Always, Deny); no answer in 2 minutes, a dismissal or Deny refuses. New bus
methodRequestAccessoneu.jumplink.curlew.Daemon1. Searches that span contacts return only
the hits you allowed and reportwithheld. - The access notification names the contact —
Name (address)— for Signal, WhatsApp, Matrix
and mail, where the address alone is an ID nobody recognises. The daemon looks the name up in
its own index; a name in the request is ignored, and none known shows the address as before. - New read-only MCP tool
messaging_capabilities: per protocol the maximum message length,
formats, image support, maximum wait timeout and splitting.
Changed
-
Grants restrict agents, not the person (ADR 0008). The daemon follows every enabled XMPP
account without anxmpp.sendgrant, and the daemon's bus send service checks no grant.
curlew sendandsend_messagestill need a grant, except a message to the account itself,
which every backend recognises in its own spellings (Signal ACI, WhatsApp JID and LID, XMPP
JID with any resource, mail address, Telegram Saved Messages, Matrix user id) and which needs
no grant.send_messageis now always listed. -
Agents now need access to read message bodies. With no rule a body is
ask, so an agent
that read freely before is asked per contact (or refused when no daemon runs). The old
<backend>.sendgrants keep working as rules allowing read and write for that pair. A grant
for one backend's send now also covers the same account and address of another backend,
because rules are per account. Your own CLI and the GTK app are not affected. -
OMEMO is decrypted for every enabled XMPP account (ADR 0009 §9); the
xmpp.omemogrant is
gone and an old config that lists it still loads, the entry ignored. The daemon no longer
watches the config for grant edits, so it never exits with code 3 to restart.
Fixed
- The
curlew-daemon.servicedescription names XMPP.
Calls that omit the new inputs behave exactly as in 0.1.0.