Skip to content
Archiedocscookbooknewssign in

    Release 1.54.0

    News ·

    Upgrade note: services now authenticate each other with TLS certificates from your own CA instead of shared tokens. Before upgrading a host whose services listen on anything but loopback (any host running agent containers), issue a certificate per service (archied, archie-gateway, archie-messaging, archie-state-store, archie-ui, each with its name as the DNS SAN and both server and client auth), add [tls] ca_file and cert_dir to config.toml, and remove every target_token, the *_TOKEN service variables and the --token/--*-token flags, including archie-ui’s -token and -token-file. A unit that still passes a removed flag fails to start. See config.example.toml.

    archied

    • Services authenticate each other with mutual TLS. Each process presents <cert_dir>/<service>.pem, peers must chain to ca_file, and a caller is identified by its certificate rather than by what it claims. Renewed certificates are picked up without a restart. Without [tls], services listen on and dial loopback only. The harness setup terminal requires [tls].
    • Every gRPC service caps the streams a connection holds, times out stalled handshakes, releases a dead client’s streams, and drains for at most 10 seconds on shutdown. Messaging exits when its listener fails instead of staying up without delivering.
    • The dashboard has user accounts. First run opens browser setup for the organisation, workspace and first administrator; people then sign in with a password, a passkey or your identity provider, and account administration lives under Access. The shared dashboard token is gone; reach the dashboard remotely through an HTTPS reverse proxy.
    • archied update install updates a host in one transaction: it verifies the release, stages every binary, pulls the agent image by digest and backs up the database, then restarts the services in order and rolls everything back if archied is not healthy for two minutes.
    • Each workflow runs as the identity it declares, checked on every attempt along with the identity that started it. A workflow that declares none is refused, a called workflow runs as its caller’s declared identity, and shipped workflows run as the instance root.
    • Test-run a workflow draft before saving it, with forge and push writes suppressed and recorded per step. The History tab lists a workflow’s revisions, diffs them as YAML and on the canvas, restores one into the editor, and shows which revision each run used.
    • Start a task from the dashboard. The dashboard home shows activity and setup, and a running task has a read-only Sandbox tab that follows its container.
    • The topbar’s Jump to is a command palette, settings lists open as accordions that wait for a new item to be saved, and history restores land as a draft applied from the save bar.
    • Labels, hints, alerts and empty states say what is wrong and what to do, without tutorial or marketing prose.
    • Org isolation is tighter: harness secrets, identity writes, principals, playbook dispatch and model selections in chat stay in the caller’s org, instance settings are written by the system org only, and creating a source or reloading a channel is authorized against the target.
    • Binding dispatch claims its capture and enqueues the task atomically, so a capture cannot start two runs, and the run-time workflow check sees the binding event’s signature and address.
    • Service-unhealthy alerts count their grace from the last report and also cover a service that went silent, and a restart no longer clears an alert still inside its grace. An invalid stored access policy raises an alert until it validates.
    • A failed cancel of a called workflow no longer leaves the caller running, retention spares captures still waiting to be dispatched, and EDA playbooks load and report at start instead of on first dispatch.
    • Chat model selection works again for provider models.

    archie-agent

    • Each run acts as its workflow’s declared identity.
    • A task snapshot carries only the model limits its aliases resolve to.
    • A build step’s “no changes” result comes from its writable stages and clears once a commit lands.
    • Test runs suppress forge and push writes and record what they would have done.
    • The default persona is a reporting-focused identity prompt, without the one-question limit in chat.