Changelog

What shipped, and when.

A running list of the changes worth telling you about, in the words you'd use rather than ours. The runtime is open source, so if you want the commit behind any of these, it's on GitHub.

July 2026

  1. Droids stay signed in between video calls

    A droid joining the same recurring Google Meet used to arrive as a fresh anonymous guest every week. It now keeps its browser session between calls, so it turns up already signed in and gets admitted like any other regular attendee.

  2. Tasks that fire on things happening, not just on the clock

    A standing job can now be triggered by an event in a connected app — a new email, a file landing in Drive, a message in Teams, an item added to a list — instead of waking on a timer and checking. Less polling, and the droid reacts in the same minute rather than the next hour.

  3. It hangs up when everyone else has left

    If the last human drops off a call, the droid notices it's alone and leaves rather than sitting in an empty room. A small thing that was quietly costing people money.

  4. Scheduled tasks declare what they need

    A recurring job can now opt in to a filesystem or a desktop rather than every job getting both by default. Tasks that only need to read a table and send an email no longer spin up a machine to do it.

  5. A ceiling on how long a task may run

    Set a maximum runtime per task. A job that gets stuck on something unexpected stops and reports, instead of burning the afternoon on a retry loop nobody was watching.

  6. A straight answer when a meeting won't let it in

    Google Meet and Teams turn anonymous guests away when no signed-in host is present, and the join flow used to read that as a lobby and wait indefinitely. It now recognises the refusal and tells you the host needs to be in the call — rather than reporting a generic failure ten minutes later.

  7. Memory that knows when it has gone stale

    What a droid knows is now held as typed claims — facts, policies, decisions — each linked to what it was learned from. Delete the contact, file or table behind a claim and the claim is flagged rather than quietly repeated back to you six weeks later as though it were still true.

  8. Look before you leap

    A droid now has to check what it already knows, and what functions it already has, before it's allowed to start running code. It cuts down on the failure where an assistant confidently rebuilds something it did last week.

  9. Pause a standing job without deleting it

    Turn a recurring task off, leave it in place, turn it back on when the season or the project comes round again. Its history and memory survive the pause.

June 2026

  1. Fillers that sound like someone thinking, not stalling

    On calls, the fast brain now picks what it says while the slow brain works based on what's actually being discussed, acknowledges when it's taking a while rather than repeating a cheerful holding phrase, and stops reusing the same line twice in a conversation.

  2. More thinking where it matters

    Reasoning effort raised across the board, with the deliberate parts of a conversation pinned high. Slower on the hard turns, noticeably better on them too.

May 2026

  1. It can get through a CAPTCHA

    Browser work that hits a reCAPTCHA no longer dead-ends. Worth saying plainly: this is for portals and suppliers' systems your team already has an account for, not for getting into places you shouldn't be.

  2. Scheduled work runs on local installs

    Recurring tasks used to need the hosted scheduler. Local installs now run their own, so a droid on your own machine keeps its standing jobs.

  3. One gateway for every channel

    Email, Outlook, WhatsApp, Teams, SharePoint, Slack and Discord now come through a single gateway instead of a channel-by-channel patchwork. Adding a new channel stopped being a rewrite, which is why several arrived shortly after.

April 2026

  1. A one-line install

    One command clones the open runtime, walks you through your keys, and leaves you with a working droid on your own machine.

  2. Attachments ingest without anyone opening them

    Files arriving on email are parsed and turned into queryable tables in the background, streaming rather than loading whole, with the type of each column worked out on the way in. Big month-end spreadsheets stopped being a problem.

March 2026

  1. Office documents read natively

    Word, PowerPoint and the rest are converted properly rather than being guessed at from raw bytes.

  2. Answers the phone before it's finished waking up

    The fast brain now knows when the slow brain is still starting, so the first few seconds of a call sound like a person picking up rather than a line that hasn't connected.

February 2026

  1. A fast path for watching over its shoulder

    Guided computer use — where you're watching and correcting as it works — got its own low-latency route, so pointing at the wrong field and saying "not that one" lands while it still matters.

  2. It reviews what it learned when a session ends

    When a long working session finishes, a droid goes back over what it did and decides what's worth keeping as a reusable function or a piece of guidance. The second time you ask for the same thing, it's already a known job.

Most of this came from someone asking.

If a droid can't do something you need, that's usually the fastest route to it appearing here. There's also longer writing on why the architecture works the way it does over on the blog.