Corenel CLI — runs the harness in node, in-proc, no transport. The headless proof the kernel is host-agnostic. (corenel run/ask/chat/login + start --sidecar to follow.)

Corenel protocol — zero-dep contracts: ports, types, transport/event shapes. Imported by every other @corenel/* package; depends on nothing.

Prompd sidecar — a local capability server. Run it next to Prompd (prompd.app) so the browser app can reach your machine: local LLMs (Ollama/LM Studio/vLLM) without CORS, your filesystem, and (opt-in) shell.

Corenel shared UI primitives — icons, theme, token-usage helpers, small UI helpers, monaco colorizer. Consumed by @corenel/web-ui and the prompd app alike.

Corenel node capabilities — the tools-web twin. A disk-backed FileService (the harness file tools + node PromptHost workspace) over node:fs, confined to a root. Shell/secrets/~/.corenel to follow.

Corenel browser capabilities: IndexedDB stores (memory/sessions/recall), storage-health, the prompt-config history, and the Web Worker transport (handler + client). The node twin is @corenel/tools-node.

Corenel — host-agnostic agent harness (kernel). Consumed as source; the app resolves it via the `corenel` path alias, node consumers via this workspace package + the exports map below. The app never hits these exports (the alias intercepts first), so the

Corenel editor workbench — the dockable-panel system today; the composable editor (panels, engine, Workbench) is being carved out of prompd-web's EditorApp. Hosts piece the editor together from these and inject services/language/brand.

Corenel browser dock/agent UI — the presentational components (transcript, composer, rich content, tool render, context manager, etc.). The prompd app's AgentPanel/PolicyEditor compose these on top.