fa6f4aef5fb7b83ceb78ab9af96936f74ea0db5c
Six defects, four of them introduced by the fixes indbacb96,44d43ef,d5e016e,de1a899and4d44ef7. This is the third round in this codebase where a round of fixes broke something the next round caught. SANDBOX SILENTLY DROPPED. startContainers degrades a failed container pool to nil, and the daemon's only test was `if ContainerPool != nil`. So `containers.enabled = true` plus a missing agent image ran every task's agent loop in-process, with the daemon's own authority and the host filesystem -- the one thing [containers] exists to prevent -- while logging only that containers were disabled. Nil now means two things and they are distinguished: SandboxRequired parks the task instead. The daemon still stays up; chat and the dashboard are unaffected. SUMMARY AT THE WRONG END OF HISTORY. compressedHistory returns [head, summary, tail], but ordering is by timestamp, not slice position. The retained messages keep their original timestamps -- that is what preserves their identity -- so the summary, being new, was clamped to now and sorted after the tail it was meant to precede. The model read the recent conversation and was only then told earlier context had been summarised. Confirmed on both backends: index 23 of 24. The monotonic clamp belongs to the append path, where an inbound message must not sort ahead of the one that provoked it. ReplaceMessages is a rewrite primitive and now honours explicit placement, and the summary takes a timestamp inside the span it replaces. A COMPRESSION SUMMARY ANSWERED A QUESTION. Following from the above, PriorReply saw a bot-attributed record immediately after an unanswered message and replayed it as the answer: a redelivered question was "answered" with the compression banner and the model never ran. The user's question was silently swallowed. RECENCY STILL DIVERGED. sessionRecency preferred LastActiveAt whenever set; SQLite used MAX(last_active_at, created_at). Those agree only when LastActiveAt is the later of the two, so a clock step or an older record made the caller and the store order the same sessions differently. LASTACTIVEAT WAS NEVER UPDATED. Touch had no caller, so "resolve the most recently active session" meant the most recently created one -- an operator who moved to an older session with /topic and worked there was dropped back into the newer, abandoned one on restart, which is the bugd5e016eclaimed to fix, with the direction reversed. /branch WITH NO ACTIVE SESSION PANICKED, slicing an empty parent ID for its default title. Pre-existing, but reachable: email and webhook call Route directly without resolving first, and the email path runs in a goroutine with no recover, so one message took the daemon down. The sandbox guard has no test. The honest reason is that exercising it needs a daemon with a forge and worktree the current harness does not build, and a test that re-states the condition proves nothing -- which is the same false confidence that let these regressions through.
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.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%