156 KiB
Changelog
The release stream. One version covers whatever changed; a release's per-component sections are labelled beneath its heading.
[Unreleased]
archied
- Releases are signed. A release is an OCI artifact whose statement is signed with the release key; updates and
install.shrefuse a release the key did not sign, a zip that is not the one signed, and a channel moved back to an older release. Releases now come fromgit.catlow.cloud/sam/archie, so a host on 1.55.0 or earlier finds this release only by running the new installer once:curl -fsSL https://offloaded.dev/install.sh | bash. - Where releases and the extension catalogue come from is a setting: an OCI repository and the key it signs with, in the update settings and the extension settings, or
[distribution]inconfig.tomlfor a new instance.archied release keygenandarchied release publishmake a key and publish signed releases to your own registry. - Chat saves the workflow draft it writes with
workflow_draftinstead of handing over YAML to paste: the draft lands in the workflow editor for review, attributed to the signed-in account.
[1.55.0] - 2026-10-16
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] - 2026-10-16
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] - 2026-10-16
archied
- Tool calls from Gemini models (Interactions API) receive their arguments intact. Any tool that takes arguments, such as
dashboard_navigatein 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] - 2026-10-16
archied
- Update checks,
archied update installandinstall.shfind releases atgithub.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] - 2026-10-16
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 toca_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 installupdates 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] - 2026-10-11
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.
/approvereaches 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
/apipath 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] - 2026-10-09
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].targetand aHARNESS_TOKENand 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_videois 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.runhonours step retry andon_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] - 2026-10-08
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] - 2026-10-08
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
transcriptionmodel 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
/modelor/personalityon its own in the dashboard chat offers the choices as buttons.
[1.50.1] - 2026-10-08
archied
- When an update is rolled back, the log names the health check that failed instead of only "unhealthy".
[1.50.0] - 2026-10-08
archied
- Tools that need your approval ask for it again, and Archie can ask you a question or offer choices mid-reply. Since the services were split these never reached Telegram or the dashboard: approval-gated tools failed and questions were never asked.
- The dashboard chat shows approvals as Approve / Always this session / Deny, choices as buttons, and questions with a reply field.
/updatein the dashboard chat lists what's available with Install and Not now.- Settings → Status → Versions installs the update it shows; its Install button sent an empty request.
[1.49.4] - 2026-10-07
archied
- Settings → Status and Settings → Extensions are split into tabs instead of one long page; the Versions table's status column ends at the card's edge.
- Tools & MCP has one "Add MCP server" button; the transport is chosen in the form, and an unnamed new server is not an unsaved change.
- Settings → Repositories shows the add field when no repositories are configured, instead of a blank page.
- The unsaved-changes bar always rests at the bottom of the window.
[1.49.3] - 2026-10-07
archied
- Settings → Status → Versions shows the Gateway as "Update available" with an Install button when a newer release exists; it read "Unknown" with no way to install. The Runtime row stays "Unknown" until an agent task has run.
- The release channel buttons sit at the Updates card's right edge instead of mid-row.
[1.49.2] - 2026-10-07
archied
- Carries the 1.49.0 and 1.49.1 changes, whose builds were never published. The update check reads GitHub releases directly and still offers only releases with a verifiable linux-amd64 zip.
[1.49.1] - 2026-10-07
archied
- When the dashboard session expires, the page returns to the sign-in screen instead of showing errors on every page until a manual refresh.
[1.49.0] - 2026-10-07
archied
- Extensions that declare no egress hosts (vault, email, gitea) reach the network again; only packages that declare their hosts are confined to them. The Accept dialog shows "network: unrestricted" for the rest.
- The update check finds releases itself, and reuses a found release for ten minutes so repeated checks stay under GitHub's rate limit.
[1.48.1] - 2026-10-07
archied
- Settings → Status → Updates now chooses only the release channel (stable, prereleases, or a pinned version). Update checks and installs always run the
archie-update-*scripts installed beside the binaries; the dashboard can no longer set the command that runs.
[1.48.0] - 2026-10-07
archied
- Settings → Status → Updates edits the update check and install commands. They default to the
archie-update-*scripts installed beside the binaries, so a zip install shows Install on the Versions card with nothing configured. Theupdate_check_commandandupdate_install_commandkeys under[chat.telegram]are no longer read; remove them fromconfig.toml. archie-update-installrun from a shell now reads~/.config/archie/env, so the pre-update backup of the bundled database no longer fails withno password supplied. Run it with--autoto install the newest release.
[1.47.3] - 2026-10-07
archied
- Settings → Extensions: Accept in the authority review now accepts the extension, and Remove removes it. Both previously closed the dialog without doing anything.
[1.47.2] - 2026-10-06
archied
- Events → Inspector now lists your capture sources with their real URLs and a New source button, replacing the
/webhooks/capture/<source>placeholder. Sources no longer sit on the Bindings tab.
[1.47.1] - 2026-10-06
archied
- The bundled PostgreSQL has no network and publishes no port: the services reach it through its Unix socket under
~/.local/share/archie/postgres, so it no longer collides with another PostgreSQL on 5432. Leaving the database question blank inarchied setupselects it. - The installer does not start the services when the bundled PostgreSQL fails to start; it names the command to read its logs.
- On hosts that restrict unprivileged user namespaces (Ubuntu 23.10+), the installer prints an AppArmor profile allowing them for the Archie binaries only.
[1.47.0] - 2026-10-06
archied
- Install with one command:
curl -fsSL https://raw.githubusercontent.com/samcharles93/archie-core/main/install.sh | bashdownloads this release, verifies its checksum and runsarchied setup.--from-sourcebuilds a checkout instead. archied setupasks for the PostgreSQL URL. Left blank, it uses the bundled Compose database with a generated password stored in~/.config/archie/envasPGPASSWORD, not inconfig.toml.- The bundled PostgreSQL listens on 127.0.0.1 only. A database created before this release keeps its old
archiepassword; enter its URL at setup or recreate the volume. - The release zip carries
docker-compose.yml. - Extensions need unprivileged user namespaces, which Ubuntu 23.10 and later restrict. Allow them for the Archie binaries with an AppArmor profile; from the next release the installer prints it. Do not disable the restriction system-wide.
- fix(app): assign the temp-file close result on the error path
- fix(webhook): set a ReadHeaderTimeout on the forge webhook receivers
- fix(forge): refuse a review line number that does not fit an int
- fix(storepkg): mask the tar mode to the permission bits before narrowing
- fix(webui): navigate the Events chain once, not twice
- feat(tools): fail the gate when docs cite a path that no longer exists
- fix(webhookguard): verify uppercase-hex HMAC signatures
- fix(configuration): make bot_user required, defaulted, and named
- feat(workflow): add the command.run step type
- fix(controlplane): an absent MCP server field inherits the file value
- fix(build): restore the go fix fixpoint, and give the formatter one owner
- fix(archied): restore contextcheck directives and drop unused adapter
- feat(secretengine): serve secret engines as go-plugin extensions
- refactor(statestore): own package for the State Store service; access reset moves to archie-state-store
- refactor(archied): gateway owns model work; daemon drops chat runtime, tools, memory and curators
- refactor(archiegateway): own package for the Gateway service
- fix(services): services wait for peers instead of exiting; restarted broker keeps its endpoint
- refactor(archieplaybooks): fold archie-playbooks into archied playbooks lint|serve
- refactor(agentrun): agent stage contract moves to the domain layer
- refactor(agentexec): model loop moves to agentexec/modelloop
- fix(configuration): bindings encryption keys must use the env engine
- feat(storepkg): fetch packages from any registry, plain HTTP on loopback only
- feat(webui): install, accept and enable extensions from the dashboard
- feat(presence): every service re-stamps a presence record in the State Store
- refactor(plugin): delete Yaegi daemon plugins and plugin_dir
- refactor(module): the log action is built in; delete the module loader and reconciler
- refactor(skill): delete Yaegi skill scripts and the run_go_script tool
- refactor(examples): the firewall workflow moves to archipelago
- feat(presence): services card on the status page and archied status
- feat(archiemessaging): verify update reports against archied's presence and restore release announcements
- fix(configuration): an overlay stands in for a missing config file; dev overlay is complete
- feat(access): edit org, workspace and object policies from the dashboard; refuse owner lockout
- feat(access): instance network rules at the capture receiver; policies reload without a restart
- feat(staterpc): attribute State Store calls to the calling service; policy audit records it
- feat(controlplane): playbooks and agent profiles install from packages; the daemon reads eda-playbooks live
- feat(forgeext): forge surface served by extensions; forge.type names the installed package
- refactor(forge): github and gitea leave core; webhooks parse in the forge extension
- feat(staterpc): the State Store derives org and actor from the principal archie-ui forwards
- feat(channelext): chat channels served by extensions; messaging runs the enabled ones
- refactor(channels): webhook and email run only as extensions; their channel settings go
- feat(skills): skill packages project into a skills resource the gateway reads live
- fix(gatewayrpc): sender_id and rate_limited cross the chat wire
- fix(controlplane): change history names kinds and reads only the caller's org
- feat(contracts)!: requests no longer name their org; the State Store derives it from the caller
- feat(identity): personal API tokens, created and revoked from the dashboard, act as their owner
- fix(archieui): a sign-in provider outage is a health issue, not a startup failure
- feat(staterpc): one run credential per task, kept in the State Store, authorizes its store calls and its push
- fix(forgerpc): forge calls need the run credential and reach only the run's own repository
- feat(controlplane): identity credential grants edited from the dashboard and applied live
- feat(daemon): a workflow that names an identity runs as it; the dispatcher needs run on the workflow
- feat(staterpc): every run start is audited by the State Store, or the run credential is withdrawn
- refactor(forgerpc): identity RPC subjects are keyed by identity ID
- fix(nats): containers log in with their run credential and reach only their task's subjects
- feat(egress): the run credential is the proxy login; Kit secrets resolve per request from live grants
- fix(webui): bind the container runtime document's keys, drop the blank Advanced page
- fix(webui): drop the repository review switch the server no longer accepts
- feat(controlplane): serve the step vocabulary in the workflow-definitions schema; the editor checks step types against it
- fix(ui): drop the topbar nav's edge fade that clipped the first item
- refactor(workflow): delete the bootstrap smoke-test workflow and its intake kind
- feat(workflow): step ids, {{ }} references to earlier results, agent.run result schemas, workflow.finish and on_failure
- feat(workflow): repository step types; implement and tdd ship as YAML in general steps
- feat(workflow): when conditions, handoff, human approval and forge steps; feasibility and triage ship as YAML
- feat(workflow): retries, parallel branches, review steps; every shipped workflow is YAML and the per-workflow step types are gone
- feat(ui): workflow canvas renders each definition as a step graph with data edges, parallel branches and conditions
- feat(ui): the workflow canvas watches a run live: each step shows its state, duration and error, and the view follows the step in progress
- feat(controlplane): serve each step type's settings schema; the workflow editor checks settings before save
- feat(ui): build workflows on the canvas: step palette, schema-driven settings forms, references to earlier results, reorder and remove
- feat(ui): the canvas Start node lists what starts the workflow: issue routes, event bindings, playbooks and other workflows
- feat(ui): canvas authoring by right-click menu and + insertion points; steps edit in a slide-in panel and show what they do
- fix(ui): workflow page header is one tab row with save and a more menu; drop the ID field, step list, version footer and the meaningless origin pill
- feat(ui): drive workflows from the canvas: run a workflow, act on the watched run, edit workflow settings from the Start node; the canvas fills the viewport
- feat(ui): inspect workflow step runs from canvas
- feat(workflow): resume a parked run from a chosen step
- feat(ui): bind an event to a workflow from its Start node
- fix(ui): reveal signing secret in canvas source creation
- feat(ui): select review gate findings before approval
- fix(ui): load task debug reliably and copy JSON output
- fix(postgres): queue a review that arrives during a remediation
- fix(ui): keep JSON copy inline on hover
- fix(webui): stop returning database_url from /api/config
- refactor(config): drop unused dispatch state labels
- feat(gateway): serve the dashboard skills and curators over ChatService
- refactor(archieui): leave channel reload unserved by the gateway
- feat(releaseupdate): install from release artifacts with journaled rollback, topology check and channels
- feat(gateway): load SOUL into the chat prompt per turn
- refactor(config): drop the unwired artifact sender and [artifacts] config
- feat(messaging): serve MessagingService.Deliver and deliver chat schedules through it
- refactor(gateway)!: drop budget_key with the webhook chat channel
- refactor(configuration): delete the dead runtime config overlay
- fix(daemon): record terminal non-dispatch outcomes so a capture is evaluated once
- fix(daemon): refuse a disabled workflow on every start path
- fix(workflow): validate workflow.call inside parallel branches
- fix(workflow): validate handoff and approve targets at save
- feat(taskactions): rejecting a pr_open task closes its pull request
- feat(eda): link binding dispatches to the captures and tasks they started
- feat(eda): record every terminal binding outcome and flag failing bindings
- feat(workflow): record parallel branch steps as their own steps
- feat(workflow): record steps skipped by when as skipped
- feat(webui): page and filter the task list on the server
- fix(webui): admit dashboard work requests through the State Store and honour the workflow's repository mode
- fix(ui): restoring shipped workflows keeps custom ones
- refactor(org): rename the default org to org-sys
- fix(postgres): collect inline comments on a review queued behind a running remediation
- fix(daemon): webhook forge intake does not poll for issues
- refactor(archied): drop the unreachable multi-identity webhook skip; validation refuses it
- feat(access): the dashboard operator is a person owning org-sys
- fix(workflow): refuse undeclared inputs and result fields at save
- fix(ui): offer resume only where the server accepts it
- feat(daemon): the timeline names and links the binding and capture that started a task
- feat(eda): pause and resume a binding; resuming goes back through approval
- feat(org): org, workspace and membership API
- fix(webui): the org-sys owner is the instance owner
- fix(webui): member changes need the admin grant and owner changes an owner
- feat(daemon): withdrawing an issue declines its queued or running work
- feat(workflow): later steps read a waited workflow.call's outputs as its result
- feat(workflow): record each failed attempt of a retried step
- feat(daemon): record an approving review on the task's timeline
- feat(workflow): each remediation round names its number, cap and the review it answers
- fix(ui): show step retries as archie's record, not the agent's report
- feat(webui): run details show inputs, outputs and workflow.call links both ways
- feat(webui): page through task logs
- feat(eda): name and delete capture sources; an armed binding blocks the delete
- feat(ui): edit retry backoff and needs on the canvas
- fix(controlplane): report watch outages and align live/restart kind labels
- feat(taskactions): merge pull request action from the task
- fix(daemon): withdraw only issues the same dispatch rule found eligible and then lost
- feat(org): instance admins manage every org
- feat(ui): org area with members, agents, workspaces, access and tokens
- fix(ui): trim filler prose and expose appearance in settings nav
- fix(archiegateway,agentexec,agentworker): rely on ai-sdk reasoning token selection
- feat(ui): org switcher and new org for instance admins
- fix(extension): confine each extension's network to its accepted egress hosts
- fix(captureintake): unwrap form-encoded webhook payloads
- fix(captureintake): decode any form-encoded webhook body to JSON
- fix(modelloop): feed the cached model catalog to the runtime so reasoning models get the right token parameter
- fix(webui): list services with the State Store marked down when it is unreachable
- fix(release): push the release commit and its tag atomically
- fix(eda): dispatch each webhook delivery once, however often the sender retries it
- fix(eda): name a source's delivery header in the dashboard instead of a built-in sender list
- fix(modelloop): mark reasoning models from the carried model limits, in the gateway and the agent worker
- feat(telegram): /stop stops the chat agent, else the tasks it created, or one task; delete the dead approval actions
- feat(storepkg): install packages from a signed default catalogue, listed on the Extensions page
- feat(setup): one guided flow; ask for PostgreSQL and generate the bundled database's password
- fix(setup): keep the generated database password out of config.toml
- feat(install): install from a verified release with curl | bash; ship docker-compose.yml in the release
archie-agent
- fix(forge): refuse a review line number that does not fit an int
- fix(webhookguard): verify uppercase-hex HMAC signatures
- feat(workflow): add the command.run step type
- feat(secretengine): serve secret engines as go-plugin extensions
- refactor(statestore): own package for the State Store service; access reset moves to archie-state-store
- fix(services): services wait for peers instead of exiting; restarted broker keeps its endpoint
- refactor(agentrun): agent stage contract moves to the domain layer
- refactor(agentexec): model loop moves to agentexec/modelloop
- fix(configuration): bindings encryption keys must use the env engine
- feat(presence): every service re-stamps a presence record in the State Store
- refactor(plugin): delete Yaegi daemon plugins and plugin_dir
- refactor(module): the log action is built in; delete the module loader and reconciler
- refactor(skill): delete Yaegi skill scripts and the run_go_script tool
- feat(access): edit org, workspace and object policies from the dashboard; refuse owner lockout
- feat(access): instance network rules at the capture receiver; policies reload without a restart
- feat(staterpc): attribute State Store calls to the calling service; policy audit records it
- feat(controlplane): playbooks and agent profiles install from packages; the daemon reads eda-playbooks live
- feat(forgeext): forge surface served by extensions; forge.type names the installed package
- refactor(forge): github and gitea leave core; webhooks parse in the forge extension
- feat(staterpc): the State Store derives org and actor from the principal archie-ui forwards
- feat(channelext): chat channels served by extensions; messaging runs the enabled ones
- refactor(channels): webhook and email run only as extensions; their channel settings go
- feat(skills): skill packages project into a skills resource the gateway reads live
- fix(controlplane): change history names kinds and reads only the caller's org
- feat(contracts)!: requests no longer name their org; the State Store derives it from the caller
- feat(identity): personal API tokens, created and revoked from the dashboard, act as their owner
- fix(archieui): a sign-in provider outage is a health issue, not a startup failure
- feat(staterpc): one run credential per task, kept in the State Store, authorizes its store calls and its push
- fix(forgerpc): forge calls need the run credential and reach only the run's own repository
- feat(daemon): a workflow that names an identity runs as it; the dispatcher needs run on the workflow
- feat(staterpc): every run start is audited by the State Store, or the run credential is withdrawn
- refactor(forgerpc): identity RPC subjects are keyed by identity ID
- fix(nats): containers log in with their run credential and reach only their task's subjects
- feat(egress): the run credential is the proxy login; Kit secrets resolve per request from live grants
- feat(controlplane): serve the step vocabulary in the workflow-definitions schema; the editor checks step types against it
- refactor(workflow): delete the bootstrap smoke-test workflow and its intake kind
- feat(workflow): step ids, {{ }} references to earlier results, agent.run result schemas, workflow.finish and on_failure
- feat(workflow): repository step types; implement and tdd ship as YAML in general steps
- feat(workflow): when conditions, handoff, human approval and forge steps; feasibility and triage ship as YAML
- feat(workflow): retries, parallel branches, review steps; every shipped workflow is YAML and the per-workflow step types are gone
- feat(controlplane): serve each step type's settings schema; the workflow editor checks settings before save
- feat(ui): the canvas Start node lists what starts the workflow: issue routes, event bindings, playbooks and other workflows
- feat(ui): inspect workflow step runs from canvas
- feat(workflow): resume a parked run from a chosen step
- fix(postgres): queue a review that arrives during a remediation
- refactor(config): drop unused dispatch state labels
- refactor(config): drop the unwired artifact sender and [artifacts] config
- feat(messaging): serve MessagingService.Deliver and deliver chat schedules through it
- refactor(gateway)!: drop budget_key with the webhook chat channel
- fix(daemon): record terminal non-dispatch outcomes so a capture is evaluated once
- fix(workflow): validate workflow.call inside parallel branches
- fix(workflow): validate handoff and approve targets at save
- feat(taskactions): rejecting a pr_open task closes its pull request
- feat(eda): link binding dispatches to the captures and tasks they started
- feat(workflow): record parallel branch steps as their own steps
- feat(workflow): record steps skipped by when as skipped
- feat(webui): page and filter the task list on the server
- refactor(org): rename the default org to org-sys
- fix(postgres): collect inline comments on a review queued behind a running remediation
- feat(access): the dashboard operator is a person owning org-sys
- fix(workflow): refuse undeclared inputs and result fields at save
- feat(daemon): the timeline names and links the binding and capture that started a task
- feat(eda): pause and resume a binding; resuming goes back through approval
- feat(org): org, workspace and membership API
- feat(daemon): withdrawing an issue declines its queued or running work
- feat(workflow): later steps read a waited workflow.call's outputs as its result
- feat(workflow): record each failed attempt of a retried step
- feat(daemon): record an approving review on the task's timeline
- feat(workflow): each remediation round names its number, cap and the review it answers
- feat(webui): run details show inputs, outputs and workflow.call links both ways
- feat(webui): page through task logs
- feat(eda): name and delete capture sources; an armed binding blocks the delete
- feat(taskactions): merge pull request action from the task
- feat(org): instance admins manage every org
- fix(archiegateway,agentexec,agentworker): rely on ai-sdk reasoning token selection
- fix(extension): confine each extension's network to its accepted egress hosts
- fix(modelloop): feed the cached model catalog to the runtime so reasoning models get the right token parameter
- fix(eda): dispatch each webhook delivery once, however often the sender retries it
- fix(eda): name a source's delivery header in the dashboard instead of a built-in sender list
- fix(modelloop): mark reasoning models from the carried model limits, in the gateway and the agent worker
- feat(telegram): /stop stops the chat agent, else the tasks it created, or one task; delete the dead approval actions
- feat(storepkg): install packages from a signed default catalogue, listed on the Extensions page
[1.46.0] - 2026-10-02
archied
- feat(workflow): declared workflow outputs for wait:true callers
- feat(prreview): the operator-approval gate is PRReview's own stage-list entry
- feat(staterpc): carry the review gate and re-review rounds, with one guarded response write
- feat(prreview): the gate records the review it holds and posts the operator's answer
- feat(taskactions): one approval path answers the review gate from every surface
- feat(webui): the dashboard answers the review gate, including a re-review's instructions
- feat(daemon): resolve the producing identity's org before publishing work
- feat(webui): block invalid settings and show a field's former value
- fix(workflow): derive a declared output's captures need for profile selection
- fix(storepkg): validate every declared authority grant at the package descriptor
- feat(archied): refresh the model catalog at runtime
- feat(mcp): answer server-initiated sampling from the chat model
- feat(container): send registry auth on image pull
- feat(messaging): retract ephemeral replies after their TTL
- feat(messaging): transcribe Telegram voice notes
- fix(egress): take a run's credential kind from its binding, not the Kit
- feat(webui): a live-apply setting reads as applied, never as a restart
- feat(webui): the dashboard reads harness bindings and opens the setup terminal
- feat(gateway): list the harness page in the dashboard page registry
- feat(webui): the harness settings page and its setup terminal
- fix(workflow): park environment gate failures without dispatching a builder
- feat(messaging): adapter-facing clarify, picker and approval contract
- feat(gateway): gate admin slash commands by sender policy
- feat(plugins): load plugin and secret-engine files without a restart
- fix(workflow): deliver the feasibility PRD to the forge issue
- fix(messaging): report the daemon version this process was built from
- fix(messaging): carry an inbound attachment's bytes to the gateway turn
- fix(daemon): resume a retry whose worktree is gone
- fix(archied): omit the max-token bound on reasoning-class models
- fix(logging): file a task log record under its own event time
- fix(control-plane): unify validation for the domain-managed kinds
- feat(webui): let the operator choose the retry worktree mode
- feat(agent): seed a starter SOUL and upgrade only untouched templates
- feat(controlplane): add the writable review-settings resource
- fix(messaging): transcribe voice notes on the model-owning side of the boundary
- fix(messaging): gate the boundary on config reads, not only package links
- feat(messaging): restart only the channel whose settings changed
- feat(container): apply container-runtime-policies live
- feat(tools): reconcile MCP servers and tool settings live
- feat(messaging): add a per-turn interactive carrier for clarify and picker
- feat(gateway): offer ask_user when the turn's channel can carry a question
- feat(telegram): carry clarify and picker through the text fallback
- fix(webui): pin the dashboard validators to the control plane's
- refactor(agent): drop the SOUL upgrade branch with no shipped template
- feat(agentworker): answer MCP sampling from the task's model
- fix(workflow): bind the remediate worktree before the builder runs
- fix(config): carry max_retries into the worker TaskConfig snapshot
- fix(agentworker): supply the guardrail engine to every task run
archie-agent
- feat(workflow): declared workflow outputs for wait:true callers
- feat(prreview): the operator-approval gate is PRReview's own stage-list entry
- feat(staterpc): carry the review gate and re-review rounds, with one guarded response write
- feat(prreview): the gate records the review it holds and posts the operator's answer
- feat(taskactions): one approval path answers the review gate from every surface
- fix(workflow): derive a declared output's captures need for profile selection
- fix(storepkg): validate every declared authority grant at the package descriptor
- feat(mcp): answer server-initiated sampling from the chat model
- feat(container): send registry auth on image pull
- feat(messaging): retract ephemeral replies after their TTL
- feat(messaging): transcribe Telegram voice notes
- fix(egress): take a run's credential kind from its binding, not the Kit
- fix(workflow): park environment gate failures without dispatching a builder
- feat(messaging): adapter-facing clarify, picker and approval contract
- feat(plugins): load plugin and secret-engine files without a restart
- fix(workflow): deliver the feasibility PRD to the forge issue
- fix(messaging): carry an inbound attachment's bytes to the gateway turn
- fix(daemon): resume a retry whose worktree is gone
- fix(logging): file a task log record under its own event time
- fix(control-plane): unify validation for the domain-managed kinds
- feat(webui): let the operator choose the retry worktree mode
- fix(messaging): transcribe voice notes on the model-owning side of the boundary
- feat(messaging): restart only the channel whose settings changed
- feat(container): apply container-runtime-policies live
- feat(tools): reconcile MCP servers and tool settings live
- feat(messaging): add a per-turn interactive carrier for clarify and picker
- feat(agentworker): answer MCP sampling from the task's model
- fix(workflow): bind the remediate worktree before the builder runs
- fix(config): carry max_retries into the worker TaskConfig snapshot
- fix(agentworker): supply the guardrail engine to every task run
[1.45.0] - 2026-09-30
archied
- fix(eda): reject a result map missing a field or needing a conversion
- feat(eda): per-org workflow enable/disable gating bindings
- feat(telegram): carry inbound media through the chat turn
- fix(prsource): use a CodeQL-recognised containment guard when extracting archives
- feat(store): key control-plane resources by (org, kind)
- fix(store): refuse resource keys the audit key cannot disambiguate
- fix(daemon): resume the task branch before container acquisition
- feat(webui): show attachment metadata in the session transcript
- feat(webui): name a workflow's declared inputs on the work-request form
- feat(controlplane): carry the caller org from the request principal
- fix(webui): the workflow handlers act in the caller's org
- feat(kitrun): render the OAuth credential file with sentinels
- feat(store): record accepted package authority against the pin
- fix(workflow): the own-PR flow no longer parks on the operator-approval gate
- feat(gateway): a TTL-bounded dedup gate for redelivered platform messages
- feat(egress): capture the OAuth scope set and carry it to the harness secret
- feat(kitrun): render the OAuth scopes and omit an uncaptured primary key
- feat(store): project installed package contributions into org resources
- feat(gateway): coalesce rapid-fire text events into one turn
- fix(config): expand plugin, module and skills dirs like every other operator path
- fix(webui): drop the config schema's editability advert
- feat(webui): events counts, YAML reading, log rows and dashboard filters
archie-agent
- feat(eda): per-org workflow enable/disable gating bindings
- feat(telegram): carry inbound media through the chat turn
- fix(prsource): use a CodeQL-recognised containment guard when extracting archives
- feat(store): key control-plane resources by (org, kind)
- feat(controlplane): carry the caller org from the request principal
- feat(kitrun): render the OAuth credential file with sentinels
- feat(store): record accepted package authority against the pin
- fix(workflow): the own-PR flow no longer parks on the operator-approval gate
- feat(egress): capture the OAuth scope set and carry it to the harness secret
- feat(kitrun): render the OAuth scopes and omit an uncaptured primary key
- feat(store): project installed package contributions into org resources
[1.44.1] - 2026-09-29
archied
Two fixes to tasks that could not get past their workflow definition.
- Approving a task no longer parks it again. A task requeued under a
different workflow kept the previous run's definition pinned, so the worker
refused to compile the dispatch — it named
feasibilitywhile the row namedimplement— and the task parked immediately, identically on every further approval, which leftdeclineas the only working operator action. The daemon now re-pins whenever the pinned definition's id disagrees with the task's workflow. A pin that is present, digest-valid and id-consistent is still a strict no-op, so an operator's own definition override survives a dispatch unchanged. - A shipped workflow definition now reaches an existing install. A stored seed was consulted only for a resource the store did not already hold, so a document that changed in the build never reached a database an earlier release had seeded. For workflow definitions that is a total outage rather than a stale setting: the collection validates as one document, so a stored step type this build no longer has failed every task's pin, whatever workflow the task named — and the documented recovery, removing the resource and restarting, wrote nothing either, because the store answered the seed's known request ID from a history that outlives the resource. A seed now refreshes a kind it wrote the newest revision of and re-creates a resource that is gone, while an operator's own replacement is never undone.
archie-agent
The runtime image is rebuilt with this release and links the shared workflow
package carrying the definition-id helper above. Hosts that run agent
containers need docker compose pull agent after updating to pick it up.
[1.44.0] - 2026-09-29
archied
Archie can now review pull requests.
- Reviews on request and by watch. Ask in chat or on the dashboard work form, add a repository to the watch list, or just let archie review its own PRs before it opens them. Review intensity follows a depth dial (quick/standard/deep) classified from the size of the change, and every finished review passes a verification layer — coverage-gap and cross-finding consistency checks — before it is produced.
- No forge credential reaches the review sandbox. The daemon prefetches the pull request's data and rebuilds its source snapshot over the forge's HTTP API, so the agent container works from an isolated copy with no read access to the repository's credentials.
- Reviews stop at the operator gate before posting.
review.precision_gate/approve_before_postdecide whether a finished review posts itself or parks for operator approval. With this release the parked state is a stop sign, not a checkpoint: the approve/reject/re-review responses behind the gate are not wired yet, and the gate's settings are not yet editable in the dashboard (configure them inconfig.toml). A parked review sits until that follow-up lands. - The adversarial self-review pass archie previously ran before opening its own PRs is superseded by this pipeline and has been removed.
- Hardened harness input handling: harness identifiers are bounded to integer types.
archie-agent
The runtime image is rebuilt with this release; it links the shared pr-review workflow packages behind the reviews above. Hosts that run agent containers need docker compose pull agent after updating to pick it up.
[1.43.0] - 2026-09-28
archied
- Organisations. Tasks, identities and settings now belong to an org. An existing install is upgraded into a default org when the State Store first starts; the upgrade resumes if interrupted. Task de-duplication is scoped per org and identity.
- Access policies are enforced at the dashboard, the API and task
dispatch, with shipped roles and a rule that nothing crosses between orgs.
Denials are recorded and reported on the health page. If a policy locks
you out,
archied access reset --org <org>(or--instance) on the State Store host restores the shipped defaults. - Workflows can call workflows with a
workflow.callstep. Inputs and call cycles are checked when the workflow is saved, and the caller waits on the callee's result. - Runs record each step. A run's stages and agent calls are stored as steps, the task detail page reads them, and stopping a task or archiving it goes through one cancel path. After a crash, steps left running are marked interrupted. Archiving a task removes its worktree.
- Model roles, repositories, scheduling policy, providers and agent profiles apply without a restart.
- Kit harness profiles:
kitis now one digest-pinned reference, a workload Kit or a published Kit set, not a list. Rewritekit = [...]inconfig.tomlor the agent-profiles settings as the single reference; a list no longer loads. Compose mixins by publishing a Kit set.- OAuth logins are handled on the host: the egress proxy refreshes tokens, stores them encrypted, and gives the container only placeholders.
- A Kit's skills request mounts
skills_dirread-only, and its instructions file (such asCLAUDE.md) is written beside the workspace, which is now/archie/workspace. - A run still cannot be granted the credential a Kit needs, so a Kit that requires one is refused at launch.
- Rate-limited webhook deliveries get
429. archie-gatewayandarchie-state-storereport ready to systemd.
archie-agent
- Runs workflow calls, records its steps and agent calls, and runs Kit harness stages under the profile's Kit.
[1.42.0] - 2026-09-26
archied
- The dashboard is rebuilt on a new Graphite theme. Settings moved to its own sidebar with one save flow across every page (Channels, Tools & MCP, Scheduling policy, Personas and Schedules, Identities, Plugins, Container runtime, and a History of past changes). The top bar, Dashboard, Workflows, task detail, the New task dialog and the Events page are all new: Dashboard leads with what needs you, a run's stage rail and detail panels sit side by side, Workflows shows per-workflow stats including completed runs, and Events states capture status with a copyable capture endpoint. Live updates share one stream and reopen after a drop instead of going quiet.
- Settings changes are audited. A field-level audit table records who changed what, with a view on each settings page.
- A task can carry a whole-run wall-clock limit, separate from a stage's own budget.
- A run that makes no changes now ends as completed and its worktree is cleaned up, rather than left in a state Workflows didn't count.
- Abandoning a task no longer closes its forge issue. Only the workflow's own terminal outcomes do that now.
- A task whose container exits before the worker replies is parked instead of left running with no way to finish.
- A worktree still holding uncommitted work is kept, rather than reset, when its task reaches a terminal state.
- A provider's stored settings no longer get corrupted with a process-local placeholder in place of your configured secret reference, and archied rejects a stored value shaped like one on the way back in.
- Kit v3 harness profiles. A
[containers.profiles.<name>]entry can now name a Kit v3 image (kit = [...], pinned by digest) instead of a plain container image, running the task's agent stages on an external CLI -- Claude Code, Codex, Pi, OMP or GitHub Copilot CLI -- inside an isolated sandbox network. This release lands the daemon-side plumbing (egress proxy, sandbox network, credential injection points); it does not yet ship a way to grant a run's identity the credential a Kit needs, so a Kit requiring one is refused at launch until a later release adds it. task devnow starts the State Store and waits for it before the rest of the stack.- Every service binary the installer builds is stamped with its version.
archie-agent
- Carries the same task-lifecycle fixes as archied above (no-change runs, parking on an early container exit, and the abandon/forge-issue fix), plus the Kit v3 harness runner: a stage can now drive an external CLI headlessly, read output from Claude Code, Codex, Pi, OMP or GitHub Copilot CLI, and serve it capture tools over MCP.
- Claude's cached tokens are counted as prompt tokens, matching the built-in agent loop's accounting.
[1.41.2] - 2026-09-25
archied
/updateno longer offers an old runtime. The runtime has shipped under the release version since the version streams merged, but the update check still read the retired runtime tags, so a current host was offered runtime 1.35.0 as an update. Do not approve that offer on 1.41.1; update to 1.41.2 instead./versionreports the runtime version. Binaries from the release zip showedRuntime: dev.
[1.41.1] - 2026-09-25
archied
- First published build of 1.41.0. The 1.41.0 tag produced no release artifacts; 1.41.1 carries everything listed under 1.41.0 below, including the PostgreSQL 18 requirement and the removed config keys.
[1.41.0] - 2026-09-25
archied
- Archie now stores everything in PostgreSQL 18, and
database_urlis required. Tasks, events, captures, bindings, settings and chat conversations are served from the databasedatabase_urlnames; the State Store, archied and the Gateway refuse to start without it, and refuse a server older than PostgreSQL 18.docker compose up -d postgresstarts a matching local database with the default URL inconfig.example.toml. - Existing SQLite data is not carried over. This release reads no SQLite
file and ships no importer, so an upgraded install starts with empty task,
event and conversation history.
db_pathis gone;state_dir(default~/.local/share/archie) now holds the embedded NATS store and task logs. - Backups are whole-database snapshots.
archie-state-store backupandrestorework on the PostgreSQL database throughpg_dump/pg_restore, which must be onPATH. There is no automatic schema rollback: the way back from an upgrade is restoring the snapshot taken before it. - Events carry a type, and bindings pick one. Archie infers an event type from captured payloads; the Inspector shows proposed and unidentified events and lets you name them. Mappings are per event type and show how many captures they match, a source can feed several bindings, and a binding chooses an event type plus an optional filter. An unidentified event does not dispatch.
- Sources own webhook signing. Each source gets a UUIDv7 path and its own signing secret, or can be explicitly approved to accept unsigned events. A new binding starts pending approval.
- EDA playbooks can run module actions and take workflow inputs. Action
playbooks run at most once per event through the dispatch ledger, a binding
can pass inputs to its workflow, the repository is optional, and a workflow
can name an agent profile.
archie-playbooks lint -eda-dirchecks a directory, andarchie-playbooks servepublishes the same findings to your editor as a language server. - Config keys removed.
[agent],[oidc],[image],containers.enabled,db_path, and thetoken_envform of[forge],[artifacts]and[chat.telegram]no longer exist. Write each credential astoken = { engine = "env", key = "NAME" }. A leftover key is reported at startup as unrecognised rather than failing the load. - Dashboard. Old
#/pathlinks and the/captures,/mappingsand/bindingsaddresses no longer redirect; use the Events page tabs. The live stream moved to/api/stream, so reloading/eventsserves the page.
archie-agent
- The Postgres-backed wire formats, event types and workflow inputs are part
of this image; a host that runs the agent should
docker compose pull agentto pick it up.
[1.40.0] - 2026-09-23
archied
- Every park now says what kind of intervention it needs. A parked task
is classified as
needs you(a decision or fix only an operator can supply),transient(an environment problem -- container pool, storage, transport -- retry once it is fixed), orterminal(the repository or identity cannot act; retrying cannot succeed). The class shows beside the Parked badge on the dashboard, so "needs you" reads as a request rather than a failure. - Operator retries and review-remediation rounds now have separate budgets. An operator's manual retries no longer draw down the rounds Archie may spend addressing review feedback on its pull requests, and a round-cap park no longer makes a later retry re-park immediately.
latestnow names the newest release. A push tomainthat is not a release publishesedgeandsha-<commit>instead. A host that was followingmainby pullinglateststops advancing at this release -- switch it toedgeto keep trackingmain, or leave it onlatestto follow releases.
archie-agent
- The park-classification wire format is part of this image; a host that
runs the agent should
docker compose pull agentto pick it up.
[1.39.0] - 2026-09-23
archied
- Archie now acts on review comments left on its own pull requests. A
requested-changes review (or a standalone comment) on a PR Archie opened
dispatches a remediation run: the smallest change that satisfies the
feedback, committed to the same PR branch and answered in the review
thread. Approved reviews never remediate, each reaction is its own round,
and the exchange is bounded by the repo's
max_retriesbefore Archie stops and says so on the PR. - The task run page is a master-detail view. The run's stage rail and detail panels sit beside the run list, so one run's timeline is visible without leaving the page.
- Live activity groups related updates instead of stacking them by event kind, so a burst of progress on one task reads as one story, and the stage filter resets when you switch attempts.
- Contrast fixes on the info and subtle text tokens clear WCAG AA.
archie-agent
- The review-reaction remediation path is part of this image; a host that
runs the agent should
docker compose pull agentto pick it up.
[1.38.0] - 2026-09-23
archied — Event capture, mappings and bindings are PocketBase records
- Captured events, field mappings and playbook bindings live in PocketBase collections instead of SQLite tables. They are ordinary records, which is what lets a binding be changed at runtime rather than by editing a database.
- A read-only operator surface over the task database ships with the State
Store (
archie-state-store -admin-addr). It serves view collections over tasks, transitions, events, identities and resources, and refuses/api/backupsandPOST /api/sql, so it cannot rewrite state or hand out the database file. - A binding cannot go live without approval. It moves draft → pending approval → armed; one binding per source is enforced on insert, on edit and on approval; and an edit always returns it to pending approval. A secret left blank on an edit keeps the stored one rather than disarming a live binding.
- The workspace code-search indexer is gone. No deployment configured it, and it was one more resident writer over the workspace.
archied — Editing a binding or a mapping shows on the activity stream
- A dashboard edit no longer needs a manual refresh. A successful binding or mapping write announces itself on the same activity path a captured event already uses. The announcement carries the record id and the action and the dashboard refetches the record, so the signal cannot go stale.
archied — Cron schedules fire
- A cron job computes its next run and fires. Until this release a cron
schedule was accepted at creation and then refused at run time with
ErrScheduleUnsupported, so a cron job never ran. - The dialect is PocketBase's, and it differs from Vixie cron on one point.
Day-of-month and day-of-week are combined with AND rather than Vixie's OR, so
0 0 1 * 1means Monday the 1st, not "the 1st, or any Monday". The@daily-style macros behave as usual. An expression that can never match, such as0 0 30 2 *, is rejected instead of being left to run forever.
archied — Tool calls are queryable
- Every completed tool call is a row in the
tool_callscollection, not only a line in the on-disk task log. The row carries the task, the attempt, the tool, its result or its error, and when it ran. - A failed projection never fails the task. The event is the record and the collection is a transcript of it, so a copy that could not be written is logged and counted rather than propagated.
archied — A task whose identity no longer resolves parks instead of acting as root
- A task naming an identity archie no longer knows — renamed, retired or removed in the control plane — no longer falls back to the root forge's credential. It parks with the reason recorded. A task arriving over NATS with such an identity is refused before it is enqueued. A task with no identity is the single-identity root path and is unchanged.
archied — The PR review is published as a readable artifact
- A completed review is rendered to markdown and published to the collaborative editor, so a person reads it and comments on it instead of reading a wall of text in a pull-request comment.
- Publishing never fails the review. With
[artifacts] base_urlunset the sender is not constructed and publishing is a log line; a publish that fails is logged with its status and the same review is republished the next time it completes. Set[artifacts] token(orWORKSPACE_INGEST_TOKEN) to enable it.
archied — The activity feed no longer depends on row ids being monotonic
- The feed's resume cursor is opaque, and a malformed or pre-upgrade cursor degrades to "from the beginning" rather than failing the stream. One consequence on upgrade: a browser holding a cursor issued before this release replays the backlog once.
archie-agent
- The runtime image is rebuilt by this release, and a host must pull it
(
docker compose pull agent). The shared State Store contract changed shape in the sections above — task and event-capture id fields are strings now — and the two halves are versioned together, so an agent image built before this release does not speak to the new State Store. There are no agent behaviour changes of its own in this release.
[1.37.1] - 2026-09-22
archied — A recorded event names the actor in its own fields
- Event attribution survives the trip to the State Store. The acting identity, its kind, and the authorising principal are carried on the event itself, so an audit query finds the actor in its own fields rather than only in the event's prose. An approval taken through the dashboard is the case that exposed the gap.
archied — A chat reply that contains code renders the way it was written
- A code fence closes only on a run of the same character that is at least as long as the one that opened it. A four-backtick fence, a tilde fence, or a reply that wraps its own code in a longer fence now arrives as code instead of as a broken language tag or paragraphs of leaked text.
archied — A tool call is one line with its own icon
- A tool call takes a single line instead of a label plus a fenced block. Telegram draws a fenced block as a full code widget — language header, copy button and panel — and the block parser inserts a spacer before it, so a handful of calls filled the screen to show a few word counts. Each call now shows the icon its own tool declares, and a tool that declares none renders without one.
- The status word prints only when the outcome is not success. Every tool line previously read "done", including the ones that had not finished.
archied — Runtime dependencies updated
- Runtime dependencies updated, including the OpenID Connect and OAuth libraries.
[1.37.0] - 2026-09-22
archied — A request is attributed to the identity that made it
- A browser can sign in, and an action taken through it records the person. The dashboard validates a
provider-issued token, resolves it to an identity, and attaches it to the request; the task-action record
then names the actor.
Authenticateand the sign-in callback share one resolver, so a browser sign-in cannot be accepted on terms a presented token would be refused on. - archie issues no session. The callback stores the provider's own token in an HttpOnly cookie and every later request re-verifies it, so nothing archie holds can outlive the provider's decision and there is no session table to expire, revoke or get wrong.
- The event kind describes the actor. A person's approval records
human_approvedas that person; an agent's recordsagent_approved; an action with no authorising principal recordstask_approvedwith the attribution fields empty. Nothing is credited to an identity that did not act, and an unattributed action is recorded as unattributed rather than guessed. - The acting identity is derived from the presented credential and never from a request field: a body
carrying
actor,actor_id,identityand anX-Archie-Actorheader still cannot choose it.
archied — A host install now works, and an update refuses a host it cannot keep consistent
install.shwrites and enables all five host units; previously it seeded onlyarchied.service, so a fresh host ran one service of five and an operator applied the rest by hand from a runbook. The runbook is a description again: it names the units and points atsystemctl --user cat.- Every host binary reports its version, and the updater reads all of them before it can report "nothing to install". A host whose binaries disagree is refused, naming each one: a newer messaging binary beside an older state store crash-loops against a service the older store does not serve, and that install previously looked healthy from the updater's point of view.
- The packaged, installer and updater command lists are pinned by a test, so a service added to one and not the others fails the gate instead of shipping a partial install.
archied — A release image can be traced to a commit
- The publish step derives the commit by dereferencing the ref rather than reading
github.sha, because every release tag in this repository is annotated and a tag's object id is not a commit. An immutablesha-<commit>tag is published alongside:latest, and a build with no release tag is stampeddev+<short sha>rather than a baredevthat identified nothing.
archied — Curator definitions are data, not a second registry
- Curator definitions may come from configuration or code and run through one engine into the existing registry — no parallel authority and no second config reader. A definition declares its tools, and an unknown tool name fails rather than widening the set silently.
[1.36.0] - 2026-09-22
archied — The dashboard declares tools an in-browser agent can call
- The dashboard registers seven WebMCP tools. Read-only:
list_tasks,get_task,recent_events,daemon_health. Recovery:retry_task,stop_task,cancel_task. An agent operating the dashboard now reads structured state and recovers stuck work instead of scraping the UI. - Every tool wraps the same
ui/src/lib/api.tsclient the dashboard itself calls, so an agent and a person exercise one path rather than two. archie-uicannot be attributed to the agent that called it: a page can invoke its own tools, so an agent's call and a page script's call reach the server identically. Tools therefore record the signed-in identity and a source, and never that an agent acted.
archied — Binaries built by the development build task can be updated
task buildpassed theinstalltypestamp for three of six commands, soarchie-messaging,archie-state-storeandarchie-uiwere built without it. An unstamped binary reportsunknownand the self-update path refuses rather than guesses, which is how an operator ends up unable to update withinstall type is unknownand no way forward. All six are stamped now, and a test reads the build task and fails naming any command line that omits it.
[1.35.0] - 2026-09-22
archied — The Messaging Service is severed from the store and workflow runtime
cmd/archie-messagingno longer linksmodernc.org/sqlite,internal/store,internal/domain/workfloworinternal/agentexec. All four arrived through a single import ofinternal/app/controlplane; the client half now lives ininternal/infrastructure/controlplanerpc, and the app package keeps the server, the registry, the seeds, the validators and the schema derivation.- The resource documents are type-aliased back into the app package, so there is one definition read under two names rather than a copy per side.
archied — Channel lifecycle reaches the dashboard
- The Messaging Service reports each channel's state, recorded per channel: one channel's failure
marks only itself, a channel that cannot start is marked failed with its reason rather than only
logged, and one that returns is marked stopped.
internal/channels/status.Managerreports each channel's state. PutChannelStatus/ListChannelStatuscarry that to the dashboard, following the config-snapshot split. The store replaces the reported set, so a channel the reporter stops mentioning is deleted rather than left as a stalerunning; an empty report clears the table, because hosting no channels is a fact worth reporting; and an id-less row is refused, since it could never be replaced or removed by a later report.Service.ReloadChannelroutes to the channel's own seam and refuses a channel that cannot reload with a reason rather than accepting and ignoring it.ReloadSupportedwas previously declared by name, so a channel could advertise reload with nothing behind it; one function now decides both.
archied — Action playbooks: a second playbook shape, with typed results
- A playbook is now one of two shapes: a workflow playbook (exactly one
workflowaction, unchanged) or an action playbook (one or moremoduleactions in order). A playbook does not mix them. argsandwhenshare one compilation path and one evaluation context, andactions.<id>is typed by the kind that action runs, so a misspelled result field, an unknown id, a map index,in, a comprehension, or a shape-foreign key (kindon aworkflowaction,workflowon amoduleaction) is a load failure rather than a dispatch failure.- Action playbooks load but do not run yet. Routing arrives with the first side-effecting position; the daemon warns at load rather than accepting them silently.
- The CEL environment is built per playbook, because result typing depends on the ids a playbook declares.
ModuleRegistry.DecodeResultturns a kind's flat map result into its typedResultbefore a later expression reads it. Without it a typed read evaluated against a shape the run never produces, and so silently read null.
archie-agent
The sandboxed runtime links the same shared packages as archied, so this release carries the channel-lifecycle store contract and the stricter action-load errors with it:
- The channel-status store contract (
PutChannelStatus/ListChannelStatus) and its replace-the-set semantics. - Authoritative module ids and stricter action load errors: a misspelled result field, an unknown id,
or a dynamic
actionsread now fails the playbook load rather than the dispatch.
archied and archie-agent move together in this release.
[1.34.0] - 2026-09-22
archied — Dashboard: an actionable authentication failure state
- An unauthenticated document request now receives a self-contained HTML page with a
paste-the-token form, instead of plain text. Previously the whole dashboard --
index.html, the bundle and every asset -- sat behind the token check, so a bookmarked bare URL returned atext/plain"unauthorised: open the dashboard URL archied logged at startup", the SPA never ran, and none of the dashboard's existing failure surfaces were reachable at all. - The response is still 401, with
Cache-Control: no-storeand a CSP. It is deliberately not a 200: a login page served as success would be cacheable, would read as healthy to anything that checks status alone, and a shared cache could hand it to the wrong person. - API and stream callers are unaffected.
application/json,*/*andtext/event-streamrequests keep the plain-text 401, with a test pinning that split so an XHR or anEventSourcereconnect can never start receiving a page. - The auth banner gains a Retry action that re-runs the dashboard's bootstrap reads, so a recovered session is actionable without a browser-level reload. It deliberately does not re-drive the SSE stream, which already reports its own reconnect state.
- The page's guidance stays generic: it points at the dashboard URL the daemon logs rather than naming where the token is stored, so the HTTP layer is not coupled to the token file's location.
[1.33.0] - 2026-09-22
archied — EDA: playbook action arguments are compiled at load (J2)
- A playbook action may now declare
args, compiled as CEL expressions when the playbook loads.argsandwhenshare one compilation path and one evaluation context, so an expression written for one works in the other. - Behaviour change: an
argsexpression that does not compile is a load failure, not a runtime miss — the same reject-at-load rule already applied to a binding collision and to an unknownactions.<id>. In practice, a daemon loading a playbook with a malformedargsblock fails at startup rather than part-way through a dispatch. - Compiling several arguments now reports the first bad key deterministically (keys are sorted). Previously it ranged a map, so the reported bad key could differ between runs and the failure was not reproducible.
argsis deliberately inert for now: parsed, compiled and stored, but no shipped position consumes it yet. A consumer arrives with the first side-effecting position.
Not yet decided: how an args evaluation failure behaves at dispatch. The when predicate rule
(error, skip, log) does not obviously transfer, because args is data rather than a predicate, and
silently skipping an action whose arguments failed to evaluate would be a silent failure of exactly
the kind this release train has been removing. It currently propagates the error to the caller, and
that asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately.
[1.32.1] - 2026-09-22
archied — Host packaging: archie-messaging now ships and updates
cmd/archie-messagingis included in the distribution zip, andscripts/archie-update-installinstalls and restarts it.- Why this mattered. v1.30.0 moved Telegram, email and webhook out of
archiedand intoarchie-messaging, but nothing packaged the new binary. A host install that upgraded across v1.30.0 therefore ran on with no messaging process at all:archiedlogged that it stopped serving the telegram gateway, nothing replaced it, and Telegram stayed dead — with no error logged anywhere, because nothing was failing. The process simply did not exist. - The host component set was enumerated in four places — the zip's build loop, the zip's copy list,
the installer's service list, and the installer's binary list — and
archie-messagingwas missing from all four. The duplication was the defect: a single test now derives the host-run commands fromcmd/and asserts that all four lists agree with it, so adding or extracting a process fails until it is packaged. deployments/systemd-user-service.mdgains the messaging unit. That is load-bearing rather than cosmetic: the updater refuses an update when a service unit is missing and tells the operator to create one from that document, which previously had nothing to offer.
Upgrade note: a host that reached v1.30.0 without a messaging unit has been running with no
Telegram, email or webhook. Updating to this release installs and starts archie-messaging.
[1.32.0] - 2026-09-22
archied — EDA: playbook action ids, and a dispatch idempotency ledger
- Action ids (J1). Every action a later action references must now carry an
id. Ids are validated at load -- unique and stable-identifier-shaped -- and awhen/argsexpression naming an unknownactions.<id>is a load failure, not a runtime miss, the same reject-at-load rule already applied to a binding collision. - Reference classification is strict at load. A map-index reference (
actions[expr]), a non-literal index, and a reference to an unknown prior id are all rejected when the playbook loads; references are classified by identifier versus static access, and the when-compilation helper is shared between the load-time and runtime paths. - Dispatch idempotency ledger. A
playbook_dispatchesrow records a dispatch against(playbook_id, playbook_version, event_id, action_id), written withINSERT OR IGNOREand surfaced through the sharedstore.ErrAlreadyDispatchedsentinel. Module, channel and forge action positions are therefore at-most-once, which is what unblocks the side-effecting positions that were previously rejected at load. - The ledger is wired into production.
stateStoreDepsconstructsDeps.PlaybookDispatcher, so the ledger RPCs no longer answerUnavailablein a running daemon. This defect was found by the pre-release review of this change rather than by its tests.
Behaviour change: a playbook whose actions reference actions.<id> without declaring that
id, declare a duplicate id, or index actions with a non-literal value now fails to load
instead of failing at dispatch time.
archie-agent
The sandboxed runtime links storecontract and staterpc, so it carries the dispatch-ledger
contract alongside archied:
- The shared
store.ErrAlreadyDispatchedsentinel now describes both dedup ledgers --binding_dispatchesper(binding_id, capture_id), andplaybook_dispatchesper(playbook_id, playbook_version, event_id, action_id). Each is an at-most-once guarantee. RecordPlaybookDispatchis part of the store contract the runtime builds against.
archied and archie-agent move together in this release.
[1.31.0] - 2026-09-22
archied — Dashboard replaced: Preact -> Vue 3 + shadcn-vue
The dashboard is now a Vue 3 application built on shadcn-vue. This is the large piece of this release; it touches every page.
- History routing, a grouped topbar built from components, the violet palette with self-hosted Geist, and a command palette with live tasks.
- Chat is a FAB-opened panel that behaves like a chat window and scrolls its
transcript with
MessageScroller. - Task actions and dangerous approvals are deliberate; the task detail page is a single head strip with honest states; the run page settles its head around an attempts pager, which is hidden for zero or one attempt.
- Appearance and System navigation were refined, with a four-column appearance grid on wide screens.
- A copy pass removed redundant tails and restating descriptions, empty states derive their own titles, and a stuck log read surfaces as an error rather than eternal loading.
- The capture pane is bound to the list it sits beside and reads beside it, not over it.
archied — Events is one page with three tabs
- Inspector, Bindings and Mappings are now tabs of a single Events page.
- The nav entry is always live, the tabs prune by capability, and the three old paths survive as bookmarks that redirect to their tab.
- Tab selection lives in one module (
ui/src/events/tab-selection.ts) that the page uses, rather than a copy of it. feat(tools): a capture-intake sender exists for exercising the Events surfaces.
archied — The channel travels with the message
SessionSource.Platform -- the first component of the session natural key, and
the column GetByChannel filters on -- was a constant "web", because one
Router serves every channel and named itself after its own. Two things followed:
the per-user identity policy was real code that no production call site reached
with a real channel name, and a curator pass's write to agent-user memory could
not be read back by the turn that wrote it, because that turn resolved no
UserID.
- The frontends now name the channel they carry (
telegram,email,webhook,web), the channel rides the message, and the Gateway stamps the session from it -- falling back to its own name when a sender names none, which is what every existing row holds. - Identity resolution reads the platform off the inbound, so
carriesPersonIdentitydecides something in production: telegram and email resolve a person, the dashboard and a webhook resolve nothing, and an unknown platform fails closed. - Behaviour change: a chat whose active session came from
/newor/branchre-resolves once, because session lookup now filters on the channel's real name. A chat without/newre-resolves onto the same deterministic id and heals silently. - Deliberately unchanged:
TurnRunnerConfig.Channelstill keys tool availability, so no channel gains or loses a tool in this release.
archied — Control plane: runtime administration, history, and derived schemas
- The State Store's gRPC server now carries runtime administration, and each process reports which settings version it is running; the dashboard shows it.
- Resource history is exposed so edits can be reviewed and rolled back, and
resource schemas are derived from the documents they describe -- the document
editor reads the derived schema (labels from
title,format: duration->1m0s, hints fromdoc), and the abandoned schema-driven card is deleted. - A live settings replacement is checked before it is switched to, the daemon's state surfaces are folded into one boot step, and a SIGHUP reload re-applies database-owned settings.
- Forge intake settings that nothing reads are now rejected at load.
archied — Configuration: judged where it is owned
- The runtime config overlay is deleted; database-owned settings are judged at the layer that owns them rather than on the file load path.
- A file overlay no longer drops the fields it omits inside a map entry, and a kind with no stored value leaves the file's value in force.
- The default config path is resolved in one place, and the channel document has its own shape.
archied — State Store: offline backup, restore, validate and rollback
- New offline backup / restore / validate / rollback path.
validateruns boot's own gate; it no longer replaces the database, reads a kind the store does not hold as its seed, or touches the daemon's log.- The recovery control-plane server is built on the shared step vocabulary.
archied — Workflow: one step vocabulary and a gate.diff-rules replacement
- The step vocabulary is owned by a family manager registered at each
composition root, replacing
.archie/gate.gowithgate.diff-rules, which fails closed on a change it never read. - Workflow roots are pinned and the dead vocabulary is removed; the workflow pin crosses the wire.
- The schedules resource skips the legacy cron jobs it cannot hold, and the scheduling policy carries the label its trigger pairs with.
archied — EDA: the playbook coordinator reaches production selection
- The playbook coordinator is wired into production workflow selection, so a
matching playbook decides a real task's workflow at the daemon's definition
pin, inheriting idempotency from
TaskEnvelope.
archied — Reliability and operations
cronstorewrites a schedule interval as a duration, not nanoseconds -- a persisted1mno longer round-trips as60000000000.- Worktrees are cut from the mapped base branch, and the Gateway's worktree
manager is built so it serves
review_pr. - A late max-uptime callback no longer resurrects teardown state.
- The state store dial installs client keepalive, and its server policy accepts the dialer's pings; control-plane watch streams re-establish themselves after they end.
/statusserves only the health facts a reply can carry; the daemon reports systemd readiness and loop-driven watchdog heartbeats.- A webhook route path no longer becomes a sender identity.
- A chat session compresses when a turn crosses its context budget.
- The MCP client supports per-server
parallel_tool_calls, carried through the tool-settings projection. - Resource request-ID idempotency keys are scoped to their kind.
- The session curator addresses memory by the deployment's bot user.
archie-agent
The sandboxed runtime links the same shared packages as archied, so this release carries the control-plane and workflow changes alongside it:
- Runtime administration over the State Store's gRPC server, resource history, and control-plane apply status on the store contract.
- The shared step vocabulary, owned by a family manager registered at each
composition root, and
gate.diff-rulesin place of.archie/gate.go(fails closed on a change it never read). - The workflow pin crosses the wire.
Runtime-specific changes:
refactor(plugin): the unusedRegistrytype is deleted.yaegiutilrefuses incomplete Yaegi interface wrappers at load rather than running them.- The runtime config overlay is deleted.
- The state store dial installs client keepalive, and the server policy accepts the dialer's pings.
- The MCP client supports per-server
parallel_tool_calls. - A late max-uptime callback no longer resurrects teardown state.
- A webhook route path no longer becomes a sender identity.
Note: the archie-agent image is rebuilt by this tag through CI
(.github/workflows/deploy.yml); a gateway-only release would not have rebuilt
it. docker compose pull agent is required to pick it up.
[1.30.0] - 2026-09-20
archied — Messaging Service extraction completed
Telegram, email and webhook no longer run inside the daemon. They run in
archie-messaging and reach the daemon through the Gateway's ChatContract
over gRPC; the daemon builds no channel and no gateway.Router (#899).
- The operator surface is re-wired in the extracted service:
/update(built from its own[chat.telegram]commands), the update-report relay, theshow_tool_callsprojection, and/restart's config reload, which re-resolves the token and allowlist from this service's own file and refuses a reload that resolves to an empty token. /versionis sourced from the Gateway through a newChatSnapshot.Versionfield.cmd/archie-messagingdeliberately takes no version ldflags, so it cannot report a partial upgrade as a matched one.- Channel configuration is validated at composition, so a configured-but- invalid front-end fails the service instead of being silently dropped.
- The inbound rate limiter moves to the Gateway, which now owns the only Router and is therefore the one place a per-sender budget can apply to every channel's turns.
RunningVersions and ReleaseAnnouncements are deliberately left unwired:
both need a component's real running version, and the only versions this
process can obtain are another binary's stamps. See
docs/architecture/migration-decisions.md.
archied — Configuration
diff_cap_lines = 0now switches the cap off, as the dashboard and the workflow step have always documented. It was a plainint, so the defaults pass could not tell an absent key from an explicit0and rewrote both to 400 -- the documented way to disable the cap was unreachable. Behaviour change: a config that set0was silently getting 400 and will now get no cap.- The same ambiguity was failing open per identity:
configForIdentityassigned the identity's value unconditionally, so an identity that merely omitteddiff_cap_linesoverwrote the shared cap with the zero value and disabled the safety rail entirely. An identity now overrides only when it sets the key. - A diff-cap park no longer tells the operator to "approve manually". A parked task's actions are retry, abandon and reject, so there is no approve path out of diff-cap; it now names the two things that work.
[health].dependency_timeoutmakes the daemon's readiness probe timeout configurable, matching the extracted services.
archied — Chat rendering
/statusand/tasksare line-oriented reports but separated lines with a plain newline, which is CommonMark's soft wrap: the Telegram renderer joined them into one run-on paragraph. The renderer implements CommonMark's hard line break and the reports use it. Ordinary prose still soft-wraps.- A park reason is capped to its first line in the
/taskslist. It carries whatever the failing stage reported, which for a lint gate is a whole tool log; unbounded, one parked task pushed every other task out of the reply. The full reason is unchanged on the task, intask_listand on the dashboard.
archied — Review
- Review findings are posted as line-anchored PR comments with suggested fixes, and a suggestion must be single-line -- GitHub applies a multi-line suggestion only up to its first line, silently corrupting the file (#891).
- The remediate workflow handles PR review comments and requested changes.
archied — /status health surface
/status reports the live broker connection and the last-known outcome of this
process's chat-model calls, alongside the queue depth and runtime block (#892).
- A provider error is flattened and capped, so a multiline or oversized error cannot break the one-line-per-fact layout.
- Concurrent model calls no longer reorder: the completion time is taken before the lock, so the newer outcome wins rather than whichever goroutine stored last.
- Curator model calls are recorded too. They bypass the chat path, so a daemon whose only recent model traffic was curator work reported "no calls attempted yet" while the provider was demonstrably reachable.
- Title generation does not record health. It runs detached under its own bound and its error is swallowed, so a cosmetic timeout was overwriting the line with "failed".
Known limitation: the container, poll and channel sections cannot render. Those facts live in the daemon, but the only Router lives in the Gateway process, which has no container pool and no poll loop. The command description says what actually appears; restoring the rest needs a cross-process health contract.
archied — Dashboard and containers
- The served lifecycle vocabulary reaches an already-painted page, the page
registry matches the routes, and the build verifies
ui/distis fresh instead of never looking at it (#890, #898). - The container reaper no longer deletes teardown bookkeeping early, so a released container is not torn down twice (#893).
archied — Build
task fmtrunsgolangci-lint fmt-- the same engine and configuration the gate checks with. Standalonegofumptcannot reproduce gci's import grouping, so formatting and linting could not converge and no command satisfied the gate (#901).goimportsis deliberately absent from the formatter set: it re-reads and re-parses the module index once per file, ~135s across this tree.
archied — Fixed
Config.Cloneleft the new diff-cap pointers aliased, so a clone could write through to the published snapshot (#902).- A curator asking for a completion on a daemon with no configured provider panicked the process; it now returns an error.
archie-agent
- The sandboxed runtime picks up line-anchored review comments: a finding is posted against the line it is about, with a suggested fix where it has one, and a suggestion is rejected unless it is single-line -- GitHub applies a multi-line suggestion only up to its first line, silently corrupting the file (#891).
diff_cap_linesis an optional value in the shared config the runtime reconstructs, so an explicit0means "no cap" rather than being rewritten to the default. Behaviour change for a repo that set0expecting unlimited and was silently getting 400 (#899).- A diff-cap park names a remedy that exists: a parked task's actions are retry, abandon and reject, so the reason no longer says "approve manually".
- A released container is not torn down twice -- the reaper no longer deletes
teardown bookkeeping before
Releaseis finished with it (#893). - Build toolchain:
gofumptandgolangci-lintare pinned as one matched pair, andtask fmtuses the same engine the gate checks with, so the runtime's own gate is satisfiable (#901).
[1.29.0] - 2026-09-19
archied — Security
google.golang.org/grpcbumped pastv1.84.0to patch GO-2026-6443, a server panic via a missing:authority/Hostheader reachable througharchied's gRPC gateway server. No stable release carries the fix yet, so this pins the pre-release commit that does (v1.85.0-dev.0.20260825072537-93e31b48545e) untilgrpc-gocutsv1.85.0.
archied — Memory engine unification
One memory engine, addressed by four typed scopes (global, agent, user, agent-user), replaces the two disconnected stores that previously existed: a chat-tool-written store nothing ever read back, and a curator-written store with no scope model.
internal/domain/memoryis a CRUD contract (Create/Get/Query/List/Update/Forget/Revisions) with retained revisions; updates supersede rather than overwrite, so a crash mid-write leaves a recoverable extra history entry, never a lost prior state (#886).- The chat turn reads its subject's scopes synchronously before the prompt is
built, rendering recalled records into a
<memory>block; a failing or panicking engine degrades to no memory block rather than failing the turn (#887). - The model writes memory through four id-addressed tools
(
memory_create/update/delete/list), scoped to the turn's own resolved identity -- the model chooses the scope kind, never the ids, so it has no path to write into another user's memory (#888). - The session curator now derives the agent-user scope from the session's own user-role messages, instead of keying facts by a session id that stops meaning anything once the session ends.
- A channel with no resolvable user (dashboard, webhook) reads and writes only global and agent scope; a webhook's route path is never treated as a user identity.
- Fixed a review finding on the read path: the per-scope record limit was being applied as one shared total across all scopes rather than per scope, and the rendered block's byte cap was checked before template escaping rather than after, letting the escaped block exceed it.
archied — Work intake
- feat(workintake): define review reaction envelope
- feat(workintake): authorize review reactions by owned PR
archied — Cleanup
- Deleted the unwired plugin capability-host health surface
(
Host.Health/Host.Manifests/ModuleStatus) and theModule.Healthchain it fed -- including themcp/builtintool-provider health implementations and their aggregation intools/provider.Registry-- none of which had ever had a production caller (#882).
archie-agent
- The sandboxed runtime picks up the review-reaction envelope and its owned-PR authorization, so an agent can only react to reviews on pull requests it opened itself.
google.golang.org/grpcbumped pastv1.84.0to patch GO-2026-6443 (shared dependency witharchied; the pre-release commit is pinned pending a stablev1.85.0).
[1.28.0] - 2026-09-19
archied — Task detail and attempt attribution
- New per-run task detail page, showing each attempt's own events, changes and configuration rather than a single merged view.
- Events, changes and config are attributed to the attempt that produced them;
EventcarriesattemptandReadTaskLogRequestcarriesstage. - The task detail page remounts when the task id changes, so switching tasks does not leave the previous one's data on screen.
archied — Configuration
- Services are keyed by name through a registry, so the State Store and Gateway listen addresses are configurable rather than fixed.
- A partial overlay no longer clears the fields it omits — an overlay that set one key was wiping the rest.
- The Services map is cloned on publish, so an overlay can no longer mutate the snapshot other readers are holding.
- The service context is enforced at registration.
archied — Logging and park reasons
- A parked run's reason is recorded in its own attempt log, in both the daemon and the workflow, so "why did this park?" is answerable from the task itself.
TaskRegistry.Writetakes the caller's context.
archied — Worktrees and containers
- Retries recover from path-type conflicts instead of failing opaquely, and the underlying cause is no longer masked.
- The worktree is handed back on every sandbox exit.
- A container's max-uptime reaper is cancelled on release, the cap stays active through the grace period, and teardown is claimed once rather than by cancelling a timer.
archied — Daemon and startup
- Every identity's forge and repos are swept at startup, including the root forge.
- A cancelled startup is no longer reported as an exhausted sweep budget; an exhausted budget names itself as the cause.
archied — Other
grepcan use the workspace codesearch index.- Forge labels are matched when namespaced, so label-driven routing works for namespaced labels.
- Triage is given criteria for choosing between workflows, and a workflow is required when a code change is needed.
- The Telegram adapter restart callback is wired into the chat router.
- The
ARCHIE_REACTIONSfan-out stream is provisioned and bounded by age. archie-uiexits cleanly when graceful shutdown overruns its deadline.- The dashboard's event pump retries priming until the State Store answers.
- The update writer emits the agent version sidecar with a real newline.
- The UI finishes its Preact port; the imperative DOM layer is deleted.
- Collection fields decoded over the State Store gRPC contract are never nil
slices, so an empty collection marshals as
[]rather thannull.
archie-agent
- The sandboxed runtime picks up the attempt-attribution contract, so the events and changes an agent produces are recorded against the attempt that produced them.
grepcan use the workspace codesearch index.- A worktree is handed back on every sandbox exit, and container teardown is claimed once — a released container's reaper is cancelled rather than re-firing during the grace period.
- Retries recover from worktree path-type conflicts instead of failing opaquely.
- A parked workflow run records its park reason in its own log.
- Triage criteria distinguish the workflows, and a workflow is required when a code change is needed.
- Namespaced forge labels match when routing by kind.
- The
ARCHIE_REACTIONSfan-out stream is provisioned. - Collection fields decoded over the State Store gRPC contract are never nil
slices, so an empty collection marshals as
[]rather thannull.
[1.27.0] - 2026-09-17
archied — Dashboard task logs
- Task logs are readable from the dashboard again, through a new State Store
read contract (
ReadTaskLog,StreamTaskLogContent) rather than the UI process reaching into the daemon's log files. Wired server-side by the standalone state-store process. - Added
GET /api/tasks/{id}/logs/download, serving an attempt's raw log as atask-<id>-attempt-<n>.logattachment. - A process that cannot read logs and an attempt that recorded no log are now distinguishable ("cannot read" answers 503, "no log" answers 404) instead of both rendering as a claim about a configuration setting.
archied — Telegram output
- Tool results are summarised rather than quoted: a search reports how many matches came back, a truncated result reports the tool's own total. The renderer no longer states a count it computed from its own truncated sample.
- Repeated successful tool calls collapse into one counted entry.
- The tool-activity block is capped to a third of the live frame, keeps the
newest lines, and marks what it dropped with a
+N earlierindicator. Every line that fits is kept. - Every clamped answer marks its cut with an ellipsis, including the opening frame, which previously appeared to begin mid-sentence.
- An error response from the log download no longer ships as a
.logfile.
archied — Readiness and shutdown
- The disk probe reports per-filesystem results and checks the root filesystem as well as the work directory, so a full root is no longer invisible.
- A path shared by several disk targets keeps the strictest requirement any target places on it, so an optional target can no longer mask a required one.
- The shutdown-watchdog test no longer races the Go scheduler, which was intermittently failing the quality gate and parking work unrelated to it.
archied — Other
- Messages persist the channel-native sender id.
- go-telegram/bot bumped to v1.27.0, fixing a streaming bug where the multipart
body could not be replayed and
sendMessage/editMessageTextfailed until the connection dropped.
archie-agent
- The per-task runtime picks up the new State Store task-log read contract, so the sandboxed agents share one log-reading path with the daemon and the dashboard.
[1.26.0] - 2026-09-17
archied
- fix(webui): publish per-identity forges so multi-identity task rows keep their links
- feat(config): add [scheduling] config block
- feat(configuration): translate [scheduling] into scheduling.EngineConfig
- feat(cronevents): adapt the events bus to scheduling.Sink
- fix(webui): count every chat front-end in the published projection
- fix(scheduling): respect configuration ownership
- feat(ratelimit): wire per-identity inbound rate limiting into the gateway
- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it
- fix(store): keep an empty binding secret empty so a partial edit cannot erase it
- fix(archied): stop advertising review_pr when no reviewer can run
- fix(daemon): carry kind/label routing bindings to the process that routes
- feat(configuration): add archied setup, the caller the first-run flow was built for
- fix(configuration): stop letting a secret value be set from the command line
- feat(configuration): let setup reference a secret without carrying its value
- fix(archied): disable a provider whose credential is missing instead of refusing to boot
- refactor(install): install.sh delegates config generation, and tests stop reading hand-written configs
- fix(daemon): guard binding dispatch loop against nil dispatcher/creator
- fix(webui): enforce CSRF/origin gate on binding and mapping mutations
- fix(secret): recover a panicking secret engine instead of crashing
- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone
- fix(email): stop dropping the first paragraph of plain-text bodies
- fix(logging): keep the live descriptor open across a failed rotation
- feat(configuration): report config keys no decode target consumed
- feat(archied): warn at boot when the config file has unrecognised keys
- feat(archied): wire the scheduling ticker engine at boot
- fix(agentworker): wire configured tool-result policy into worker's LoopRunner
- refactor(staterpc): delete the superseded single-token auth interceptor
- refactor(memory): delete the unreachable fence scrubber
- fix(channels): delete unreachable Telegram webhook delivery mode
- fix(gateway): delete unwired Router.Dangerous approval path
- refactor(gateway): delete orphaned SessionState goal/steer/queue machinery
- refactor(archied): delete the daemon's unused webui.Server and UI adapters
- refactor(tools): delete unreachable dispatch/gating engine
- feat(channels): wire chat.webhook route config through to the gateway
- refactor(tools): delete unreachable AST-based tool discovery
- refactor(tools): delete unused plugin-tool registration API from builtin.Registry
- feat(channels): wire ConfigSchema/ValidateConfig into a startup validation loop
- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)
- fix(curator): populate PassInput.Since with the prior pass time
- fix(memory): install the threat scanner the composition root never wired
- fix(staterpc): preserve marshal_error marker in eventDataJSON
- fix(gate): validate finding level and share the blocking threshold
- fix(scheduling): record a completed run so a recurring job stops re-firing every tick
- fix(releaseupdate): don't treat empty available as deferred
- fix(tools/provider/mcp): preserve MCP binary tool results for delivery
- refactor(gateway): share sensitive-key markers with webhookguard
- refactor(daemon): remove unreachable SQLite poll/drain path
- refactor(tools/mcp): delete unreachable MCP adaptation path
- fix(taskactions): resolve max_retries from the task's owning identity
- fix(daemon): forward configured MCP servers to task agents
- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path
- refactor(skillbuild): delete dead AugmentRegistry path
- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout
- refactor(binding): delete dead Matcher.Overlaps method
- refactor(forge): delete dead CreateIssue surface
- fix(mcp): cancel in-flight SSE reconnect on Stop
- fix(container): enforce MaxUptime lifetime cap with a timer
- refactor(store): use taskstate status constants in SQL
- fix(ui): unbreak binding approve and the two deletes, and centralise the client
- fix(tools): stop testing on the text of other files, and ungate contractaudit
- refactor(forge): delete the unwired RepliesAfter surface
- refactor(config): delete the two decoded-but-unread policy fields
This release is dominated by dead-code removal and the completion of the
scheduling capability. Roughly half the commits delete surfaces that no longer
had a caller: the unreachable SQLite poll/drain path, the unwired MCP
adaptation path, the AST-based tool discovery, the superseded single-token auth
interceptor, and several dead forge and binding methods. The
IncrementRetryCount State Store RPC is gone with them -- a breaking change to
the wire contract, accepted because nothing called it.
The cron/scheduling epic lands its remaining slices: the [scheduling] config
block, its translation into the engine's own settings, the events-bus sink
adapter, and the boot wiring that starts the ticker. A recurring job now records
a completed run, so it stops re-firing on every tick.
Operator-facing work: archied setup gives the first-run flow the caller it was
built for, configuration no longer accepts a secret value from the command line,
and a provider whose credential is missing is disabled rather than refusing to
boot. A secret engine that panics is now recovered instead of crashing the
daemon.
archie-agent
- feat(config): add [scheduling] config block
- fix(webui): count every chat front-end in the published projection
- fix(scheduling): respect configuration ownership
- feat(ratelimit): wire per-identity inbound rate limiting into the gateway
- fix(tools): judge the rm guard by base name so absolute paths cannot bypass it
- fix(daemon): carry kind/label routing bindings to the process that routes
- fix(config): deep-copy Image.Hosted/Image.Local in Config.Clone
- fix(logging): keep the live descriptor open across a failed rotation
- fix(agentworker): wire configured tool-result policy into worker's LoopRunner
- refactor(staterpc): delete the superseded single-token auth interceptor
- refactor(tools): delete unreachable dispatch/gating engine
- feat(channels): wire chat.webhook route config through to the gateway
- refactor(tools): delete unreachable AST-based tool discovery
- refactor(tools): delete unused plugin-tool registration API from builtin.Registry
- refactor(state): delete the dead IncrementRetryCount RPC (breaking change, accepted)
- fix(staterpc): preserve marshal_error marker in eventDataJSON
- fix(gate): validate finding level and share the blocking threshold
- fix(tools/provider/mcp): preserve MCP binary tool results for delivery
- refactor(tools/mcp): delete unreachable MCP adaptation path
- refactor(skill): delete dead Discover/DiscoverPlugins/Skill path
- refactor(skillbuild): delete dead AugmentRegistry path
- fix(builtin): bound read/edit filesystem work by DefaultToolTimeout
- refactor(binding): delete dead Matcher.Overlaps method
- refactor(forge): delete dead CreateIssue surface
- fix(mcp): cancel in-flight SSE reconnect on Stop
- fix(container): enforce MaxUptime lifetime cap with a timer
- refactor(forge): delete the unwired RepliesAfter surface
- refactor(config): delete the two decoded-but-unread policy fields
The runtime carries a smaller, more focused set of changes than the same
version's archied entry: agent-side tool-result policy is now wired into the
worker's loop, MCP binary tool results survive to delivery, the container
MaxUptime lifetime cap is enforced with a timer, and a scheduled run records
completion so it does not re-fire each tick.
Note that several bullets above name config, webui and ratelimit packages. Those
are attributed here by the release tool's package-closure rule (go list -deps
over the agent binary), not because the agent owns them; the substantive
runtime changes are the worker, MCP, container and scheduling fixes.
This entry also confirms the removal of the dead IncrementRetryCount State
Store RPC, which the agent reaches through staterpc rather than by calling it
directly.
[1.25.0] - 2026-09-15
archied
- fix(update): resolve releases without a checkout, and fail loudly when it cannot
- fix(update): back up the task store the daemon actually uses, or refuse
- fix(update): build each component from its own approved release tag
Components are independently versioned, so the newest archied/v* and
archie/v* tags usually sit on different commits. The installer required both
tags to resolve to one commit whenever both components changed, which refused
every update once the two newest releases diverged -- a deployment stuck on
1.22.0 could not take any update. Each component now builds from its own
approved tag.
archie-agent
- chore: no user-facing changes; versioned so the 1.25.0 release tags both components at the same commit
[1.24.0] - 2026-09-12
archied
Makes 1.23.0 deployable. That release split archied into separate processes,
but the self-updater still installed only the archied binary and restarted
only archied.service, so updating to it left the State Store, Gateway and UI
on the previous release. archied cannot boot without a reachable State Store,
so the update failed its health check and rolled back. Update to this release
rather than to 1.23.0.
If your host does not yet run the four units in
deployments/systemd-user-service.md, create them first: the updater now
refuses, naming what is missing, instead of installing binaries onto a host it
would leave broken.
- fix(update): install and cycle every process in the release
- fix(telegram): stop the relay corrupting identifiers and code
Also in this release, though outside the version-stamped package closure:
- ci(deploy): produce a complete distribution zip on every release. No zip was
built for v1.23.0 at all, and the zip omitted
archie-ui.
[1.23.0] - 2026-09-12
archied
Archied is no longer a single process. The State Store (archie-state-store)
now owns archie.db outright, the Gateway serves its contract over
authenticated gRPC, and the dashboard ships as a standalone UI Service
(archie-ui). Upgrading is not a binary swap: these processes must be running
and addressable before archied will start clean. See deployments/ for the
supported profiles.
archied — Service decomposition
- feat(contracts): add gateway service seams and protobuf toolchain
- feat(gateway): extract ChatContract service
- feat(gateway): delete in-process ChatContract path, make remote the only mode
- feat(gateway): authenticate the gRPC contract and allow off-loopback listeners
- fix(gateway): drop services.gateway.mode, remote is the only transport
- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)
- feat(state-store): stand up archie-state-store binary and own archie.db (#771)
- refactor(state-store): migrate capture/mapping/binding consumers to State Store (#772)
- refactor(state-store): migrate workflow/intake/task lifecycle consumers to State Store (#773)
- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)
- fix(state-store): task-scope container credentials, stream large capture lists, validate Update
- feat(archieui): standalone UI process over remote Gateway and State Store
- refactor(archied): cut the dashboard over to the archie-ui process
- refactor(ui): sever the archie-ui binary from every daemon runtime package
- refactor(archied): move the update relay to the process that owns updates
- refactor(archied): move webhook capture intake to the process that owns work intake
- feat(archieui): mount the capture intake receiver over the State Store
- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)
- refactor(store): move the producer-owned contracts to internal/contracts/store/v1
- feat(messaging): migrate gateway session persistence onto domain types
- feat(gateway): flip channel boundary onto messaging.Message
archied — Pull request review
- feat(gateway): operator-triggered PR review with selectable reviewer model
- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)
- feat(workflow): surface adversarial review findings on the PR body
- feat(workflow): review calibration, checked properties and style nits out of contract
- fix(archied): share one PR reviewer across channels; harden forge and worktree
- fix(workflow): order findings before footer; test the report stash
archied — Dashboard
- feat(webui): render configuration from a published snapshot
- feat(staterpc): carry the dashboard's configuration snapshot
- refactor(webui): take configuration off the dashboard server
- feat(webui): report which dashboard sections a process can serve
- feat(webui): deliver live dashboard events by polling the State Store cursor
- feat(webui): route dashboard task actions through the Gateway contract
- feat(gateway): give the dashboard operator its own task-action contract
- feat(webui): add /health and /health/detailed readiness endpoints (#717)
- fix(webui): distinguish refused vs broken task actions, handle 401 (#753)
archied — Daemon, gateway and workflow
- feat(archied): add shutdown watchdog that force-exits a hung graceful shutdown (#716)
- feat(archied): serve the daemon's own health endpoint
- feat(drain): honour external drain marker with instantiation epoch (#718)
- feat(gateway): wire progressive tool disclosure (bridge tools)
- feat(gateway): render workspace, managed repos and operator into chat env
- feat(gateway): add session_transcript tool for full JSON export
- feat(gateway): consolidate task actions and repair daemon default path
- feat(eda): thread Playbook ID/Version and DispatchInput task identity
- feat(worktree): Resume re-syncs a worktree onto its branch tip
- fix(staterpc): attach the bearer token to State Store streams
- fix(archieui): resolve service tokens from env, without requiring a config file
- fix(archied): initialize conversation persistence on daemon startup
- fix(archied): preserve channel turn ledger with remote gateway
- fix(gateway): share NATS and session ownership
- fix(update): probe the dashboard's real address after a self-update
- fix(store): migrate binding owner and repo columns
archie-agent
The agent runtime now reaches task state through the State Store gRPC contract
(STATE_STORE_URL/STATE_STORE_TOKEN, injected by the daemon) instead of the
NATS storerpc transport, which is deleted. Credentials handed to a task
container are scoped to that task rather than being the daemon's own token.
Running a 1.23.0 daemon against an older agent image will not work; rebuild or
pull the archie-agent image with this release.
- feat(state-store): generalize storerpc as the State Store gRPC contract (#770)
- feat(state-store): stand up archie-state-store binary and own archie.db (#771)
- refactor(state-store): cut daemon/Gateway over to the remote State Store (#774)
- fix(state-store): task-scope container credentials, stream large capture lists, validate Update
- fix(staterpc): attach the bearer token to State Store streams
- feat(staterpc): carry the dashboard's configuration snapshot
- refactor(workflow): relocate Task/Status/Source and define workflow.Store (#754)
- refactor(store): move the producer-owned contracts to internal/contracts/store/v1
- feat(contracts): add gateway service seams and protobuf toolchain
- fix(gateway): drop services.gateway.mode, remote is the only transport
- feat(forge): pull request review read surface (ListReviews/ListReviewComments/ReplyToReview)
- feat(gateway): operator-triggered PR review with selectable reviewer model
- feat(workflow): surface adversarial review findings on the PR body
- feat(workflow): review calibration, checked properties and style nits out of contract
- fix(workflow): order findings before footer; test the report stash
- fix(archied): share one PR reviewer across channels; harden forge and worktree
- feat(worktree): Resume re-syncs a worktree onto its branch tip
- feat(telegram): support secret refs for bot tokens (#705)
- feat(gateway): wire progressive tool disclosure (bridge tools)
- feat(archied): serve the daemon's own health endpoint
- feat(archieui): standalone UI process over remote Gateway and State Store
- refactor(archied): move webhook capture intake to the process that owns work intake
- refactor(ui): sever the archie-ui binary from every daemon runtime package
- fix(archieui): resolve service tokens from env, without requiring a config file
[1.22.0] - 2026-09-03
archied
- feat(telegram): support secret refs for bot tokens (#705)
- fix(update): make daemon rollback schema-safe (#704)
- fix(archied): preserve ephemeral gateway ports (#707)
- fix(webui): bound log limit parsing and add endpoint regression coverage (#706)
- fix(deps): upgrade x/crypto to v0.56.0 for security fixes (#708)
[1.21.0] - 2026-09-03
archied
- feat(workflow): make kind-to-workflow routing YAML-overridable
- feat(workflow): route arbitrary forge labels to workflows via playbook YAML
- feat(workflow): load kind/label bindings from multiple playbook directories
- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive
- feat(eda): Module position first slice -- registry + side-effect-free log kind
- feat(eda): CEL expression environment (compile/validate at load, evaluate at dispatch)
- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch
- fix(skillcurator): document and scope the intentional nilerr in reviewOne
- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch
- feat(webui): bindings dashboard UI; fix app-wide Preact render regression
- fix(binding): split ValidateForUpdate so edits can preserve the secret
- refactor(ui): extract Pill to ui/src/base/, closing archie-core-mlro
- refactor(eda): extract helpers to satisfy cyclop/gocognit gates
- fix(webui): stretch HEALTH row cards to equal height
- fix(eda): make playbook key collision reporting deterministic
- fix(gateway): split /status (health) and /tasks (work) apart
archie-agent
- feat(workflow): make kind-to-workflow routing YAML-overridable
- feat(workflow): route arbitrary forge labels to workflows via playbook YAML
- feat(workflow): load kind/label bindings from multiple playbook directories
- fix(extract): regenerate stale Yaegi symbol tables; fix wfextract directive
- feat(eda): Module position first slice -- registry + side-effect-free log kind
- feat(eda): playbook document + event coordinator, single-action workflow-kind dispatch
- fix(binding): add Owner/Repo pin, fixing multi-repo dispatch
- fix(binding): split ValidateForUpdate so edits can preserve the secret
- refactor(eda): extract helpers to satisfy cyclop/gocognit gates
- fix(eda): make playbook key collision reporting deterministic
[1.20.0] - 2026-09-03
archied
- fix: baseline gate repair (go test ./... -count=1)
- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler
- feat(image): define provider-neutral image capability contract and config
- fix(channels): call MarkRunning once a channel is actually up
- fix(workflow): stop discarding baseline-fix commits as 'no changes'
- fix(webui): wire the Logs page to per-task attempt-log detail
- fix(workflow): net cache hits from token totals, trim gate-retry output
- feat(workflow): dynamic triage instead of defaulting every task to implement
- fix(gateway): stop SOUL from forging the prompt invariant tags
- fix(curator): stop curator actions from serializing a zero timestamp
- feat(webui): hand-author the configuration field descriptor catalog
- feat(webui): attach the config field schema to GET /api/config
- feat(webui): render scalar config sections generically from the schema
- feat(webui): surface allow_concurrent/max_retries/review_enabled on the repositories card
- feat(webui): inline editing for per-repo allow_concurrent/max_retries/review_enabled
- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated
- fix: resolve golangci-lint funlen, nilerr, and empty branch issues
- feat(store): encrypt playbook binding secrets at rest
- feat(webhook): harden captured payload redaction
- fix(store): satisfy makezero when building cipher payload
- feat(webui): refactor chat module to Preact component and add unit tests
archie-agent
- fix: baseline gate repair (go test ./... -count=1)
- fix(logging): propagate bound slog attrs to wrapped handler in FeedHandler
- feat(image): define provider-neutral image capability contract and config
- fix(workflow): stop discarding baseline-fix commits as 'no changes'
- fix(workflow): net cache hits from token totals, trim gate-retry output
- feat(workflow): dynamic triage instead of defaulting every task to implement
- feat(webui): playbook bindings -- matcher + mapping + workflow, HMAC-gated
- feat(store): encrypt playbook binding secrets at rest
- fix(store): satisfy makezero when building cipher payload
[1.19.10] - 2026-09-02
archied
- feat(curator): session-memory curator reference implementation
[1.19.9] - 2026-09-02
archied
- feat(memory): typed memory engine contract, registry, and registrar
- feat(memory): builtin engine implementing the domain/memory contract
- feat(config): config surface for memory engine selection
- feat(daemon): wire the domain/memory engine registry at boot
- feat(curator): bind curators to memory engines
- fix(config): reject memory.provider instead of silently ignoring it
- feat(curator): skill curator reference implementation
archie-agent
- feat(config): config surface for memory engine selection
[1.19.8] - 2026-09-02
archied
- fix(update): drop dev-facing wording from the unconfirmed-update message
- fix(telegram): stop adjacent rich blocks from rendering glued together
- fix(telegram): send undelivered-media fallback after finalize as its own message
[1.19.7] - 2026-09-02
archied
- fix(logging): make Tail/Page allocation bound explicit for CodeQL
archie-agent
- fix(logging): make Tail/Page allocation bound explicit for CodeQL
[1.19.6] - 2026-09-02
archied
- fix(build): stamp gatewayVersion/runtimeVersion in the right package
[1.19.5] - 2026-09-01
archied
- feat(webui): dashboard-aware chat — Archie sees the page, points you there
- fix(telegram): drop retry_after bandaid, bump go-telegram/bot to v1.24.0
- feat(curator): track and expose recent activity per curator
- fix: go.mod bumped to 1.27.0 and stupid tests removed
- refactor: remove unnecessary AI-generated scaffolding
- refactor: go modernisation fixes
- refactor: remove unused Operator param.
- fix(gateway): fix broken system prompt template and scrub real telegram ID from tests
- fix(plugin): add missing CLAUDE.md reference to plugin engine rule
- fix(app): repoint archied wiring contract test at internal/app/archied
- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet
- fix(config): standardize Provenance to pointer receivers (recvcheck)
- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui
- fix(app): repoint capability-host wiring contract test at internal/app/archied
- refactor(lint): extract more helpers to clear nestif/gocyclo findings
- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult
- refactor(lint): split TurnRunner.Run and dispatchLocal further
- refactor(lint): extract markdownBlockParser and list/quote helpers in richblocks.go
- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization
- fix(lint): noctx fixes and dead-code cleanup
- feat(workflow): adversarial self-review stage before PR open
archie-agent
- feat(tasks): allow rejecting a task from any non-terminal state
- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta
- fix: go.mod bumped to 1.27.0 and stupid tests removed
- refactor: go modernisation fixes
- refactor: remove unused Operator param.
- fix(plugin): add missing CLAUDE.md reference to plugin engine rule
- fix(app): repoint archied wiring contract test at internal/app/archied
- refactor(agentexec): use ai-sdk NewTypedTool for pluginToolSet and scriptToolSet
- refactor(lint): reduce cyclomatic/cognitive complexity in tools, workflow, webui
- fix(app): repoint capability-host wiring contract test at internal/app/archied
- refactor(lint): extract more helpers to clear nestif/gocyclo findings
- refactor(lint): split AgentStage.Stage into resolveModel/buildRequest/handleResult
- refactor(lint): extract Apply/findWalkVisitor helpers; go fix modernization
- fix(lint): noctx fixes and dead-code cleanup
- feat(workflow): adversarial self-review stage before PR open
[1.19.4] - 2026-08-28
archied
- refactor(telegram): render replies as structured rich blocks
[1.19.3] - 2026-08-28
archied
- feat(tasks): serve the lifecycle presentation catalog from /api/task-meta
- feat(dashboard): render task actions, statuses and filters from the server catalog
[1.19.2] - 2026-08-28
archied
- feat(tasks): allow rejecting a task from any non-terminal state
[1.19.1] - 2026-08-27
archied
- fix(telegram): keep Markdown headings/lists as blocks and strip Markdown on plain fallback
[1.19.0] - 2026-08-28
archied
- feat(logging): cursor pagination and filtering for task_logs
- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29
[1.18.0] - 2026-08-28
archied (released 2026-08-25)
- Fix concurrent chat-turn claims so SQLite writer contention no longer leaks as
SQLITE_BUSY. - Make task timelines operationally useful with stage outcomes, durations, retry context, and durable per-stage token economics.
- Return canonical repository, issue, and pull-request URLs for each task's owning GitHub or Gitea identity.
- Preserve per-identity commit attribution and real model context limits across daemon-to-worker dispatch.
archie-agent
- feat(logging): cursor pagination and filtering for task_logs
- build(deps): upgrade github.com/samcharles93/ai-sdk to v0.1.29
[1.17.1] - 2026-08-25
archied
- fix(update): remove source checkout dependency
- fix(gateway): make UUIDv7 session references unambiguous
[1.17.0] - 2026-08-25
archied
- fix(webui): add nil receiver guard to Server.trustForwardedHeaders
- fix(chat): restore transcript and update replay
archie-agent
- Compact task history against the selected model's real context capacity without imposing a token cap.
- Preserve completed steps and billed usage when a later provider call fails; failed compaction now keeps the original history and continues.
- Persist detailed agent-stage usage through the daemon-owned store before lossy live event fan-out.
- Apply configured or forge-derived author and committer identity to sandboxed task commits.
[1.16.1] - 2026-08-25
archie-agent
- fix(agentworker): reconcile task clone ownership after commits
[1.16.0] - 2026-08-25
archied
The agent can hand you a file, and the dashboard works behind a reverse
proxy. Media delivery was fetch-by-URL only, so a file the agent produced
locally — a transcript, a log dump, a screenshot — was passed to Telegram as
a URL it could not fetch: the send did nothing and reported success. The new
send_file tool plus upload-by-reader delivery closes that, and every layer
that cannot deliver now says so rather than staying silent. Dashboard
mutations behind a TLS-terminating proxy were refused as cross-origin;
forwarded headers are now honoured, but only under an explicit opt-in that is
off by default.
- feat(telegram): deliver a local file as an uploaded attachment, choosing
upload-by-reader or fetch-by-URL per attachment;
send_fileresolves paths under the same confinement policy the read tool applies, so sending cannot reach what reading cannot - feat(gateway):
task_actionchat tool for operator task management — abandon, archive, retry, stop, cancel, approve and reject from chat, on the same action path and state machine as the dashboard - fix(webui): validate mutation
Originagainst the effective external scheme and host.X-Forwarded-Proto/-Hostare honoured only whenweb.trust_forwarded_headersis set, which is off by default and safe only behind a proxy that overwrites or strips untrusted forwarded headers - fix(webui): report a local file the dashboard chat cannot upload as
undelivered instead of dropping the event, which had reproduced the exact
silent non-delivery
send_filewas built to end - fix(daemon): detach terminal state transitions and cleanup from a cancelled context, so a stopped task still records its outcome
archie-agent
Version realigned with archied. This release jumps from 1.9.9 to 1.16.0
to put the two components on matching numbers; there are no 1.10-1.15 agent
releases. It clears the accumulated runtime backlog in one cut rather than
bundling it as a rider on a later change, so the list below spans several
weeks of work rather than one session's.
Highlights:
- feat(nats): run an embedded server when no external NATS is configured, and expose the embedded broker to managed task workers
- feat(deployment): default to managed NATS workers; the daemon requires a full-task worker handoff and the legacy in-process, subprocess and single-stage execution paths are gone
- feat(forge): GitHub webhook receiver for immediate issue dispatch, with dedup regression proof; unbound webhook events are stored retention-bounded
- feat(webui): payload field mapping -- bind JSON paths to named fields and preview before saving
- feat(scheduling): ticker engine with configurable interval and pools
- feat(storage): persist agent project state
- feat(agent): stamp archie-agent's build and report it back to the daemon
- feat(tools):
generate_videovia MiniMax, gated behind config, andMultimodalResult.URLsfor remote-hosted media - feat(workflow): define the adversarial-review findings contract
Fixes:
- fix(worktree): bind publication to dispatch grants; reset retries to a
pristine base; reject diffs without a merge base; clean untracked files when
.gitis a gitdir file; post-push metadata resilience, cancellation and branch naming - fix(container): persist the npm cache for per-task MCP servers
- fix(agentexec): recover omitted finish calls
- fix(agentworker): move JSONL decode into storage, unblocking CI
- fix(telegram): compact tool output and drop turn caps
- fix(webui): give dashboard-initiated updates a phase-2 report; restore the provider gate and dashboard token accounting
- refactor: remove dead
BasePlatformAdaptercode and legacy execution paths
Shared with archied 1.16.0 (these packages are in both closures):
- feat(telegram): send local files as uploads, not fetchable URLs
- fix(webui,sendfile): close three holes the adversarial review found
- fix(webui): validate mutation Origin against the effective external scheme
[1.15.0] - 2026-08-24
archied
Autonomous workflows now have exactly one production execution path. Every
task is handed complete to a scoped archie-agent container over core NATS;
archied no longer runs an agent loop in-process. Embedded NATS is the
default and generates a per-start token, binding to the resolved Docker bridge
so managed workers can reach it; external NATS changes only broker placement.
The legacy [agent] section and containers.enabled still decode for
migration but can no longer select an execution path, and a reloaded
nats.url is logged as requiring a restart. Operators upgrading from a
agent.mode = inprocess configuration get the managed-worker topology
automatically; see deployments/ for the supported profiles.
- feat(nats): expose the embedded broker to managed task containers behind a generated per-start credential
- fix(daemon): park before worktree access when the container pool or task transport is unavailable, rather than silently executing locally
- refactor(agentexec): remove the in-process, subprocess and single-stage execution paths
- fix(worktree): report a successful push as successful even when writing local upstream tracking metadata afterwards fails, so a published branch no longer parks the task as failed
- fix(worktree): honour context cancellation in
CommitAll, so a cancelled task can no longer stage or commit - fix(daemon): remove the worktree when a task completes with no changes, which previously leaked a full clone per no-change task; parked worktrees are still retained for post-mortems
- fix(worktree): derive the branch prefix from the issue title before falling back to labels, matching the documented contract
- fix(worktree): clean untracked files when
.gitis a gitdir file - fix(agentexec): recover agents that end a turn without the required finish call
- feat(scheduling): ticker engine with a configurable interval and pools
- fix(telegram): keep tool-call context when compacting tool output (#609)
- feat(workflow): add the adversarial-review findings contract, where only a confirmed finding blocks and "review found nothing" is distinct from "review did not run" (contract only; no review stage runs yet)
[1.14.0] - 2026-08-23
archied
- fix(telegram): compact tool output and drop turn caps
- fix(update): install only approved components
[1.13.0] - 2026-08-23
archied
- fix(telegram): render tool progress as bounded code blocks
[1.12.0] - 2026-08-23
archied
- fix(webui): give dashboard-initiated updates a phase-2 report
- feat(agent): stamp archie-agent's build and report it back to the daemon
- feat(releaseupdate): enrich components with install type and reference
- feat(webui): surface per-component update status on /api/version and Configuration
[1.11.1] - 2026-08-23
archied
- fix(update): wire Telegram personas and survive callback cancellation
- fix(webui): theme the Workflows 'Start work' form controls
[1.11.0] - 2026-08-23
archied
- feat(forge): make webhook intake observable and deduplicate concurrent delivery
- fix(telegram): preserve code fences across message splits
- fix(gateway): replay completed-duplicate turns with their tool activity
- feat(storage): persist agent project state across sessions
- fix(container): persist npm cache for per-task MCP servers
- fix(worktree): bind publication to dispatch grants, reset retries to a pristine base, and reject diffs without a merge base
- feat(media): deliver generated media through Telegram with link fallback in the dashboard
- feat(tools): generate videos through MiniMax, gated by provider configuration
[1.10.0] - 2026-08-22
archied
- feat(forge): GitHub webhook receiver for immediate issue dispatch
- feat(webhookguard): shared HMAC, rate-limit, and redaction mechanics
- feat(nats): run an embedded server when no external NATS is configured
- feat(capture): store unbound webhook events, retention-bounded
- feat(webui): event inspector -- see captured payloads in the dashboard
- feat(webui): payload field mapping -- bind JSON paths to named fields, preview before saving
- fix(webui): stop the capture live-event notification duplicating payloads into the unbounded events table
- fix(update): verify an update took effect instead of trusting the report (#530)
- fix(daemon): refuse to poll on an empty label-trigger match (#529)
- fix(gateway): stop persona from asserting unverified claims as fact (#528)
- fix(gateway): stop ClaimTurn's insert-race branch losing its own retry read
- fix: restore provider gate and dashboard token accounting
- fix: address simple findings from a repo-wide golangci-lint sweep
[1.9.11] - 2026-08-19
archied
- fix(mcp): persist npx package cache across daemon restarts
[1.9.10] - 2026-08-19
archied
- feat(update):
/updatenow streams live progress while an update installs, reports a clear version summary (previous/installed, daemon/agent) once the build succeeds, and automatically rolls back and reports the outcome if the restarted daemon fails its post-update health check
[1.9.9] - 2026-08-18
archied
- fix(telegram): drain live renderer in concurrency test
archie-agent
- chore: no user-facing changes
[1.9.8] - 2026-08-17
archied
- chore: no user-facing changes
archie-agent
- chore: no user-facing changes
[1.9.7] - 2026-08-17
archied
- chore: no user-facing changes
archie-agent
- chore: no user-facing changes
[1.9.6] - 2026-08-16
archied
- fix(update): stamp install type and bound retry backoff
archie-agent
- chore: no user-facing changes
[1.9.5] - 2026-08-16
archied
- refactor(archied): decompose the daemon bootstrap into phased wiring (no behaviour change; splits the ~950-line run() into focused setup phases so complexity linting passes)
- refactor(archied): extract the config overlay boot helper and thread context through chat gateway setup
- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity
- fix(tools): avoid predeclared
maxnames - fix(email): use context-aware test networking
- fix(indexing): remove the unused code search test runner
- fix(tests): use contexts and type assertions in overlay and gateway tests
- docs(architecture): document the memory engine family
archie-agent
- refactor: decompose the daemon bootstrap into phased wiring (no behaviour change; complexity-driven restructure)
- refactor(tools): split the read executor and flatten nested config/tool fallback logic to lower complexity
- fix(tools): avoid predeclared
maxnames
[1.9.4] - 2026-08-15
archied
- feat(gateway): polish /status command response format
- fix(telegram): preserve URL boundaries in responses
archie-agent
- chore: no user-facing changes
[1.9.3] - 2026-08-15
archied
- fix(webui): scroll selected command into view on keyboard navigation
- fix(logging): resolve error attrs to their message string, not {}
- feat(agentexec,workflow): surface tool calls on the task timeline
archie-agent
- fix(logging): resolve error attrs to their message string, not {}
- fix(agentworker): back off before refetching a nak'd stage message
- feat(agentexec,workflow): surface tool calls on the task timeline
[1.9.2] - 2026-08-15
archied
- fix(worktree): force checkout so retry recovers from a dirty worktree
archie-agent
- fix(worktree): force checkout so retry recovers from a dirty worktree
[1.9.1] - 2026-08-15
archied
- fix(agentworker): forward workflow events across the NATS worker boundary
- fix(webui): filter turn_completed noise from the Live Activity SSE feed
- feat(releaseupdate): stamp install type at build time, fail closed on unknown
archie-agent
- fix(agentworker): forward workflow events across the NATS worker boundary
[1.9.0] - 2026-08-15
archied
- fix(webui): style tool-call failure from a structured field, not a string prefix
- fix(config,webui): make show_tool_calls one cross-channel setting
- fix(telegram): guarantee no message is stranded on gateway stop/restart
- fix(telegram): use NewRequestWithContext to satisfy noctx
- refactor(webui): decompose handleSSE to cut cognitive complexity
archie-agent
- fix(agent): resolve git dubious-ownership in sandbox containers
- feat(agent): mark the mounted worktree as a git safe directory
- fix(agent): route git safe.directory setup through markWorktreeSafe
- feat(chat): show tool calls inline and stream replies into one message
- refactor(agent): move worker runtime into application layer
- fix(config,webui): make show_tool_calls one cross-channel setting
[1.8.0] - 2026-08-15
archied
- feat(archied): add -version so the installed build can be read from a shell
- fix(webui): rebuild the Configuration page layout so values stop colliding
- fix(webui): size Configuration key/value lists to their own content
- fix(webui): keep Configuration rows full width, hug only the label column
- fix(webui): cap and centre the Configuration page instead of its lists
- fix(webui): preserve encoded redirect path characters
- feat(chat): show tool calls inline and stream replies into one message
- fix(chat): harden inline tool call streaming
- refactor(agent): move worker runtime into application layer
- fix(telegram): harden live-reply delivery against /stop and multi-byte content
- fix(telegram): keep tool activity visible and mark failed/empty turns
- fix(config): de-duplicate disabled-forge predicate, export ForgeDisabled
[1.7.0] - 2026-08-10
archied
- fix(build): install ripgrep where grep.go actually needs it on PATH
- fix(webui): Send button no longer passes its click event to sendMessage
- feat(webui): Enter sends, Shift+Enter inserts a newline
- fix(chat): stop showing raw 501 banner for unconfigured update-check
- fix(chat): give chat page a real height budget instead of a floor
- fix(workflow): carry gate output into the baseline park error
- feat(logging): add a per-task log sink
- feat(agentexec): publish agent-side logs to the task's system subject
- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed
- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool
- refactor(gateway): persist conversations in sqlite
- refactor(store): replace legacy persistence with SQLite
- fix(webui): tighten configuration KV row spacing
- fix(gateway): harden session recovery paths
- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe
- feat(config): SIGHUP-triggered reload with requires-restart warnings
- fix(config): share one config Holder between daemon and dashboard; re-apply model catalog on reload
- fix(config): complete the reloadable allowlist and pin it against ForTask
- feat(config): runtime config overlay store, PATCH /api/config, and the
--no-config-overlayrecovery flag - feat(webui): inline config editing on the Configuration page
- feat(config): surface overlay state, shadowed keys, and per-row reset
- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state
- fix(config): preserve nil slices in Clone to avoid spurious reload warnings
[1.6.0] - 2026-08-09
archied
- feat(gateway): tool-approval gate, session tools for chat, and /delete command
- fix(webui): close open-redirect in dashboard token-exchange handler
- feat(gateway): make chat turns durable and idempotent
- feat(webui): lifecycle-safe task controls with atomic retry and archive
- feat(config,channels): format-neutral config resolution and truthful channel state
- feat(logging,workflow): daemon log feed and executable workflow registry
- fix(store,gateway): taskstate constants and mobile jump-to search
- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams
- fix(ui): hide inactive chat command menu
[1.5.0] - 2026-08-08
archied
- feat(curator): engine family contract, registry, and runtime
- feat(curator): trigger accounting — primary-input wake path
- feat(setup): interactive setup steps with a TTY-gated prompter
- feat(webui): rebuild the dashboard and add chat
- feat(daemon): identity-scoped isolation plus gateway session titles and /delete
- feat(logging): optional rotating log file
- feat(configuration): export Validate for the setup flow
- fix(gateway): durable message identity with a SQLite store
- fix(gateway): consistent message ordering and paged search
- fix(gateway): stop /compress destroying history it should have kept
- fix(gateway): do not answer a redelivered message twice
- fix(gateway): claim the session slot before writing it, not after
- fix(gateway): keep /topic off from poisoning the session cache
- fix(gateway): resolve the most recently active session, not an arbitrary one
- fix(gateway): give branch-inherited messages their own identity
- fix(gateway): make both backends agree on newest-first
- fix(store): honour the transition guard in production persistence
- fix(store): move ID counters away from the reserved metadata namespace
- fix(store): surface task timestamps and tag the summary structs
- fix(telegram): pause the update loop when rate limited
- fix(memory): fail startup on an unusable memory directory
- fix(tools): let an optional provider fail without taking the daemon down
- fix(tools): report a cancelled find walk as an error, not empty results
- fix(worktree): name the missing forge credential when a push fails
- fix(tomlwrite): recognise table headers carrying a trailing comment
- fix: close the duplicate-work loop and the dead paths around it
- perf(tools): drop the embedded ripgrep binaries
- refactor: one definition of what approving or declining a task means
- refactor: move workflow into its own domain
[1.4.1] - 2026-07-31
archied
- fix(catalog): match SDK provider fallback
[1.4.0] - 2026-08-10
archied (released 2026-07-31)
- fix(secrets): wire provider credentials through engines
archie-agent
- feat(gateway): tool-approval gate, session tools for chat, and /delete command
- feat(gateway): make chat turns durable and idempotent
- feat(webui): lifecycle-safe task controls with atomic retry and archive
- feat(logging,workflow): daemon log feed and executable workflow registry
- fix(store,gateway): taskstate constants and mobile jump-to search
- feat(webui,gateway): wire config, channel, log-feed, and work-intake seams
- fix(build): install ripgrep where grep.go actually needs it on PATH
- fix(workflow): carry gate output into the baseline park error
- feat(logging): add a per-task log sink
- feat(agentexec): publish agent-side logs to the task's system subject
- feat(daemon): consume agent system logs into per-task sinks and the dashboard feed
- feat(webui,gateway): add /api/tasks/{id}/logs endpoint and task_logs chat tool
- refactor(store): replace legacy persistence with SQLite
- refactor(daemon,webui): make Daemon.Cfg and webui.Server.Cfg reload-safe
- feat(config): SIGHUP-triggered reload with requires-restart warnings
- feat(config): surface overlay state, shadowed keys, and per-row reset
- fix(config): close review blocker on the PATCH path; deep-copy snapshots; atomics for shared state
- fix(config): preserve nil slices in Clone to avoid spurious reload warnings
[1.3.1] - 2026-07-31
archied
- fix(telegram): omit empty model picker markup
[1.3.0] - 2026-08-08
archied (released 2026-07-31)
- fix(memory): replace framework-specific names with generic equivalents
- feat: unify provider and model selection
archie-agent
- feat(curator): engine family contract, registry, and runtime
- feat(curator): trigger accounting — primary-input wake path
- feat(logging): optional rotating log file
- feat(daemon): identity-scoped isolation
- fix(secrets): wire provider credentials through engines
- fix(store): surface task timestamps and tag the summary structs
- fix(tools): let an optional provider fail without taking the daemon down
- fix(tools): report a cancelled find walk as an error, not empty results
- fix(worktree): name the missing forge credential when a push fails
- fix: close the duplicate-work loop and the dead paths around it
- perf(tools): drop the embedded ripgrep binaries
- refactor: one definition of what approving or declining a task means
- refactor: move workflow into its own domain
[1.2.0] - 2026-07-31
archied
- feat: add MCP client capabilities to archied and archie-agent
- fix: handleSummary ignores errors from WorkflowStats/StageStats/TokensByDay
- feat: establish Archie identity and use stable callback tokens
- refactor(telegram): keep one model selector command
- fix: handleSSE silently swallows EventsSince backlog fetch errors
- fix: Transition() ignores
fromstatus guard, allowing lost updates - fix: skillscript.Run ignores context, cannot be canceled/timed out
- feat(telegram): report installed component versions
- feat(telegram): add approved component updates
- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup
- feat(chat): real system prompt for Archie — identity, tools, env
- feat(indexing): port tau's codesearch workspace index
- fix(indexing): surface index config properly and stop silent degradation
- refactor(worktree): replace git shell-out with go-git v6
- fix(worktreerpc): bound handler contexts and drop the git binary from tests
- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries
- refactor: route tasks on a typed kind, not forge labels
- fix(natsrpc): make RegisterAll wait for the server to see subscriptions
- refactor(config): move loading into infrastructure/configuration
- fix(telegram): publish all executable session commands in menu and help
- fix(telegram): publish the restored gateway commands
- refactor: add internal/eventbus as the broker-neutral messaging contract
- fix(chat): operator name from config, session wiring, prompt rules
- feat(tools): lift tau's file and shell tools into the tool registry
- feat: make /stop cancel the running chat turn
- fix: kill the whole process group when a shell command is cancelled
- feat: refuse unrecoverable shell commands
- feat: make /stop reach running agent tasks
- fix(chat): temper prompt brevity rules with warmth
- fix: use errors.Is/As for context errors and cleanup
- fix(grep): distinguish ripgrep exit 1 from a failed search
- fix(archied): disable the forge on a missing credential, not the daemon
- fix: restore /model parsing and close the 6d4e0be autofix audit
- feat: embed config.example.toml and add comment-preserving TOML writer
- fix(docker): install unzip and Node 24 so MCP servers can start
- fix(docker): slim both images and repair unreachable Go tooling
- fix(container): write the task boot brief under .git
- fix(telegram): drop pending updates before long polling
archie-agent
- feat: add MCP client capabilities to archied and archie-agent
- fix: Transition() ignores
fromstatus guard, allowing lost updates - fix: skillscript.Run ignores context, cannot be canceled/timed out
- fix: LoadDir: no timeout around Yaegi Eval can hang daemon startup
- fix(indexing): surface index config properly and stop silent degradation
- refactor(worktree): replace git shell-out with go-git v6
- fix(worktreerpc): bound handler contexts and drop the git binary from tests
- refactor(nats): rebuild as infrastructure/eventbus/nats with real boundaries
- refactor: route tasks on a typed kind, not forge labels
- fix(natsrpc): make RegisterAll wait for the server to see subscriptions
- refactor(config): move loading into infrastructure/configuration
- refactor: add internal/eventbus as the broker-neutral messaging contract
- feat(tools): lift tau's file and shell tools into the tool registry
- feat: make /stop cancel the running chat turn
- fix: kill the whole process group when a shell command is cancelled
- feat: refuse unrecoverable shell commands
- feat: make /stop reach running agent tasks
- fix: use errors.Is/As for context errors and cleanup
- fix(grep): distinguish ripgrep exit 1 from a failed search
- fix(docker): slim both images and repair unreachable Go tooling
- fix(container): write the task boot brief under .git
[1.1.0] - 2026-07-27
archied
- feat: add the Telegram gateway with persistent sessions, topic-thread support, streamed rich replies, typing indicators, and Markdown rendering
- feat: add
/spawn,/approve, and/cancelfor chat-driven task control - feat: provide a comprehensive
/helpguide whose command list stays aligned with Telegram's published menu and Archie's executable command surface - feat: add
/providerand provider-filtered/modelselectors that switch the provider and model used by subsequent live chat turns - feat: include the active provider and full model reference in
/status - feat: notify authorized Telegram users once when a newly tagged component release is installed
- feat: add
/restartto reload and relaunch the Telegram gateway without interrupting in-flight daemon tasks - feat: add deny-by-default Telegram sender authorization and native command-menu publication
- feat: connect Desktop Commander through Archie's managed MCP client so chat can use workspace file and process tools
- feat: add multi-identity daemon configuration, persona routing, an email channel, and webhook platform support
- feat: add durable task, session, message, and memory persistence
- feat: add memory synchronization, prefetch, context scrubbing, threat scanning, and built-in memory tools
- feat: add tool guardrails, classification, budgets, availability filtering, and disclosure controls
- feat: add feature-based YAML configuration with
conf.doverlay loading - feat: add typed secret-engine registration and Yaegi extension support
- fix: reject unknown slash commands locally instead of allowing the LLM to fabricate command behavior
- fix: publish Telegram commands to default, private-chat, and group-chat scopes so stale commands inherited with the bot token cannot shadow Archie's menu
- fix: drain the SDK's full event stream so streamed Telegram replies cannot deadlock
- fix: use standard newline-delimited JSON framing for MCP stdio clients
- fix: make MCP stdio shutdown and timeout handling race-safe
- fix: restore legacy
[forge].token_envcompatibility and required container environment passthrough - fix: make the agent-container Docker network explicitly configurable
archie-agent
- feat: add streamed agent execution with typed message events
- feat: add MCP client transports and managed tool-provider discovery
- feat: add memory context scrubbing and normalized memory tool schemas
- feat: add plugin metadata extraction from
metadata.archie.plugins - feat: add configurable container networking for daemon-launched runtimes
- fix: preserve valid UTF-8 when clipping runtime output
- fix: make MCP stdio lifecycle, retries, and timeout handling race-safe
- fix: enforce a zero-finding lint and vet baseline
[1.0.0] - 2026-07-22
archied
- feat: ship the resident forge-polling daemon, deterministic workflow engine, isolated worktrees, quality gates, Gitea integration, Docker/NATS worker split, plugin loading, and skills support
- feat: publish
archiedandarchie-agentcontainer images to the Gitea registry
archie-agent
- feat: ship the isolated agent runtime, NATS RPC boundary, workflow execution, skills, and plugin support
- feat: publish the
archie-agentcontainer image to the Gitea registry