Glyphi TeamsTeams

What shipped,and when.

Five releases so far, newest first: the team window, the manager with per-member caps and an encrypted chat, its own application, and the Rust build coming at 0.3.0.

  1. 0.2.4

    15 Nov 2026

    The proxy counts messages too

    • The counting proxy reaches any endpoint: a known name, an explicit upstream, providers.json, or the host in the path.
    • A member whose tool reports no tokens still appears: the proxy counts the real text and the request's messages, and marks the row as an estimate.
    • Streamed answers are read for usage, so tokens measured mid-stream are no longer lost.
    • Update failures now name their cause instead of blaming the connection.
  2. 0.2.3

    14 Nov 2026

    The counting proxy, in a company build

    • The Rust counting proxy ships in the installer and starts with the manager, so a member whose tool writes nothing readable still reports what went through the proxy.
    • The manager reads the proxy totals as one more source beside the local history, with today's input, output and a line per provider.
    • The proxy listens on loopback only, keeps no credentials and stores one line per request in the app's data folder.
  3. 0.3.0

    plannedPlanned

    The Rust build

    • Glyphi Teams moves to the same Rust shell as Glyphi, and ships the local counting proxy with it.
    • The Electron build keeps shipping updates until then; the two switch together.
  4. 0.2.2

    13 Nov 2026

    Its own application

    • A separate installer, a separate Glyphi Teams.exe, its own install folder and its own %APPDATA%\Glyphi Teams data folder, so it sits beside Glyphi without touching its history, preferences or sign-in.
    • The Windows installer carries a self-signed signature, so Windows still warns until a certificate authority replaces that key; macOS ships unsigned on purpose.
    • Freebuff usage says nothing is measured, instead of drawing a zero, when neither the local database nor a cloud token is available.
  5. 0.2.1

    13 Nov 2026

    Signing step and the cloud quota fallback

    • A signing step for the Windows installers and a detached GPG signature for the Linux packages.
    • When the local usage database stops being written, the manager asks the Freebuff cloud for today's quota instead of reading zero.
  6. 0.2.0

    13 Nov 2026

    The manager window

    • Per-member daily token caps, set by the owner, with an over-cap flag on the board.
    • Encrypted team chat: AES-256-GCM with a key derived from the invite code by PBKDF2-SHA256; the API stores ciphertext and an IV and holds no key.
    • The invite code as a QR image with the app mark in the centre, at error-correction level H.
    • Backend migration 0003 adds the member cap and the message table, all SECURITY DEFINER behind the service role.
  7. 0.1.0

    13 Nov 2026

    First public release

    • A Teams window inside the app: create a team, hand out one invite code, see every member's daily token and cost totals.
    • Sharing is per member and per team, and off until each member turns it on; turning it off deletes the rows already shared.
    • Only day totals are uploaded — a date, a token count, an estimated cost and the split per tool. Never prompts, completions, file paths or project names.
    • MIT licensed, with the backend deployable in your own Supabase project.

Each release is published with its installer on GitHub. The Windows installer is self-signed, so Windows still warns; macOS ships unsigned on purpose.