cb147b7a37160cbc4f84085bef7a02cc497a6446
Allowlist (16.33). telegram.New was called with a nil allowlist and isChatAllowed returned true whenever the list was empty, so any Telegram user who found the bot could talk to it; AllowedChatIDs was not plumbed into config, so there was no way to close it. Chat tools run with the daemon's own authority, so this had to be fixed before wiring any real tools to the chat agent. Now chat.telegram.allowed_user_ids configures it and an empty list denies everyone: a bot handle is public, so failing open is not a safe default. The check matches the sender (from.id) rather than the chat, so adding the bot to a group cannot be used to inherit access. Rejections log the sender id and answer once, so a legitimate user missing from the list can tell the bot is misconfigured rather than dead. Startup warns when the gateway is enabled with an empty list. The previous TestIsChatAllowed asserted 'empty allowlist allows all' -- it encoded the vulnerability -- and is replaced by fail-closed tests. Command menu (16.34). SetMyCommands was never called, so Telegram showed no menu and the commands Router implements were undiscoverable; asked about /commands the LLM confidently answered it had none. The published list mirrors what Router actually handles. Failure is logged, not fatal: it costs discoverability, not function.
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
132 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%