Skip to content
Archiedocscookbooknewssign in

    News

    1.50.0

    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.
    • /update in 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

    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

    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

    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

    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

    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

    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

    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. The update_check_command and update_install_command keys under [chat.telegram] are no longer read; remove them from config.toml.
    • archie-update-install run from a shell now reads ~/.config/archie/env, so the pre-update backup of the bundled database no longer fails with no password supplied. Run it with --auto to install the newest release.

    1.47.3

    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

    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.

    Page 2 of 10