Skip to main content
A module in Codenull is a complete functional unit — it includes a data model (tables, fields, relationships) and the screens to interact with that data. Agents can design entire modules from a single description.

​
How to design a module with an agent

  1. Open the agent panel in the designer.
  2. Describe the module you need, including the entities, their fields, and how they relate to each other.
  3. The agent will propose the data model and the screens to manage it.
  4. Review the proposal and confirm or ask for adjustments.
  5. The agent applies the changes to your application.

​
Example prompt

Module generation may take a few seconds as the agent needs to process the data model relationships and generate multiple screens.

​
Architecture decisions recorded while building

While it builds, the agent can record architecture decisions — the reasoning behind a choice that the resulting configuration does not show on its own (why one data model was picked over another, a naming convention, a trade-off). They are stored per application and are visible to anyone working on it later, from the chat or from an external MCP client. After a step that changes the data model (tables, fields, relationships) or that grants roles access to what was created, the agent is reminded to record a decision if the change involved a non-obvious choice. The reminder is a suggestion: the agent skips it for self-explanatory changes, and it appears at most once per kind of change in a plan, so it does not interrupt the flow.
Recording decisions requires the Designer agent permission — the same one needed to design features and modules. Users without it can still read the decisions already recorded.