Skip to content

Releases

Kai mobile 0.2.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 16:37

Kai mobile 0.2.0 browses all your lmgw Chat threads, takes a voice call into any of them and speaks plain words in its settings. It needs lmgw 0.6.0.

  • Threads. A Threads page, opened from the conversation's top bar, lists your folders with their threads in lmgw's order, plus the loose, temporary and archived ones. Open a thread to read and write in it as in the Kai conversation. A thread's menu (its button or a long press) pins, archives, moves, renames or deletes it; deleting asks first. New thread works in a folder that names a model, and the Kai thread opens as the Kai conversation.
  • Search. From two characters, across active, archived or all threads and optionally one folder, with the matches in bold and More results; a hit opens its thread at the message.
  • Fold and unfold. On a narrow screen the list and the thread are two pages; on a wide one they sit side by side. What you typed, the search and its results stay across a fold.
  • Voice in any thread. Talk beside an opened thread's field starts a call there, or moves the running call at its next quiet point; there is still one call at a time. Each thread says where voice is, with Back to Kai or a way back to the thread that has it. The voice screen, the overlay and the call's notification name the thread (the notification not on a locked screen). Temporary threads have no Talk.
  • Settings in plain words. Every setting has a label, a line that explains it, its unit and a fitting control; everyday voice choices come first, waits and retries sit under Advanced, and the Connection page is now Advanced connection. Errors name a setting by its page and label, never by its key.
  • Conversation. A new page offers Shared with your other Kai apps (the Kai folder) or Only on this phone, named "Kai " to start with, so two phones keep separate conversations.
  • Your phone's name on lmgw. When pairing, the app gives lmgw the phone's device name for the Devices card.
  • GPU states. A turn refused because the GPU is busy says so in the app's words (try again shortly), with lmgw's message beside it. The GPU hold reads "Local models are paused (GPU hold)", and a call's stage that a fallback model answers for names that model.
  • Kai's logo as the launcher icon, for themed icons and in the status bar.

Upgrading: Kai mobile 0.2.0 needs lmgw 0.6.0, with its device listener on and a Chat model; voice needs speech-to-text and text-to-speech models. Android 12 (API 31) or later, arm64, as before. Install the APK from this release over the old one; the pairing stays.

Not built yet: images and attachments in messages, a spoken yes or no for approvals, a local message cache, Markdown tables, phone tools, screen context for the assistant, the lock screen as a place to talk, and automatic certificate renewal. There is no iOS app.

Kai mobile 0.1.1

Choose a tag to compare

@github-actions github-actions released this 19 Oct 07:33

Kai mobile's first release. (The v0.1.0 tag was never released: its build failed in the APK check, which 0.1.1 fixes; the app is the same.)

Kai mobile is an Android client of lmgw: voice first, and able to be the phone's digital assistant. This is its first release, an alpha.

  • Pairing over lmgw's device link. Scan the QR code on lmgw's Devices card, tap a pairing link or paste it. Kai shows what it is about to pair with, makes a non-exportable P-256 key in the Android Keystore, enrols it with the one-time token and keeps a certificate. You confirm a short code on lmgw's Devices card. It tries the link's URLs (LAN, VPN) in parallel and follows the one that answers.
  • Text conversations. The ongoing Kai conversation of your lmgw's Chat, shared with Kai on the desktop: Markdown replies, tool notices under the answer, New conversation, and a notice when a tool of a device is not granted or offline.
  • Voice over WebRTC calls. Automatic turn-taking, push-to-talk, mute, stopping Kai by speaking, captions, and a ring that follows the voice. If another device holds the conversation's call, Take over asks first. Echo cancelling (software, or half duplex), Bluetooth and headset routing, headset buttons and audio focus are handled: another app's audio pauses the call instead of ending it.
  • Kai as your digital assistant. Set Kai as the assistant in Android's settings (a card in the app walks through it): its overlay opens from the assistant gesture, a quick settings tile or a launcher shortcut. Closing it before you spoke ends the call; after a turn the call goes on, and Expand moves it into the app.
  • Tool notices and approvals. A tool call that needs a decision shows one card on the overlay, the voice screen and in the conversation, and as a notification with Approve and Decline. Approving needs an unlocked phone; declining works locked.
  • Notifications through the Chat feed. A foreground service holds the feed open, so replies and approvals reach you with the app closed, with no push provider in between. Notifications show no content on the lock screen.
  • Two-screen layouts, TalkBack and font-scale support.

Requirements:

  • lmgw 0.5.0 or later, with its device listener on and a Chat model; voice needs speech-to-text and text-to-speech models.
  • Android 12 (API 31) or later, arm64.
  • A network path to lmgw: the same LAN, or a VPN such as WireGuard. Calls use UDP and lmgw has no STUN or TURN, so the phone must reach lmgw directly.

Install: download the APK from this release and sideload it (allow installs from this source). Updating is installing the next APK over it; there is no in-app updater yet.

Known gaps: images and attachments in messages, a spoken yes or no for approvals (use the card or the notification), a thread browser and search, a local message cache (the conversation is read again at start), Markdown tables, phone tools (alarms, calendar and the like), screen context for the assistant, the lock screen as a place to talk, and automatic certificate renewal (you pair again when it lapses, after about a year). Whether your phone maker lets the side button or power key reach the assistant varies. There is no iOS app.