Skip to content
Archiedocscookbooknewssign in

    Release 1.36.0

    News ·

    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.ts client the dashboard itself calls, so an agent and a person exercise one path rather than two.
    • archie-ui cannot 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 build passed the installtype stamp for three of six commands, so archie-messaging, archie-state-store and archie-ui were built without it. An unstamped binary reports unknown and the self-update path refuses rather than guesses, which is how an operator ends up unable to update with install type is unknown and no way forward. All six are stamped now, and a test reads the build task and fails naming any command line that omits it.