Bohdan Triapitsyn
34e8a24b20
The panel stored notes, todos and plans inside one shared JSON file that six unrelated domains also wrote to, synchronised itself through window CustomEvents, and could only read plans. It is now Project knowledge: server-owned storage with explicit routes, a store with rollback, a section sidebar, plans that open and edit in place, and search across all of it. Notes and plans the user pins travel with every message sent in that project. Pinning is project state, not an attachment to one message, so it holds until unpinned and the work status panel names what is riding along and can detach it. Agent memory is added alongside, in two scopes: what is true about the user, and what is true about this codebase. The split is not cosmetic — a wrong project fact costs one project and is noticed, while a wrong global fact quietly shapes every session everywhere and the user has no code to check it against. It stays separate from notes so an agent mistake cannot land in what the user wrote. Sessions receive an index of titles only; bodies are read on demand, because an index carrying full text grows until it crowds out the conversation. Deciding what a session must be told, and whether it has been told, now lives on the server. The client owned it before, which meant sessions started without a UI — scheduled tasks, sessions the agent dispatches — received nothing at all, and a tab's record of what it had sent outlived the conversation: after compaction the agent no longer held the block while the tab went on believing it did. What was delivered is recorded in the session's own metadata, and compaction restores it through the runtime that already restores pinned messages, in the same turn. Agent memory ships dark behind OPENCHAMBER_MEMORY_ENABLE: unset, there is no tool, no routes, no session index, no settings row and no panel tab. Absent rather than switched off, so nothing invites turning on a feature that has not been announced. Pinned notes and plans are unaffected and ship as normal.
20 lines
814 B
JavaScript
20 lines
814 B
JavaScript
/**
|
|
* Whether agent memory exists at all in this build.
|
|
*
|
|
* The feature is complete but not released: it ships dark so it can be tested
|
|
* against real work without appearing to users who have not asked for it. With
|
|
* the flag unset there is no tool, no routes, no session index and no settings
|
|
* row — not a switch left in the off position, which would invite someone to
|
|
* turn on something unannounced.
|
|
*
|
|
* Read per call rather than captured at import, so a process started with the
|
|
* variable set is the only thing that decides — no build step bakes it in.
|
|
*/
|
|
|
|
const TRUTHY = new Set(['1', 'true', 'yes', 'on']);
|
|
|
|
export const isAgentMemoryFeatureAvailable = () => {
|
|
const raw = process.env.OPENCHAMBER_MEMORY_ENABLE;
|
|
return typeof raw === 'string' && TRUTHY.has(raw.trim().toLowerCase());
|
|
};
|