On this page

Codepot ecosystem

Codepot is one project with several deliberately different implementation layers.

The packages should not be presented as accidental duplicates or immediate replacements. Each layer has a specific responsibility in how features are discovered, validated, stabilized, and eventually expressed in the final platform.

Stage 1: mature working prototypes

`codepot-openapi`

The first TypeScript contract engine for the project.

It provides typed builders for OpenAPI contracts, schemas, entities, relations, routes, access, runtime hooks, frontend metadata, and compiler-resolved x-codegen extensions.

`codepotg`

The stable Python and Jinja generation runtime.

It consumes OpenAPI JSON or YAML, performs inference, builds normalized generator contexts, resolves dependencies and imports, and applies bundled or custom Jinja template packs.

Why both remain supported

The prototype workflow is mature and has been exercised in real projects. It provides an important proving ground for new metadata, inference, templates, generation policies, and compatibility decisions.

Stage 2: official JavaScript ecosystem

`codepotx`

codepotx is the official stable rewrite and long-term JavaScript release line.

It is not merely another OpenAPI CLI. It is a reusable runtime with explicit public artifacts and ports for authoring, templating, generation, platform services, and execution.

`codepotx-cli`

codepotx-cli is a terminal frontend. It intentionally contains argument parsing, project-runtime discovery, event presentation, and exit-code handling—but not compiler or generator business logic.

Stage 3: final Codepot platform

The Rust-based platform places Codepot Lang at the center.

The final platform includes:

Feature movement

The normal direction is:

Not every implementation detail moves unchanged. What moves forward is the validated semantic behavior: what a feature means, which inputs and outputs are stable, which safety guarantees matter, and how tools should consume it.

Possible future consolidation

When codepotx reaches sufficient stability and feature coverage, it may replace more of the prototype workflow. That is a future migration decision, not the current status.

Until then:

codepot-openapi and codepotg remain supported;
codepotx remains the official stable rewrite in active development;
Codepot Lang remains the final experimental platform direction.