Skip to content
Archiedocscookbooknewssign in

    News

    1.55.0Latest

    archied

    • Personas are gone: the Personas settings page, the chat Personality selector and /personality. A selected persona never changed what the model was told; SOUL (Settings → SOUL) is the one place to set Archie’s identity and style. Stored persona settings are deleted on upgrade.
    • The shipped SOUL describes Archie as the assistant for an event-driven automation system rather than a coding assistant. A SOUL you have saved is kept as it is.

    1.54.3

    archied

    • Chat can help write a workflow: it reads your workflows and the step catalog, writes a definition, and checks it the same way saving does, fixing what the check reports. It does not save; paste the YAML it gives you into the editor’s YAML view and save there.

    1.54.2

    archied

    • Tool calls from Gemini models (Interactions API) receive their arguments intact. Any tool that takes arguments, such as dashboard_navigate in chat, failed with “invalid character ‘{’ after top-level value”.

    archie-agent

    • Agent steps on Gemini models (Interactions API) pass tools their arguments intact instead of failing to decode them.

    1.54.1

    archied

    • Update checks, archied update install and install.sh find releases at github.com/samcharles93/archie-releases, so a host can update again. A host on 1.54.0 or earlier still looks in the old place and has to be upgraded to 1.54.1 by hand once.

    1.54.0

    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.

    1.53.0

    archied

    • Every organisation’s data is its own. Chats, tasks, events, transitions, steps, tool calls, run statistics, event sources, event types, mappings, bindings and agent memory are read and written in the org that owns them, and a request can no longer write into another org. Rows written before orgs existed move to their owner’s org on upgrade.
    • An instance admin decides what each org may reach: the models it can use, and whether it may register providers under its own credentials. Org Settings gains a Models tab and instance Models gains Org access. The system org is never restricted; another org uses nothing until it is granted.
    • Models are addressed by alias. Aliases replace model roles, one resolver serves every purpose (agent steps, implement, PR review, MCP sampling, chat, embedding, transcription), and an unknown alias fails instead of falling back to a default. The step editor and the chat picker offer aliases, and a workflow naming one that does not exist is refused when saved.
    • Chat sessions belong to one org; a chat resolves its models in the caller’s org and is billed to it, and a task run from chat posts its outcome back to that chat.
    • Add a member by provider subject, or by email as a placeholder that the first sign-in the provider vouches for claims.
    • The workflow canvas authors parallel branches as lanes, adds a switch step that runs the case matching a reference, and edits a call’s interface. A step shows its role, its number and its run trace.
    • The workflows list shows each workflow’s running count and latest run result, the canvas reveals its data-edge handles on hover, and restoring a version asks for confirmation.
    • Store packages can auto-update: a package given the policy is moved to the catalogue’s newest digest by a State Store ticker. An update asking for more authority than was accepted waits as a pending update with the running version untouched; approving it accepts the new authority, and a rollback restores the previous version with the authority accepted against it.
    • Model provider keys never enter an agent container: the runtime reaches its providers through the egress proxy, which holds the keys. A task’s own credential can no longer replace the workflow definition its run is pinned to, and a package workflow’s triggers, tools and forge calls are bounded by the authority accepted for the package.
    • The dashboard warns when it is reachable from off-host over plain HTTP, and the wildcard listen address counts as off-host rather than loopback. Instance health, logs, config and identities, the setup checklist and the skill catalogue are system-org only, and API requests are refused until the access chain has loaded.
    • /approve reaches Telegram; the router served it but nothing published it.
    • A worktree a killed container left root-owned is taken back by the daemon, and a PR review’s benchmark runner works again on configured models and public PRs.
    • An unserved /api path returns 404 instead of the dashboard page, and an input group’s select no longer loses clicks to its addon.

    archie-agent

    • The runtime reaches model providers through the egress proxy, so provider keys stay out of the container.
    • Agent steps resolve model aliases and their own org’s models and credentials, failing on an unknown alias instead of falling back.
    • A switch step runs the case matching its reference.
    • A call waiting on another step is reconciled from durable steps, so it resumes after a daemon restart rather than stranding.

    1.52.0

    archied

    • The harness page’s setup terminal opens a real session: it starts an ephemeral container from a Kit profile, runs the CLI’s own login and captures the OAuth tokens at the provider’s token endpoint. Point the dashboard at the daemon with [services.harness].target and a HARNESS_TOKEN and it stops answering 503; the terminal is created at your browser’s size. Takeover of a live task is not in this release.
    • A credential’s token endpoint is refused when the run is not granted that service, instead of proxy-ing the provider’s real tokens into the container.
    • Settings → Profiles, Credential bindings and Playbooks are editable from the dashboard, and curator definitions can be changed and applied without a restart.
    • Settings say whether each one applies live or needs a restart, show what is consuming resources, and report whether an apply landed.
    • Status shows each service’s dependency checks, the agent workers and the broker.
    • The Logs page reads recent logs from every service, not just the daemon.
    • Captures and webhook sources are scoped to the org that owns them: the list, retention and delivery authorization all act in the right org, and a workflow definition resolves in its own org.
    • Chat settings are attributed to the signed-in user, and Settings → Tokens explains when a personal token cannot be created.
    • A channel enabled after Archie started works immediately; a channel that fails on its own recovers; a failed channel is no longer reported as enabled, and stored channel settings no longer save duplicate or unnormalized values.
    • The task table sorts, the command palette no longer scrolls sideways or loses its highlight, unknown routes render a not-found page, and configuration reload failures are shown instead of passing silently.
    • A scheduled job whose payload names a dangerous command is refused.
    • A disabled model provider is never served from the ambient API key.
    • generate_video is backed by ai-sdk’s MiniMax video provider.
    • A dashboard token is no longer written to the startup log.

    archie-agent

    • workflow.call: a call is keyed on its declared step path, its key is freed once the callee reaches a terminal state, and a caller waiting on a callee releases its capacity instead of holding it.
    • command.run honours step retry and on_failure.
    • A value passed between steps keeps its declared type, and optional result booleans are enforced only when the workflow declares them.
    • Capture tools have their results checked against the declared schema.
    • A single-cycle run waits for its in-flight tasks before exiting, and identity tasks inherit live settings.
    • Kit containers run Docker’s init as PID 1, so orphaned processes are reaped instead of accumulating inside a long task.

    1.51.1

    archied

    • Chat with OpenAI’s gpt-6 models (gpt-6-luna and the rest) works with tools; a turn failed with “Function tools with reasoning_effort are not supported”.

    1.51.0

    archied

    • A secret engine enabled after Archie started (Bitwarden, for example) now supplies its keys straight away; providers that depended on it no longer stay disabled until a restart.
    • The dashboard chat has a microphone button: record a voice message and it is transcribed like a Telegram voice note. It shows only when a transcription model role is set under Settings → Models.
    • A file Archie sends in the dashboard chat is a download link for an hour, instead of a note that it can’t be delivered.
    • Typing /model or /personality on its own in the dashboard chat offers the choices as buttons.

    1.50.1

    archied

    • When an update is rolled back, the log names the health check that failed instead of only “unhealthy”.

    Page 1 of 10