# Dev Desk: One Request In, One Accountable Answer Back > The Dev Desk is the AI development help desk in the Ai1 platform by MyZone AI: it turns a developer's request into a bounded plan, sends each piece only to an approved specialist, joins the results and returns one answer with the result, the evidence and any blockers. Canonical page: https://myzone.ai/pages/agents/ai-dev-desk-agent Part of Ai1, by MyZone AI. Book a Dev Desk walkthrough: https://calendly.com/d/ct6h-tcy-8qf/ai1-demo?a1=Dev%20Desk&utm_source=myzone.ai&utm_medium=agent-page&utm_content=ai-dev-desk-agent-final Last updated: 2026-10-05. Reviewed by the MyZone AI team. One developer request in, one accountable answer back. ## At a glance - **Developers ask:** In chat, in their own words - **Questions:** One clarifying question at most, only when it changes where work goes - **Who does the work:** Approved specialists only: building, QA, testing, code review, security and more - **Each brief:** The goal, the scope, what done looks like and the evidence expected - **The answer:** One reply with the result, evidence and blockers, checked for gaps first - **What it never does:** Pass work outside its approved list to another agent ## What the Dev Desk does - **Takes in the request:** It works out the outcome, scope, constraints, deliverable and urgency, and asks one clarifying question at most, only when it changes where the work goes. - **Sends work only to approved specialists:** It finds the best owner and hands over work only if that specialist is on its fixed list: building, QA, testing, code review, security, requirements, scoping, architecture and strategy advice. - **Writes complete briefs:** Every specialist gets the goal, what is in and out of scope, what done looks like and the evidence expected. - **Joins the results:** It waits for every piece, checks for gaps and conflicts, and never passes raw specialist output straight through. - **Answers once:** One consolidated reply goes back in the conversation the request came from. - **Tracks every request to the end:** Each request is followed until it is delivered, blocked or cancelled, with a record of what happened. ## How the Dev Desk differs from a shared request channel In a shared request channel, developers guess who owns a job and replies arrive from everywhere. The Dev Desk works out what each request needs, writes a complete brief for every approved specialist and joins their results, checking for gaps and conflicts before it answers once. Work outside its approved list is refused with no effect, and release work is pointed to the DevOps Agent, never handed on. ## How it works 1. **Request** (Whenever a developer needs something): A developer asks in chat. 2. **Triage** (Before any work is handed out): It works out what is needed and which approved specialist owns each part. 3. **Brief** (Once the owners are clear): Each approved specialist gets a complete brief. 4. **Join** (Before anything is answered): It waits for every piece and checks the results for gaps and conflicts. 5. **One answer** (Once every piece is in): One reply comes back with the result, the evidence and any blockers. ## When to use it - **A bug needs fixing and testing:** The fix goes to the Developer and the test run to the Tester, and one joined answer comes back with the evidence. - **You want to know if a new feature design is secure:** The Security Agent reviews it, and the findings come back summarised in one answer with any blockers. - **Someone asks it to deploy a release:** It explains that releases belong to the DevOps Agent and points you there, without handing the work on. - **You want to know where a request stands:** It tells you the current state: in progress, delivered, blocked or cancelled. ## What you get - One consolidated answer per request with the result, evidence and blockers - Complete briefs for each approved specialist - A record of every request until it is delivered, blocked or cancelled - A clear pointer to the DevOps Agent for release, deploy and code hosting requests ## Example: one answer to a fix-and-test request 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. What it was asked: Riders are getting charged twice when a dock is slow to confirm a return: fix it, make sure it is tested, have someone check the payment change is safe, and ship it tonight. An illustrative request record that follows the five steps in Dev Desk's current public guide: request, triage, brief, join and one answer. It shows the triage, the routing to approved specialists, one complete brief, the join with a follow-up round, and the single reply; release work is pointed to the DevOps Agent, not handed on. The company and all results are invented, and no specialist work was actually run for this example. Run date: 1 October 2026. ### What it found - Before the fix, all 40 simulated slow-dock returns charged the rider twice; after two rounds, all 40 ended in exactly one charge in the Tester's independent run. - The join check caught what the Developer's own tests missed: returns confirmed after the 30-second retry window still charged twice, so Dev Desk sent a follow-up brief before answering. - "Ship it tonight" was not handed on: the release goes through the DevOps Agent when the development lead starts it, and refunds for past charges stayed with the company's finance team. ## Guardrails - It does no specialist work itself; building and bug fixing always go to the Developer. - Work outside its approved list is refused with no effect, never passed to a nearby or more powerful agent. - Answers are written to be safe for everyone who can see them, with no private data and no personal performance scoring. ## Frequently asked questions ### How should a small team handle developer requests that need several specialists? Send them through one front door. In Ai1 by MyZone AI, the Dev Desk splits each request into a bounded plan, writes a complete brief for every approved specialist, waits for all of them and checks the results for gaps and conflicts before anyone hears back. You then get one answer with the result, the evidence and any blockers. ### What is specialist routing with an approved list? Each piece of work goes only to a specialist on a fixed list: building, QA, testing, code review, security, requirements, scoping, architecture and strategy advice. The Dev Desk refuses anything outside that list with no effect, rather than passing it to a nearby or more powerful agent. It coordinates and does not write code itself. Building and bug fixing always go to the Developer. ### Why get one consolidated answer instead of a reply from each specialist? Separate replies make a conversation hard to follow and leave you to join the pieces. The Dev Desk joins the results itself, never passes raw specialist output straight through and replies once. Every request ends delivered, blocked or cancelled, never in silence. Release, deploy and code hosting stay with the DevOps Agent. Dev Desk points you there and does not pass the work on. ### Is Dev Desk ready for my developers, and can we ask it in our team channel? Yes. Your developers ask it in chat, and it turns each request into a bounded plan for approved specialists. You can also ask it in your team channel, and it answers in the same place. ## 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 Dev Desk 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.