Skip to content

Arky changelog

Every release, newest first. Back to Arky or read the whole Forge Log.

  1. Registry graph upgrades

    v2026.10.01

    • Filter the graph by entity type
    • Layout runs off the main thread, so large estates stay responsive
    • Labels no longer collide; structured attributes in the side drawer

    The registry explorer now handles much larger estates: layout moved to a Web Worker, labels are placed in screen space so they never overlap, and the drawer shows each entity's structured attributes instead of raw text.

  2. Groups, shared keys, moderation and redaction

    v2026.09.18

    • Groups with per-connector permissions decide what each person's assistant can reach
    • Shared keys for every connector, with one-call invitations
    • Inbound moderation with pause-after-strikes, and secret redaction on every result

    Access is now group-shaped: an admin grants a group a connector and everyone in it gets that reach. Secrets are scrubbed from every tool result and every response before anyone sees them.

  3. Workspace diff review

    v2026.09.14

    • Workspace diffs render inline in chat
    • A dedicated review surface per workspace task
    • Reviewer comments flow back to the agent

    Code-workspace changes are reviewable before they become a pull request — read the diff in chat or on the review page, leave comments, and the agent picks them up.

  4. Code workspaces

    v2026.09.10

    • Clone, build and test a repository in a credential-less sandbox
    • Run the app on your own machine after you say yes
    • Branch-plus-pull-request is the only outward write; idle workspaces stop on their own

    Arky can now work on code: it clones the repository into a sandbox with no credentials, builds and tests it, brings up the services it needs, and proposes the fix as a pull request behind a confirmation card.

  5. Unified web app and approvals inbox

    v2026.09.03

    • One web app for chat, cards and admin
    • Blocking confirmation cards for every write
    • A separate approver inbox for production changes

    The first unified surface: chat, confirmation cards and the approvals inbox in one place, with a second approver required on every production change.