District AI for Linux
The native District AI app for the Linux desktop, in Rust with GTK 4 and libadwaita. The call log with each call's summary and transcript, the inbox with a reply written by AI when you ask, contacts and the rest of the workspace; and in a build with calls, as both packages are, a call handed to you rings on the desktop and the dialer places your own. Releases are on GitHub, as a .deb and a Flatpak.
Harbour Dental
- Overview
- Inbox
- Calls
- Contacts
Workspace
- District HQ
- Analytics
- Phone numbers
- +1 416 555 0142Asked to move a Thursday cleaning to Friday morning. Booked Friday at 9:30 AM.9:41 AM2m 22s
- +1 202 555 0171Called back to confirm Friday's appointment. Confirmed.9:05 AM1m 5s
- +1 647 555 0118Hung up before the greeting finished.26 Sep
A native Linux desktop client
Sign-in stays in your browser
The app never shows a password field. You sign in in your browser, which hands the result back through a districtai:// link, and your sign-in is kept in the desktop's keyring, or without one only until the app quits.
Held to the service's own answers
The repository carries responses recorded from the District AI service, and its tests decode every one with unknown fields refused. A field the server renames or adds fails the tests here rather than in the app.
Every package is attested
Each release is a .deb and a Flatpak with a signed attestation of the build, published only after the licensing of the call library's codecs was reviewed.
- Licence
- Apache-2.0
- Built with
- Rust, GTK 4, libadwaita
- Status
- Released
What is open source, and what is not
What is open source
This app, under Apache-2.0: you can read it, build it and change it. The District AI and Distronode names are Distronode's, and the app's icon is the Distronode mark, which the licence gives no permission to use.
The app reports no crashes: no crash-reporting library is among its dependencies, and its own code writes no log.
What is not
The District AI service the app talks to. Everything the app shows comes from that service, and using it needs a District AI account.
Without an account with us
Today the apps need a District AI account to sign in. We want them to work without an account with us too. We have not worked out what that looks like or whether it can work, and the answer depends on what people would use them with, so we are asking before we build anything.
Get involved
Issues and pull requests are welcome on GitHub. Report a vulnerability privately, as the security policy describes, and not in a public issue.
- Contributing guide
- CONTRIBUTING.md
- Security policy
- SECURITY.md
- Changelog
- CHANGELOG.md