Etendo Dev Assistant — Shared Context

Etendo ERP development context is established by detecting the project root, core mode, and infrastructure services. It reads database parameters from gradle.properties and resolves the active module so subsequent development commands execute against the correct environment.

Source and JAR core modes in Etendo development determine whether you modify the core codebase directly or use a compiled binary. The context manager detects this setup to apply the correct build and deployment rules for your active module.

Dockerized infrastructure services for an Etendo project are detected automatically during context setup. The system determines whether your environment relies on Docker containers or local services and adjusts the operational context for subsequent development tasks.

You do not need to manually specify the active module for Etendo development commands. The system resolves the active module automatically via the .etendo/context.json configuration file or by analyzing the current working directory.

The /etendo:* prefix is required for Etendo development skills to ensure they operate within the established project context. This enforcement prevents configuration errors and guarantees that all development tasks target the correct database and active module.

Running SQL execution outside the Etendo context risks targeting the wrong database or missing connection parameters. The context manager enforces safe SQL execution by verifying database configurations from gradle.properties before allowing commands to proceed.