The active rule asked for one fact per file, while init still creates
LEARNED.md as a multi-lesson log and the docs tell users to have agents
update it. The rule now says which goes where: a fact or decision gets
its own file linked from INDEX.md, a lesson from a failure gets a new
heading in LEARNED.md.
Refs Codex review on #384.
- The LEARNED.md starter said to update only on request, which
contradicted the active memory guidance; it now defers to the guidance.
- website/AGENTS.md hardcoded a command-page count that had drifted and
omitted the Desktop App navbar item.
- wiki/testing.md gave `bash -c` and `bash -lc` as the rule in different
places; it now says which container needs which, and why.
- Migration-relative wording in wiki/architecture.md and an unexplained
"Always use" in the targets reference are stated as current rules with
their reason.
The generated guidance block defined "what is worth saving" the same way
agents' built-in memory does, but never said how the two relate, so agents
with their own memory kept saving there and left the shared folder alone.
The active rule now says to save here instead of tool-specific memory,
gives a note format and an INDEX.md line shape, and both modes read
INDEX.md at the start of each task instead of "when relevant". The
passive rule asks agents to point out facts worth keeping so the user
can ask for them to be saved.
Dashboard mode descriptions, the CLI help, and the website pages are
updated to match. Test fixtures that anchored on "Read only" follow the
new wording.
* feat(memory): let each agent choose passive or active note updates
Shared memory guidance only told agents to update notes when asked, so
anything worth keeping was lost unless the user remembered to request it.
Some users want agents to maintain the notes themselves, but because the
notes are shared across every tool, blind writes would fill them with
noise.
Add an active mode whose guidance limits saves to facts that will matter
in later sessions, asks the agent to propose a note when unsure, to update
an existing note instead of duplicating it, and to report what it saved.
Passive stays the default and its block is byte-for-byte unchanged, so
existing connections remain configured.
The mode is recorded in each block's marker, so agents can differ. Agents
that read the same file share one block; the dashboard switches them
together and the API rejects conflicting modes for one file. The CLI
prints either block with `extras memory instructions --update-mode`
(`--mode` already means an extra's sync mode).
* feat(memory): review guidance changes as a unified diff
The side-by-side Before/After panes made users scan two windows to find
the one block that changed. A single Git-style diff shows only the
removed and added lines in context, with removals listed first.
* fix(memory): flag targets that read guidance in both update modes
A tool that imports several shared instruction files can read a passive
block in one and an active block in another. The status showed only the
best-ranked block, so the target looked configured in one mode while the
agent still received the other, and switching modes rewrote just one
file. Report such a target as needing attention instead, so the user
sets the tools on those files to one mode.
* fix(memory): refuse mode switches that would split a target's guidance
A target can read intact blocks in more than one file, such as its own
file and an imported shared file. Switching its mode rewrote only the
file the status pointed at, leaving the other block in the old mode and
creating the contradiction the mixed_modes state reports. Skip such a
switch as multiple_blocks so the user removes the extra block first.
Document guidance modes, mixed_modes and multiple_blocks in the
architecture topic, which still described a single implicit mode.
Instructions renders the memory folder with filepath.ToSlash, so asserting the raw
root path can only hold where the OS separator already is a slash. On windows-latest the
test fails on every run while the rest of the package passes.
Co-authored-by: Willie <egg358358@gmail.com>
* feat(extras): add shared Markdown memory management
Store user-managed notes in extras/memory for global and project scopes.
Add CLI operations, a nested dashboard browser, versioned edits, and
backup-backed deletion and recovery.
Connect selected agents with reviewed, marked reading guidance while
preserving existing instruction files and routes. Add explicit INDEX
linking, conflict draft comparison, and copy-content previews.
Document the workflow in five website locales with English screenshots
and translate dashboard copy across all eleven locales. Native automatic
memory remains separate from this shared file overlay.
Validation: make check; 22 UI tests; TypeScript and ESLint; production UI
build; six isolated CLI E2E steps; five-locale website build; explicit
Claude-write/fresh-Codex-read smoke test.
* feat(memory): support dashboard note moves and redesign browser
Add version-checked rename and folder moves without replacing existing notes.
Back up the old path and preserve content and permissions while refreshing
selection, search, index warnings, and backup links.
Integrate the two-pane Memory browser and compact agent controls. Refresh all
English screenshots and document move/link/history behavior in five locales.
Validation: make check, scoped UI tests, TypeScript, ESLint, UI production build,
five-locale website build, locale parity, and visible Chrome workflow checks.
* fix(memory): recheck reviewed files before committing changes
Preserve external edits detected after note backup or draft preparation, and create new notes exclusively. Revalidate each guidance file before writing, report stale partial failures, and correct the built-in move/rename documentation.
* fix(memory): repair initialization and preserve note recovery scope
Detect missing starter files before dashboard note creation and refresh the index after initialization. Honor requested backup paths, include external project memory sources in recovery scope, and log initialization failures after partial mutations.
* fix(memory): protect guidance creates and match Windows history paths
Create new reviewed instruction files exclusively to preserve competing writes. Match Windows history links with native backup paths while keeping POSIX names and backup API paths intact.
* fix(memory): require configured extra for external backup access
Keep project backup scope inside the repository unless a valid memory folder extra enables its external source. Cover listing, version preview and restore denial without changing configured-source recovery.
* fix(memory): lock backup scope validation through restore
Validate project memory backup access under the restore write lock so concurrent extra deletion cannot revoke access between validation and writing. Hold read locks across scoped backup reads as well.