---
title: "Memory files and evolution use separate Channel views"
version: "zh"
---

> Documentation Index
> Fetch the complete documentation index at: https://botharness.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Memory files and evolution use separate Channel views

> Status: Accepted

# Memory files and evolution use separate Channel views

## Context

The first Channel Memory entry combined a current-file list and inline editor with a Git graph. Selecting a commit already opens a full Channel-body diff (#260), while uncommitted changes appear only as a dirty marker. The Human wants to read current files and inspect external edits without having to commit them. ADR-0068 establishes the checked-out Git working tree as current Memory.

## Decision

A PersonaBot DM has two application-defined Channel sidebar entries:

- **Memory files** presents the checked-out Memory Repository as an expandable folder tree. Selecting a file opens its current content in the Channel body. Text is read-only in this surface; binary or oversized content gets a clear non-text result. The Human can use VS Code or another external tool to edit the repository.
- **Memory evolution** shows the native local Git graph. Selecting a commit opens its changed-file list and full-body diff. Current changes default to the Human-facing groups **New memories** and **Updates to existing memories**, with one row per file and a diff against HEAD. A persisted Git terminology preference instead shows collapsible unstaged, staged, and untracked groups with A/M/U/D/R badges and phase-specific diffs. Binary changes are identified without being rendered as text.

Both views return to Chat without losing its unsent draft or reading position. While open, the views reread repository state after a bounded interval and on window focus, so external edits appear automatically. Each collapsible Channel entry also has a Refresh icon in its header. The Memory Service owns safe, bounded Git and file queries; the Client consumes them through the existing DSH Typert/API Gateway seam. Querying never stages or commits. Git remains the authority for current files and history; no second file or diff store is introduced.

## Consequences

The earlier inline text editor is removed from ordinary Memory navigation. This UI choice does not change the existing explicit Human save service contract or Git's own editing and commit capabilities. A working change can disappear or change between listing and selection; the query reports that stale selection rather than showing a diff for an unrelated state. Large and binary files degrade to a safe indicator. The existing commit diff behavior and branch operations remain part of Memory evolution.

Source: https://botharness.ai/zh/dev/adr/0088-memory-files-and-evolution-are-separate-channel-views/index.mdx