WHAT YOU NEED
Before the agents
can start work.
You'll need access to the code, the ticket project and a machine that can build it. Use this list to check what is already in place.
- 01 Platform access
- Your ENAX account must have access to the right company and project. An administrator sets up the connections and adds the agents.
- 02 Development machine
- The current Windows setup runs on a supported 64-bit Windows PC or DevBox. You'll need PowerShell 5.1 or later and administrator rights for the service and updater. Keep the machine on while the agents are working.
- 03 Repository & tickets
- The agents need a Git repository and a ticket project, with permission to read and update the relevant items. Azure DevOps can provide both; Jira needs a connected code repository. Install Git on the DevBox.
- 04 Accounts for each role
- Use a separate work-tracking account for each role: the Consultant Agent, Developer Agent, human consultant and human developer. This keeps assignments and responsibility clear. The roles can share a DevBox when your setup allows it.
- 05 AI provider access
- Have your chosen AI provider account ready. If you use a subscription, install the provider's official CLI and sign in using the Windows account that will run the agent service.
- 06 Build & validation tools
- The DevBox needs the tools your project uses to build and test. Use the SDK required by your .NET repository, or the Python version, dependencies and test tools specified by your project. For D365 F&O, you need a licensed development environment, X++ build tools and a development/test database if the workflow includes synchronization.
Network: the DevBox must be able to reach ENAX, your AI provider, the ticket system and the repository over HTTPS. Check access to private repositories too.
Hardware: choose RAM, CPU and disk space for the size of your codebase and its builds. With a cloud AI provider, you don't need to install a local AI model or have a dedicated GPU.
Optional settings: you can use the standard workflow without creating custom Azure DevOps fields. Custom mappings and local skill files are there if your project needs them.