Ecosystem
Corenel is one part of a system you mostly already own: your machine, your provider key, and perhaps Claude Code, already installed. Here is where each part sits.
How the parts fit
Two of these are ours and two are yours. Which is which is the whole architecture.
| Part | Whose | What crosses it |
|---|---|---|
| The app | Runs in your browser | Prompts, by the route you chose. Beyond that: usage analytics, and error reports and run metrics limited to a fixed list of fields such as model, token counts and timings. |
| The gateway | Ours | Prompts and completions for a built-in provider, forwarded and not stored. A custom OpenAI-compatible endpoint bypasses it entirely and is called from your browser. |
| The sidecar | Yours: you install and start it | Tool calls, each checked against your policy first. Its file tools reach only the folders you gave it. |
| Your provider | Yours: your key, your bill | Whatever the agent read, as prompt text. What the provider keeps is set by its own terms. |
What it plugs into
@corenel/sidecar ships and releases separately. It is the bridge between the agent in your browser and the directories on your machine you have approved, and the reason your files never need an upload step.
Running Claude Code locally? The sidecar proxies it over the Agent Client Protocol (an open protocol for driving a coding agent from another program) and gates its tool calls with the same policy every other run goes through. By default it signs in with your existing Claude subscription: no second subscription, and no second set of rules.
The gateway calls OpenAI with your own key, at their rate and with no markup. Any other model can reach Corenel through an OpenAI-compatible endpoint (Ollama, LM Studio or vLLM on your machine, or another vendor’s compatible API) which your browser calls directly.
Prompd’s registry publishes versioned prompt packages, workflows and skills. Installing one records the exact version it resolved in the workspace’s lockfile, so the same install comes out the same on another machine or for a teammate.
Get connected
The sidecar is the only thing you install: the @corenel/sidecar package, on Node 22 or later. Point it at the work you want reachable and pair it from the browser with the token it prints.