← All products
ENAX VIRTUAL AGENCY

Development agents for
.NET, Python and Dynamics 365 F&O

Virtual Agency helps your team plan, implement and validate changes in your existing codebase.

The Consultant Agent prepares a technical plan from the request and the relevant code. The Developer Agent implements the change, runs the configured checks and opens a pull request. Your team decides whether to merge it.

The Consultant and Developer Agents in the product film
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.

GETTING READY

Before installation.

A few checks now will save time during setup. Once these are ready, follow the installation steps in the platform.

  1. Pick a project to start with.

    Choose the repository, base branch and ticket project. Make sure you have a development/test environment for the first run.

  2. Set up the accounts.

    Create the four work-tracking identities and give them the access their roles need. Have the chosen connection details ready, such as a PAT or API token.

  3. Check the DevBox.

    Check that the repository can be opened and the build and tests run on this machine. Choose the Windows service account and make sure it can use the same files and tools.

  4. Sign in to your AI provider.

    Choose the provider in the project settings. For a subscription, complete the official CLI login on the DevBox using the account that will run the service.

  5. Save the connections, then install.

    Test the connections and save them in the platform. Then create the agents and follow their setup instructions. Check the publisher fingerprint against the value shown in the platform before trusting the installer.

  6. Try a small task first.

    Review the project rules and checks, then approve the workflow. Start with a small test request so you can see the analysis, code changes and pull request before handing over more work.

Have a question about your setup? We can go through it in a demo →

WHO DOES WHAT

How the agents divide the work

The agents work from your tickets, repository and project rules. Your developers review what comes back.

◎ CONSULTANT AGENT

Technical analysis

The Consultant Agent reads the ticket and relevant code before writing a technical plan. Missing details can be sent back for clarification.

  • Read the request and existing code
  • Prepare the plan and identify questions
  • Pass the task to the Developer Agent
</> DEVELOPER AGENT

Implementation and testing

The Developer Agent follows the plan on a feature branch, runs the checks set up for the project and opens a pull request.

  • Use the project rules and skill files
  • Run the configured build and tests
  • Respond to changes requested in review

Your team reviews the changes. The agent opens a pull request; your developers decide whether to merge it. They can ask for changes before approving.

A SHORT PRODUCT FILM

Virtual Agency product overview

This 35-second film shows the steps from technical analysis to code review.

35 SEC PRODUCT FILM
Read a summary of the film

The film starts with a developer facing a backlog of requests. The Consultant Agent reviews a task and prepares a plan; the Developer Agent writes the code and runs the project's build and test checks. The developer reviews the resulting pull request. It ends with the message “Understand. Build. Deliver.” There is background music and text on screen, with no voiceover.

WORKING WITH YOUR PROJECT

Set up each project’s workflow

Set up connections and checks for each project, so the agents use the right repository, accounts and build tools.

CONNECT

Tickets & repositories

Connect the ticket system and code repository your team uses. The platform supports Azure DevOps, GitHub and Jira.

CONFIGURE

Rules & skills

Use ENAX's skills, manage your own in the platform or keep an approved skill file on the DevBox. Add project rules when the agents need more guidance.

FOLLOW

Progress & diagnostics

See which task an agent is working on, read its logs and check AI usage. If a run stops, diagnostics and maintenance guidance help you investigate.

WORKS WITH

Technologies and integrations

Virtual Agency supports .NET and Python development alongside Dynamics 365 F&O. Each project uses its own build and test tools.

Application development

  • .NET
  • Python

Databases

  • PostgreSQL
  • SQL Server

ERP development

  • Dynamics 365 F&O

Repositories and work tracking

  • Azure DevOps
  • GitHub
  • Jira
BOOK A DEMO

See Virtual Agency on a project like yours