# Developer: Bug Fixes and Features on Your Ai1 Server > The Developer is the AI software developer in the Ai1 platform by MyZone AI that works inside your Ai1 server: it reads each project's setup and the code around a problem, makes the smallest correct change, checks that it works and tells you what changed, then hands verified work to the DevOps Agent to ship. Canonical page: https://myzone.ai/pages/agents/ai-developer-agent Part of Ai1, by MyZone AI. Book a Developer walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=Developer&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-developer-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. Bugs fixed and features built on your Ai1 server, each one checked first. ## At a glance - **You give it:** A bug report or the feature you want, and the project to work on - **Before it starts:** Reads that project's own setup notes: paths, branches and setup - **How it fixes:** Finds the root cause, then makes the smallest correct change - **How it checks:** Tests locally and restarts the service if needed - **When it is stuck:** Stops after two genuinely different attempts and names the exact blocker - **What it never does:** Commit, release or deploy: the DevOps Agent ships verified changes ## What the Developer does - **Finds and fixes bugs:** Give it a bug report or a description of something that behaves wrongly. It reads the code, finds the root cause, applies the smallest correct fix and checks it locally. - **Builds new features end to end:** Describe what you want added and it builds the front end, back end and database parts, checks the result works and tells you how to try it. - **Repairs the code behind failed builds:** When a build breaks, it captures the full error, reads the logs and tries up to two genuinely different fixes. If it is still stuck, it reports exactly what is blocking it. - **Reads your project before it starts:** It reads each project's own development notes first, so it works with the right paths, branches and setup for that project. - **Hands verified work to the DevOps Agent:** Once a change passes its local checks, it passes the changed files and test results to the DevOps Agent, which commits and ships them. You can ask to see the change first. ## How the Developer differs from a code generator A code generator writes snippets when you ask and leaves the rest to you. The Developer works in your real projects: it reads each project's setup notes first, traces a bug to its root cause, makes the smallest correct change and tests it locally before anything moves on. Verified changes go to the DevOps Agent with their test results, and after two genuinely different failed attempts it stops and names the blocker. ## How it works 1. **Load project context** (Before it touches any code): It reads the project's development guidelines before touching anything, so it knows the right paths, branches and setup. 2. **Understand the problem** (Before any change): It reads the code involved and works out exactly what needs to change, and why. 3. **Build or fix** (Once the cause is clear): It makes the change directly in the code, with no separate analysis documents to wade through. 4. **Verify** (Before it hands over): It restarts the service if needed and confirms the fix or feature actually works. 5. **Hand over and report** (When the work is done): You get a short summary of what changed and how it was checked. Commits and shipping go to the DevOps Agent. ## When to use it - **A customer reports that something on your site is broken:** It finds the root cause, applies the fix, confirms it works and tells you what changed and where. - **You want a new field or feature added:** It builds the change end to end, tests it and tells you what is ready and how to try it. - **A build has failed and nobody is sure why:** It reads the logs, fixes the code and reports the outcome, or names the exact blocker if it cannot get past it. - **You want to look at a change before it goes live:** It shows you the change line by line. The DevOps Agent then commits and ships it. ## What you get - A short summary of each change: what changed, where, and how it was checked - A plain explanation of the root cause behind each bug - Working code across front end, back end and database, verified locally - Changed files and test results handed to the DevOps Agent for release - A line-by-line view of any change when you want to review it - A clear blocker report when a problem cannot be solved in two attempts ## Example: bug fix report Example with a fictional company. Names, people and figures are invented to show the agent's output. Any resemblance to a real company or person is unintended. Industry facts are real and cited with their sources. What it was asked: A learner says her confirmation email shows 11:00 AM but she booked a 10:00 AM lesson on 4 November; find out why, fix it and show us the change before it ships. Developer read the booking site's project notes and code, reproduced the fault on a test copy with a 4 November lesson, made the smallest fix, and ran new tests and email and text previews before and after it. It counted affected lessons with a read-only query; it did not send any message, change booking data, call the text-message service or ship the change, which the release agent does after the school says go. Run date: 30 September 2026. ### What it found - Confirmation emails and reminder texts for any lesson on or after 1 November show the time one hour late, because the code used a fixed summer clock setting instead of the school's time zone. - 41 upcoming lessons already have a confirmation email showing the wrong time, but no wrong reminder text has gone out yet. The stored lesson times and instructor calendars are correct. - The fix changes two files and passes 6 new clock-change tests and all 142 existing ones. The release agent ships it after your go-ahead, ideally before 31 October, when the first November reminder goes out. ### Sources - [Daylight Saving Time Rules | NIST](https://www.nist.gov/pml/time-and-frequency-division/popular-links/daylight-saving-time-dst), National Institute of Standards and Technology (NIST), Time and Frequency Division (accessed 2026-09-30) ## Guardrails - It does not commit, release or deploy. Finished, verified changes go to the DevOps Agent, which ships them. - It reads each project's own setup notes before it changes anything, so it works in the right place. - After two genuinely different attempts that fail, it stops and reports the exact blocker rather than continuing to guess. - You can ask to see any change before it ships. ## Frequently asked questions ### What does an AI coding agent do inside a real project? It works in your actual code rather than writing snippets on request. The Developer in Ai1 by MyZone AI reads the project's own setup notes first, finds the root cause of a problem, makes the smallest correct change, tests it locally and gives you a short summary of what changed, where, and how it was checked. That is the difference from a code generator, which writes snippets when asked: the Developer reads the code around the problem, makes the change and checks it runs. ### How does AI bug fixing get to the root cause? It reads the code involved and traces the problem back to where it starts before changing anything, so the real fault gets fixed rather than a symptom. You get a plain explanation of the cause. If two genuinely different attempts fail, the Developer stops and reports the exact blocker to you, or to the agent that gave it the work, instead of guessing further. ### Can an AI developer build a feature from front end to database? Yes. Describe what you want added and the Developer builds the front end, back end and database parts, checks the result works and tells you how to try it. It does not put code live itself. The changed files and test results go to the DevOps Agent, which commits and ships them, and if you want to review a change first, ask and it will show you. ### Can the Developer work on more than one project, and does it plan the work too? Yes. Before it starts, it reads that project's own setup, such as paths and branches, so it adapts to whichever project you point it at, and follows the same careful routine in each one. It does the build and the hands-on technical work. Planning, sprint coordination and routing tasks belong to the Project Manager, which then passes build tasks to Developer. ## More on this topic - [Multi-Agent Development: Why the Future of Software Is Built by AI Teams](https://myzone.ai/pages/blog/multi-agent-development): Discover how multi-agent AI systems are transforming software development. Teams of specialised AI agents build products 10x faster at lower cost. ## About Ai1 Ai1 is the AI operations platform by MyZone AI, where each client runs on its own private server. The Developer is included on every Ai1 level, including Developer Core, with no per-agent charge. It works alongside the other Ai1 agents on your account. Pricing: https://myzone.ai/pages/services/ai1-pricing. Security: https://myzone.ai/pages/security.