Memory Becomes Infrastructure, Not a Tool

Today’s target was fixing a category error: memory was being treated like any other tool Chalie can call, when it should behave more like breathing.

Every ability in Chalie runs through the Policy Manager — the layer that decides, per context, whether an action is allowed, needs confirmation, or gets denied. That’s the right default for things like sending an email or running code, where the consequences are visible and external. But memory isn’t an action with consequences; it’s how Chalie stays coherent across a conversation. Routing it through the same gate as everything else meant memory.forget could land in an “ask” state mid-chat, or get denied outright in subconscious and external-agent contexts — friction on a capability that should never have friction, because the alternative is Chalie quietly forgetting things it shouldn’t.

The fix promotes memory to a SYSTEM-level ability, the same tier skill_manager already sits at. It still dispatches through the same enforcement path as everything else — no special-cased bypass wired around the policy engine — but the default matrix no longer lists memory.* at all, so enforcement resolves to allow in every context: chat, subagent, subconscious, external agent. The ability also drops out of the policy UI entirely, because there’s nothing to configure. On the enforcement side, a new _is_system_action() predicate does prefix-aware matching so sub-actions like memory.recall and any stale seeded memory.* rows from before this change are correctly recognized as system actions rather than falling through to a default. The net behavioral change is concrete: memory.forget, which used to prompt in chat and get denied in subconscious/external-agent contexts, is now allowed everywhere. Memory management stops being something the user or a policy config has to think about, which is exactly where infrastructure should sit — invisible until it breaks, and it shouldn’t break.

The rest of the day was smaller cleanup with real visual impact. The active speech input carried a hardcoded dark box-shadow with no light-theme override, so switching to light mode left a dark halo glowing around the one element you’re actively looking at while talking to Chalie — the kind of bug that’s easy to miss in dark mode and impossible to miss once you’re not in it. The shadow came off outright since the existing top-edge highlight already communicates “active” on its own. That triggered a quick audit of every other hardcoded box-shadow in the frontend for the same pattern; two more turned up — a permissions card and the API key dialog — and both got proper theme-aware treatment instead: strong shadow in dark, soft shadow in light, same sense of lift either way. Small thing, but it’s the kind of detail that either makes an interface feel considered or makes it feel like dark mode was the only mode anyone tested.

Last, a bit of plumbing: the website repo moved to a different GitHub organization, and the CI workflows that push the installer and sync release notes were still pointed at the old path. Repointed and done — the kind of fix you only notice when it’s broken, which is the whole point of catching it before that happens.

None of today’s changes are user-facing features, but they’re the kind of day where the product gets quietly more trustworthy: memory stops being something that can be misconfigured into forgetting, and the interface stops occasionally lying about which theme it’s in.

• Memory promoted to a SYSTEM-level ability — bypasses the Policy Manager, allowed in every context, no longer configurable or listed in the policy UI
• New _is_system_action() prefix-aware predicate correctly classifies sub-actions like memory.recall and legacy seeded rows
• Behavioral change: memory.forget moves from ask/deny in some contexts to allow everywhere
• Dark box-shadow halo removed from the active speech input in light theme; two more hardcoded shadows (permissions card, API key dialog) made theme-aware
• CI workflows repointed to the website repo’s new home after an org transfer