Coding assistant for domain-driven design projects in ASP.NET Core.
pip install codius
⚠️ Alpha ReleaseCodius is currently in alpha.
Features may be incomplete, unstable, or subject to change.
Use with care in production environments — and help shape it by providing feedback or contributing!
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.
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.
$ pip install codius # Temporary package name
$ cd /your/project/root # Go to your project's root
$ codius # Starts Codius CLIOn first run, Codius will create .codius/config.yaml and initialize a modeling session.
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.
| 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 |
- 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)
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.
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| 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.
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.
Licensed under GPLv3.