Making good use of Qoder Experts Mode to assemble a multi-Agent expert team, delivering merge-to-main features through 30-minute parallel work.
I'm a bit of a perfectionist—the moment I see a software update prompt, I upgrade right away.
Sure enough, after upgrading Qoder to the latest V0.8, the Experts Mode I'd been waiting for finally went live!
Much like the Team Agent in Claude Code, Qoder's Experts Mode also evolves AI from a single Agent to multi-Agent collaboration.
The Leader Agent is responsible for breaking down tasks, assembling the team, and tracking progress, while the Frontend Dev, Backend Dev, and QA Tester work in parallel—you only need to review the plan and accept the results.
I recorded a screen capture so everyone can get a feel for it in advance.
Each expert in Experts Mode is a specially tuned SWE Agent (Software Engineering Agent).
This so-called specialized tuning isn't merely swapping in a different prompt; it involves targeted optimization across model selection, parameter configuration, context management, tool calling, and more.
For those who haven't downloaded it yet, copy this address and open it in your browser.
Talk is cheap—let's get straight to practice.
I happen to have a PaiGit project on hand—a source-code management platform similar to GitCode, GitHub, and Gitee. Its current features include repository import, Issue management, Wiki generation, and more.
Since Qoder told us there are still three directions to improve—Issue creation/editing/commenting, Wiki page creation/editing, and refining the download feature—
we launch all three features in parallel right away.
At this point, Experts Mode pulls the investigator Sam (Research Agent) into the Team, responsible for investigating the existing code state of the three modules, then formulating specific tasks for parallel development.
Heh, this really is comfortable.
Throughout the whole process, it felt like I didn't even have to use my brain—Qoder thought of everything for me.
OK, after a short wait, the tasks are ready.
Experts Mode pulls backend engineer Jimmy into the Team, responsible for Task 1: Issue module enhancement—editing issues and editing/deleting comments.
Maybe Experts Mode felt one backend engineer was too slow, so it pulled in Bill too, responsible for Task 2: Wiki module enhancement—manually creating/editing/deleting Wiki pages.
That's not all.
Experts Mode then pulled in frontend engineer Robin as well, responsible for the frontend refinement of the download module: the admin review panel and the user download experience.
Wow, a true Agent legion.
Three experts working at the same time, without interfering with one another. I could see each expert's progress in real time on the interface. The efficiency of this parallel work is clearly higher than a single Agent executing serially.
At this moment, I no longer knew whether I was living in a real-world team or in a cyberpunk future.
I believe everyone here is a loyal fan of IntelliJ IDEA, but at this moment, I already felt a slight worry.
AI IDEs are evolving way too fast.
You can't help but marvel at Qoder's speed of evolution.
After the development tasks were done, Experts Mode pulled in a new test engineer, Chris, responsible for verifying whether these three features were complete.
Soon, the test results came in too.
Issue editing and comment management — fully working. An "Edit" button was added to the top-right of the Issue detail page, supporting inline editing of the title and content. Each comment in the comments section has "Edit" and "Delete" links next to it (visible only to the author/admin), and deletion has a confirmation dialog to prevent accidental actions.
Wiki creation/editing/deletion — fully working. The Wiki page added a "New Page" entry, and the creation form supports title + Markdown content input. Existing pages show an "Edit" button, and admins additionally see a red "Delete" button. Markdown renders well, with titles, lists, code blocks, and links all displaying correctly.
Download module frontend refinement — working properly. The Dashboard added a "My Download Requests" section, showing request history and status tags (Approved/green). The admin area retained the "Pending Download Requests" panel, supporting approve/reject actions. The download button on the repository details page displays correctly according to status.
As an old-timer programmer, seeing the results at this moment, I felt both delighted and astonished.
The delight: Qoder's progress along the way is truly there for all to see. From now on, when I develop projects for everyone, all that's left is to burn tokens.
The astonishment: after not looking for just a few days, Qoder has evolved to this point—completely exceeding my initial expectations for Experts Mode.
Test engineer Chris even kept some of her testing evidence; click the image to view it.
In this round of development, a total of 19 code files were modified—truly impressive.
Let's manually verify the results. For the Issue part here, confirmed no problems.
Indeed, everything's fine.
This kind of autonomous coordination among experts saved me a lot of communication overhead. In a traditional development process, this kind of frontend-backend format inconsistency would require manual intervention to coordinate.
But in Experts Mode, the experts discovered the problem themselves, discussed the solution themselves, and only needed me to confirm at the key decision points.
Overall, the delivery quality was quite good—reaching a standard that could be merged directly into the main branch.
Unlike a traditional single Agent, the advantages of Experts Mode are quite obvious.
① Planning first makes the overall architecture clearer. The Leader Agent produces a complete plan first; I review and confirm it before execution, so it's less likely to go off track. Even if there are adjustments during execution, they're adjustments within the overall framework and won't stray too far.
② Multiple experts work simultaneously—the Backend Dev writes the backend while the Frontend Dev writes the frontend, the Researcher does research, and the QA Tester prepares test cases. This level of parallelism is something a single Agent can't match.
There's one thing I especially appreciate: every time a new feature is developed, the investigator steps in to ensure that all development tasks are crystal clear.
This reduces a lot of rework.
In the real world, development often outpaces requirements research, leading to later rework until the development matches what was wanted.
Because sometimes even the client can't figure out their own requirements. But in Experts Mode, you can clearly feel that specialized division of labor guarantees quality. Each works deeply and thoroughly in their own domain. There's no situation of "knowing a bit of everything but mastering nothing."
Currently, there are several tiers for getting Experts Mode.
Pro+, Ultra, and Teams users unlock it upon subscription—no application needed; just switch to Experts in the mode selector to use it.
Well, I'm Pro+ (let me splurge 😄).
Pro users can join the Waitlist for priority review, and will be notified by email once approved.
After heavily using Experts Mode for a while, I have one strong feeling: AI programming tools are evolving from "pair programming" to "engineering delivery."
AI programming in the past meant AI assisting you in writing code. You were still the protagonist, and AI was the assistant. You had to tell the AI what to do at every step, check every line of code the AI wrote, and correct every mistake the AI made.
Today's Experts Mode is an AI team delivering features for you. You've become the project manager, and the AI is the execution team. You're responsible for defining the problem, reviewing the plan, and making decisions; the AI is responsible for the concrete implementation, quality assurance, and progress tracking. In this mode, the AI is a team and you're a manager.
The significance of this shift is profound.
I hereby declare that Qoder Experts Mode will be the main force for my complex tasks from now on.
This mode is just too good to use—oh my goodness.
You can manage multiple tasks at the same time. Before, for a complex feature, you had to keep your full attention on the AI and couldn't do anything else. Now you toss the requirements to Experts Mode, go do something else, and just wait for the notification to accept the results. Your time is freed up to handle higher-level problems.
Your role is being upgraded—from "the person who writes code" to "the person who defines problems, reviews plans, and makes decisions." This is exactly the direction programmers should evolve in the AI era. When AI can write code, a person's value lies not in the speed of writing code, but in understanding the business, controlling the architecture, and holding the line on quality.
[The future of software development may truly be a model of "one person + one AI team." One person can manage multiple AI experts and complete tasks that previously required a whole team.]
This isn't the future—it's what's happening right now.
This whole piece is intense—buckle up, we're hitting the road. Beep beep, off we go.
01. What Is Experts Mode?
Each expert in Experts Mode is a specially tuned SWE Agent (Software Engineering Agent).
This so-called specialized tuning isn't merely swapping in a different prompt; it involves targeted optimization across model selection, parameter configuration, context management, tool calling, and more.
For those who haven't downloaded it yet, copy this address and open it in your browser.
https://qoder.com/ideAfter installing, open Qoder, create a new session, select [Experts Team], switch to Experts Mode, and then enter your requirements to get started. We just provide the requirements, and the Leader Agent automatically assembles a team of experts who work in parallel—well-suited for complex, multi-step tasks. In this mode, the AI is an engineering team and you're the project manager, responsible for reviewing the plan and accepting the results. More importantly, different experts are automatically routed to the model best suited for them. The Leader Agent needs to do complex task planning and decision-making, so it might route to Opus, which has the strongest reasoning ability; the Backend Dev needs to write high-quality Java code, so it might route to GLM5, which excels at coding; the QA Tester needs to do browser automation testing, so it might route to Kimi K2.5, which supports vision capabilities. In plain terms: you give the requirements, and Experts Mode assembles a team to do the work for you. The Agent workhorse squad has arrived. As everyone knows, in real-world software development, a complex feature is never written by one person from start to finish. Instead, an architect or tech Leader does the design first, then splits it among different roles—frontend, backend, testing—for parallel development, and finally integration testing. Experts Mode is exactly this collaboration model.
02. Experts Mode in Action
Talk is cheap—let's get straight to practice.
A First Try
I happen to have a PaiGit project on hand—a source-code management platform similar to GitCode, GitHub, and Gitee. Its current features include repository import, Issue management, Wiki generation, and more.
Prompt: Start the frontend and backend separately; let's first take a look at the current development progress.In the past, we'd need to start the backend in IntelliJ IDEA, then start the frontend with a separate frontend IDE, and then open the browser to visit the address. Right? And now? Qoder proactively brings up the frontend and backend for us, then assigns a test engineer, Alex, to help us check the project's development progress. He automatically opens the browser (note the Chrome in the top-left corner being controlled by automated testing software) and then verifies each feature one by one for us. And gives us a final report: the authentication module (fully implemented), the home browsing module (fully implemented), the repository details module (fully implemented), and the user dashboard (fully implemented). Afterward, it even thoughtfully asks whether we want to generate the project's Wiki. Of course we do.
Going All Out
Since Qoder told us there are still three directions to improve—Issue creation/editing/commenting, Wiki page creation/editing, and refining the download feature—
we launch all three features in parallel right away.
At this point, Experts Mode pulls the investigator Sam (Research Agent) into the Team, responsible for investigating the existing code state of the three modules, then formulating specific tasks for parallel development.
Heh, this really is comfortable.
Throughout the whole process, it felt like I didn't even have to use my brain—Qoder thought of everything for me.
OK, after a short wait, the tasks are ready.
Experts Mode pulls backend engineer Jimmy into the Team, responsible for Task 1: Issue module enhancement—editing issues and editing/deleting comments.
Maybe Experts Mode felt one backend engineer was too slow, so it pulled in Bill too, responsible for Task 2: Wiki module enhancement—manually creating/editing/deleting Wiki pages.
That's not all.
Experts Mode then pulled in frontend engineer Robin as well, responsible for the frontend refinement of the download module: the admin review panel and the user download experience.
Wow, a true Agent legion.
Three experts working at the same time, without interfering with one another. I could see each expert's progress in real time on the interface. The efficiency of this parallel work is clearly higher than a single Agent executing serially.
At this moment, I no longer knew whether I was living in a real-world team or in a cyberpunk future.
I believe everyone here is a loyal fan of IntelliJ IDEA, but at this moment, I already felt a slight worry.
AI IDEs are evolving way too fast.
You can't help but marvel at Qoder's speed of evolution.
After the development tasks were done, Experts Mode pulled in a new test engineer, Chris, responsible for verifying whether these three features were complete.
Soon, the test results came in too.
Issue editing and comment management — fully working. An "Edit" button was added to the top-right of the Issue detail page, supporting inline editing of the title and content. Each comment in the comments section has "Edit" and "Delete" links next to it (visible only to the author/admin), and deletion has a confirmation dialog to prevent accidental actions.
Wiki creation/editing/deletion — fully working. The Wiki page added a "New Page" entry, and the creation form supports title + Markdown content input. Existing pages show an "Edit" button, and admins additionally see a red "Delete" button. Markdown renders well, with titles, lists, code blocks, and links all displaying correctly.
Download module frontend refinement — working properly. The Dashboard added a "My Download Requests" section, showing request history and status tags (Approved/green). The admin area retained the "Pending Download Requests" panel, supporting approve/reject actions. The download button on the repository details page displays correctly according to status.
As an old-timer programmer, seeing the results at this moment, I felt both delighted and astonished.
The delight: Qoder's progress along the way is truly there for all to see. From now on, when I develop projects for everyone, all that's left is to burn tokens.
The astonishment: after not looking for just a few days, Qoder has evolved to this point—completely exceeding my initial expectations for Experts Mode.
Test engineer Chris even kept some of her testing evidence; click the image to view it.
In this round of development, a total of 19 code files were modified—truly impressive.
Verifying the Results
Let's manually verify the results. For the Issue part here, confirmed no problems.
Indeed, everything's fine.
This kind of autonomous coordination among experts saved me a lot of communication overhead. In a traditional development process, this kind of frontend-backend format inconsistency would require manual intervention to coordinate.
But in Experts Mode, the experts discovered the problem themselves, discussed the solution themselves, and only needed me to confirm at the key decision points.
Overall, the delivery quality was quite good—reaching a standard that could be merged directly into the main branch.
03. The Advantages of Experts Mode
Unlike a traditional single Agent, the advantages of Experts Mode are quite obvious.
① Planning first makes the overall architecture clearer. The Leader Agent produces a complete plan first; I review and confirm it before execution, so it's less likely to go off track. Even if there are adjustments during execution, they're adjustments within the overall framework and won't stray too far.
② Multiple experts work simultaneously—the Backend Dev writes the backend while the Frontend Dev writes the frontend, the Researcher does research, and the QA Tester prepares test cases. This level of parallelism is something a single Agent can't match.
There's one thing I especially appreciate: every time a new feature is developed, the investigator steps in to ensure that all development tasks are crystal clear.
This reduces a lot of rework.
In the real world, development often outpaces requirements research, leading to later rework until the development matches what was wanted.
Because sometimes even the client can't figure out their own requirements. But in Experts Mode, you can clearly feel that specialized division of labor guarantees quality. Each works deeply and thoroughly in their own domain. There's no situation of "knowing a bit of everything but mastering nothing."
04. How to Get Experts Mode
Currently, there are several tiers for getting Experts Mode.
Pro+, Ultra, and Teams users unlock it upon subscription—no application needed; just switch to Experts in the mode selector to use it.
Well, I'm Pro+ (let me splurge 😄).
Pro users can join the Waitlist for priority review, and will be notified by email once approved.
https://qoder.com/ide?waitlistBy the way, new users who register for Qoder get a 14-day free Pro Trial and an extra 300 Credits. My usage suggestion: first use Agent Mode to get familiar with Qoder's basic operations, then upgrade to Experts Mode when you hit complex tasks. Don't jump straight into Experts Mode for simple tasks—that's a bit of overkill.