GeezerVison

Personal memory reused the project guidance, so the model was told to
save project people, decisions, deadlines, and links into a scope the
intro said was personal. Guidance now follows the memory scope.

Also drops the memory Storybook stories in favor of Vitest coverage of
the loading and error states.

…olidate memories in the background

The system prompt keeps only the memory guidance so it stays stable across
turns; the read_memory tool description carries the current index. After
extraction, a detached consolidation pass merges duplicates and prunes
superseded memories under strict caps (8 mutations, 24h debounce, per
scope advisory lock, fresh memories protected) and records each run in
chat_memory_consolidations, pruned to the newest 20 per scope.

…solidation in the memory section

Adds mock-based tests for the consolidation debounce, lock, cap, protect
window, journaling, pruning, and failure paths, and surfaces the newest
successful consolidation as a one-line summary under the memory list.

…tion tests

Revalidation now reads rows FOR UPDATE inside the apply transaction so an
edit committed after the reread cannot be overwritten. Candidates are the
unprotected memories oldest first, so the input cap trims recent entries
rather than the stale duplicates consolidation exists to remove. At the
cap only a run that shrank the scope bypasses the debounce. Journal
mutations are always an array.

Extraction tests use an afterMemoryExtraction seam instead of spawning
consolidation goroutines against strict mocks.

Sidebar project list with create, edit, and delete gated on the
authcheck result, a project page at /agents/projects/:projectId, new
chat in project, and move-to-project from the chat menu. Behind the
chat-projects experiment.

Collapsed memory rows expand to show the description, body, and edit
and delete controls. Delete failures surface an error alert.

Adds /agents/settings/memory with the personal memory toggle and the
per-organization memory list, and generalizes the project memory
components to serve both scopes.

Summarizes the newest successful consolidation run in one line under
the memory list.

…olidation

…ects-ui

…ects-ui

…ed composer

… the memory toggle

…s UI

chatgpt-codex-connector Bot left a comment

…ct folder review feedback

- Show an empty state when every visible chat is filed in a project.
- Reuse the chat list empty-state copy for empty folders.
- Make the projects loading and error props required.
- Rename ProjectDialogMode to ProjectDialogState.
- Add mock prefixes to new test fixtures.
- Add stories for loading, error, and empty emoji-icon folder states.

chatgpt-codex-connector Bot left a comment

…lar empty state when every chat is in a project

Project chats live only in their folders, so the Chats section uses its
usual empty-state copy when nothing outside a project remains.

…folders open when navigating between projects

A folder that was open because its project was active now stays open
when the user opens a chat in another project. Only an explicit toggle
collapses a folder.

…roject's page after creating it

…t folders with the chat list

The Projects section no longer has its own bounded scroll area. It sits
in the sidebar's scroll area above the Chats section, so expanding a
folder pushes the chats down.

chatgpt-codex-connector Bot left a comment

…coder/coder into f0ssel/chat-projects-ui-folders

# Conflicts:
#	site/src/pages/AgentsPage/components/ChatsSidebar/chats/ChatsPanel.tsx

…ct's page after deleting it

… Projects section

chatgpt-codex-connector Bot left a comment

…ew feedback on project deletion and stories

chatgpt-codex-connector Bot left a comment

…s empty state while projects load

When every chat belongs to a project, those chats are held back until
the project list loads. The Chats section showed "No agents yet" in the
meantime, which falsely told users their chats did not exist.

DanielleMaywood left a comment