Codius CLI
Coding assistant for domain-driven design projects in ASP.NET Core.
pip install codius
Why Codius?
Free domain-driven designers from boilerplate and let them focus on modeling.
Codius is your coding assistant for domain-driven design — built to take care of the repetitive tasks that just have to get done.
Instead of manually writing boilerplate for aggregates, methods, repositories, and other building blocks, you describe the changes you want to make. Codius takes care of translating those changes into code, aligned with the OpenDDD.NET framework.
This frees you up to focus on what really matters: modeling your domain and evolving your design.
Refinements become faster, iteration cycles shorter, and the feedback loop tighter.
With Codius, your ideas move from thought to implementation without getting lost in scaffolding.
If you’re passionate about DDD, code quality, and improving developer flow, try Codius — or help shape it by contributing to its development.
Example
Say you want a Book aggregate with Title, Author, and Price, and a method to apply discounts.
Just tell Codius:
> Create a Book aggregate with Title, Author, and Price.
Add a method to apply a discount to the Price.
Codius handles the boilerplate — aggregate, method, repository — so you can focus on the model.
Quickstart
$ pip install codius # Temporary package name
$ cd /your/project/root # Go to your project's root
$ codius # Starts Codius CLI
On first run, Codius will create .codius/config.yaml and initialize a modeling session.
Compatibility
Codius is designed for projects built with OpenDDD.NET — a framework for Domain-Driven Design in .NET.
It works directly on your existing codebase, generating and modifying code according to OpenDDD.NET’s conventions.
Whether you’re evolving your domain model or adding new building blocks, Codius helps you stay consistent and productive within the framework’s structure.
Slash Commands
| Command | Description |
|---|---|
/clear |
Reset session state and history |
/clearhistory |
Reset session history |
/compact |
Summarize and condense history |
/model |
Change LLM provider/model |
/approval |
Switch approval mode (suggest/auto) |
/sessions |
List previous sessions |
/history |
Show session history |
Requirements
- Python 3.9 to 3.12
- A project built with OpenDDD.NET
- OpenAI or Anthropic API key (set in
config.yamlor use/modelin the CLI)
Configuration
When you run Codius for the first time, it creates a .codius/config.yaml file in your project root.
This file controls how Codius behaves — including which LLM provider it uses, how verbose it is, and whether changes are auto-approved or suggested.
Example
debug: true
debug_llm: false
log_level: warning
approval_mode: suggest
llm:
provider: openai
openai:
model: gpt-4o
api_key: sk-... # Or leave blank to use the OPENAI_API_KEY environment variable
anthropic:
model: claude-3-opus
Config Options
| Key | Type | Description |
|---|---|---|
debug |
bool |
Enables general debug output in the CLI |
debug_llm |
bool |
Logs LLM request and response payloads |
log_level |
str |
Controls log verbosity: info, warning, or error |
approval_mode |
str |
Determines if changes are auto-applied: • suggest — manual approval• auto — apply immediately |
llm.provider |
str |
Specifies which LLM provider to use: • openai, anthropic |
llm.<provider>.model |
str |
The name of the LLM model to use (e.g. gpt-4o, claude-3-opus) |
llm.<provider>.api_key |
str or null |
The API key to use for that provider. Can be omitted to use env var (e.g. OPENAI_API_KEY) |
💡 If
api_keyis not specified in the YAML file, Codius falls back to environment variables likeOPENAI_API_KEY.
Contribute
Codius is under active development.
If you're into:
- Domain-Driven Design
- Developer tooling
- LLM-based assistants
- Improving the modeling experience
...then jump in! Try it out, explore the codebase, and open an issue or PR.
License
Licensed under GPLv3.
Metadata
Release files for codius 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| codius-0.3.0.tar.gz | 45.0 kB | With provenance | Details for codius-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codius-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for codius-0.3.0-py3-none-any.whl |
Total release size: 135.1 kB
Release files / codius-0.3.0.tar.gz
| Download URL | codius-0.3.0.tar.gz |
|---|---|
| Size | 45.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0de3205a7506c7a7abd3ae5fedce0f44a6ce3696879105b64d142e05288d12d8
|
|
BLAKE2b-256 checksum How to use checksums |
6ec537523d607611f275ca981e81664cd879db8239d9ecd38fb28a31299508a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2025.
Transparency logRelease files / codius-0.3.0-py3-none-any.whl
| Download URL | codius-0.3.0-py3-none-any.whl |
|---|---|
| Size | 90.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fed0e522d79bfa6db72a78789294d64371a8be18495ac2a3b874e027f83dee95
|
|
BLAKE2b-256 checksum How to use checksums |
f4b68346d959f596b04661414f5b7f8f9f5e1c5a56ea3cb8a8089cea7f607468
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2025.
Transparency logSecurity for codius 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for codius-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.