_Kerman
ff1c7d415f
The first-use directory name and its stored title came from the Client's startup language, so one product decision carried two incompatible requirements: a path addressed by shell commands, tool arguments, @path references, and session logs, and a label a reader reads. The controller now owns the fixed `default-workspace` directory name and the registry titles the Workspace after that same segment, so `workspace.initializeDefault` takes no request at all — WorkspaceInitializeDefaultRequest and its name validation are gone, and the registry resolver returns a path instead of a path and title. No language reaches the Host. Browser consumers label a Workspace through the new `workspaceDisplayTitle`: a title still equal to the automatic one reads as the localized default name from the `common` namespace, every other title reads verbatim. The Workspace browser resolves it once at the store read, so rows, hover card, search meta, and the rename and delete dialogs inherit it; the hero picker and the Conversation chip resolve it too. Confirming a rename stores the text on screen, which is what stops a row following the language.
description, kind
| description | kind |
|---|---|
| The workspace group map: the persistent workspace entity family, durable directory records, and header-validated session membership, for users and maintainers navigating the group. | package-group |
packages/workspace
English | 中文
Summary
The workspace family lets a host product keep an ordered list of named projects and group each project's sessions by directory. Users can browse those projects and sessions, hide a session from the grouping without deleting it, and remove a project without deleting its folder or session history. Hidden or removed sessions remain available as ungrouped history. Choose this family for a persistent project surface; it requires session storage and a persistence backend, and it does not expose tools, prompts, or session events to the model.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
workspace |
Provides named, ordered projects with the sessions that ran in each directory | ctx.workspaceRegistry |
Related documentation
- Workspace subsystem — the authoritative feature contract for projects and their sessions.
- domain KV storage Agent Note — the storage design behind project records.
- Workspace UI product-flow Agent Note — how the first start builds projects from session history and how the GUI orders them.
- Workspace registration deletion decision — why removing a project never deletes its folder or sessions.
Dev Note
Working context for maintainers — click to expand
None.