3dfc5394bd8e00e5a54fbed57bb48417b0e5f122
Installing a release and approving a gated action are things you do to the deployment, not things you say to Archie. They lived in the chat surface only because that is where they were first built, and in a launcher panel a few hundred pixels wide they crowded out the conversation (archie-core-tf20). Both are new cards in ui/src/settings/operator-cards.jsx, wired into Configuration beside the read-only UpdateStatusCard that was already there. Behaviour is unchanged from the chat panel, including accepting both the capitalised and lowercase checkpoint field shapes the API has returned. A 501 from either endpoint renders no card at all rather than an error: a deployment that does not wire update-checking should show nothing, which is what the dev stack does. Reload Telegram deliberately did not move. It was never an API call -- the old handler sent the "/restart" chat command as a message -- so a Configuration button would have to post a chat message to reach the adapter. It stays as /restart in the palette until the cross-process restart RPC exists (archie-core-ry4k); archie-core-oif3 tracks landing it here afterwards.
fix(ui,gateway): load the served lifecycle vocabulary, and make the page registry match the routes (#890)
feat(messaging): Messaging Service operator surface, chat report rendering, and the diff-cap config fix (#899)
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%