Skip to content
Archiedocscookbooknewssign in

    News

    1.15.0

    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 .git is 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

    archied

    • fix(telegram): compact tool output and drop turn caps
    • fix(update): install only approved components

    1.13.0

    archied

    • fix(telegram): render tool progress as bounded code blocks

    1.12.0

    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

    archied

    • fix(update): wire Telegram personas and survive callback cancellation
    • fix(webui): theme the Workflows ‘Start work’ form controls

    1.11.0

    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

    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

    archied

    • fix(mcp): persist npx package cache across daemon restarts

    1.9.10

    archied

    • feat(update): /update now 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

    archied

    • fix(telegram): drain live renderer in concurrency test

    archie-agent

    • chore: no user-facing changes

    Page 8 of 10