Products
When to use Codemap, Persist, or Layers — open-source TypeScript and JavaScript libraries from Stainless Code, with docs and npm links.
Need a structural index for agents, hydration-aware store persistence, or awaitable overlays? Start from the catalog below. Why we ship this way: About.
Libraries
| Product | One-liner | Docs | npm |
|---|---|---|---|
| Codemap | Local SQLite index for agents — SQL and recipes instead of scanning the tree | docs | @stainless-code/codemap |
| Persist | Any store, any storage — one middleware, no hydrate flash | docs | @stainless-code/persist |
| Layers | Headless modal/dialog/drawer/popover/toast manager — open any layer from anywhere | docs | @stainless-code/layers |
When to reach for each
- Codemap — Use when an agent (or tool) needs a local structural map of a codebase — symbols, imports, and calls — as SQL and recipes instead of scanning the tree.
- Persist — Use when a reactive store needs hydration-aware persistence across storage backends — one middleware, no flash of empty state.
- Layers — Use when overlays should open from anywhere as awaitable calls on a named stack — headless core plus framework adapters, not ad-hoc dialog state.
Different problems. No forced stack — pick one package or several.
Legacy / adjacent
Older React utilities under the same org (npm-homed; no dedicated docs site today):
Archive / npm links — not the primary product index.