Skip to content

feat(studio): Settings core + Memory - #975

Closed
jtenniswood wants to merge 1 commit into
studio/S09from
studio/S10
Closed

jtenniswood wants to merge 1 commit into
studio/S09from
studio/S10

Conversation

@jtenniswood

Copy link
Copy Markdown

Stack 10/21 — Studio: Settings core + Memory

The settings shell and the read-only Memory surface (structurally a settings sub-feature).

  • Settings layout/header/nav + the sections registry — enumerating only pages that exist at this point in the stack, so there are no dead nav rows mid-series (provider/model-router/gateway rows arrive in PR 11, Labs in PR 19).
  • Pages: index grid, You/profile ("Your name" labels your messages; the agent learns your name in conversation — Studio has no write path into the daemon's user model by design), Personalize/appearance (text size, UI scale, session-list side, notifications; the Enter-behavior row arrives with steer in PR 15), agent identity, learning review (over PR 5's learning client), legacy redirect stubs.
  • Memory: table + detail + consolidate (over PR 5's dream client) with honest disabled/empty states and store footprint — read-only; the daemon has no memory write API by design.
  • The settings/memory e2e spec row joins workspace.spec.ts; user-docs grows; llms regen.

Demo at this stack point: full settings shell, Personalize, agent identity, memory table + detail, learning review.

Part of the stacked landing of #618.

🤖 Generated with Claude Code

The settings shell (layout, header, nav, the sections registry — enumerating
only pages that exist at this point in the series, so no dead rows) and its
core pages: the index grid, You/profile, Personalize (text size, UI scale,
session-list side, notifications — the Enter-behavior row arrives with steer
later in the series), agent identity, the learning-review page over the
harness learning client, and the legacy redirect stubs.

Memory is structurally a settings sub-feature and lands with it: the
read-only table with honest disabled/empty states and store footprint,
per-entry detail, and consolidate over the dream client. Read-only is by
design — the daemon has no memory write API, because a hand-typed value
would enter turn-0 context without injection scanning.

The settings/memory e2e spec row joins workspace.spec.ts.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jtenniswood jtenniswood added enhancement New feature or request ux ui WebUI Applies to the WebUI interface labels Sep 2, 2026
@jhrozek jhrozek closed this Sep 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request ui ux WebUI Applies to the WebUI interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants