Skip to content
Devlog

Changelog

What shipped, and when.

Every entry below corresponds to something that landed. No roadmap promises, no 'coming soon'.

  1. site

    A public site worth the product

    • New landing page with a live commit-to-log demo, plus Features, Integrations, Security, Docs, Changelog and Contact pages.
    • Privacy policy corrected: stored tokens are encrypted at rest, and it now says so.
    • The casual UI voice is labelled Casual, and two of its lines were softened.
  2. feature

    Ask your log, and reports worth sending

    • Ask: questions answered from your own record, with the entries it used.
    • Reports: a fortnight framed for management, executive or technical readers. Numbers from SQL; prose from the model, handed the numbers as facts.
    • Sending is a separate, deliberate step after the draft is on screen.
  3. improvement

    Branch-aware commit fetching

    • GitHub commits are fetched per branch, so work on a feature branch is no longer missed until it merges.
    • Database configuration gained a connection test that reports the server's own error message.
  4. security

    Operator functions locked down

    • Five operator-only database functions had remained callable by any holder of the anon key; they are now revoked from every public role and re-check the caller inside their own body.
    • A tenancy proof script attempts every cross-workspace read and write as a signed-in user.
  5. improvement

    The companion follows you

    • Mascot choice and on/off state moved from localStorage onto the account, so they follow you between machines.
    • Eight species to choose from, each a pair of pixel grids with shared 3D extrusion.
  6. feature

    Connectors, API keys, and time that means what it says

    • Generic source connectors: Jira, Linear, GitHub Issues, Google Calendar, Outlook Calendar, Sentry, Bitbucket, Azure DevOps, and Notion as a destination.
    • API keys and POST /api/ingest so any tool can push work in. Keys are hashed; retries are idempotent.
    • Microsoft Teams and custom webhook notifications alongside Slack and Discord.
    • Schedules store an IANA timezone. 22:00 means 22:00 where you are; a commit at 01:00 belongs to that day.
    • Stored tokens encrypted at rest with AES-256-GCM. Task links appear in the workspace report.
    • Bulk fill previews one day before running a range, and invitations go out by email.
  7. feature

    Workspaces

    • Organizations with owners, admins, managers and members; seat-sized plans with a shared credit pool.
    • Projects and tasks with a board, comments and an activity trail. A task key in a commit message links that day's log to that task exactly.
    • Manual task linking from Daily Work for the days that produce no commit.
  8. feature

    Billing and the public profile

    • Credit packs paid through Razorpay, or by UPI/invoice approved by an operator. Prices are read server-side; the browser never grants credits.
    • Public profiles at /u/handle with streaks, heatmap and rhythm — aggregates only — plus generated images for link unfurls and stories.
    • Commit activity mirrored as day counts so a daily committer's year no longer looks empty.
  9. feature

    GitLab, and the work with no commit

    • GitLab as a second code host, cloud or self-managed.
    • Manual activities: meetings, reviews, pairing, on-call, with optional hours that feed the day's total.
    • Repository rules to decide which repos count as work.
  10. feature

    The automation engine

    • Nightly schedules, a review-before-write flow, Slack and Discord notifications, and Google Sheets and SQL Server as destinations.
    • Every entry records where its hours figure came from: measured, typed, or estimated.
  11. release

    First commit

    • Sign in with GitHub, read the day's commits, summarise with the provider of your choice, write one row per day to Supabase.