Raise all 88 workspace zod declarations to exact 4.6.6 and move @browserbasehq/stagehand to 4.4.0, which pins the same version, so the lock keeps a single zod copy. Test expectations and the Typert consumer's node types follow the new declarations; pnpm-workspace.yaml records the release-age exemption for [email protected].
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.
- historical Workspace registration deletion decision — why removing a project never deletes its folder or sessions.
Dev Note
Working context for maintainers — click to expand
None.