Hi,
I'm having some issues with the AI agent in ABP Studio v3.0.2, It doesn't seem to complete tasks, gets a lot of things wrong, keeps repeating the same errors. Even though I get it to create a plan which looks correct and give it very specific prompts, it just doesn't get anything right for the ABP framework.
For example, I gave it this prompt:
it went away and created a plan like this:
Then i switch to Agent mode to implement the plan and after a long time of creating errors and trying to fix them it fails and I get this message:
Instead it created some components and razor pages that won't compile and have errors etc.
I've tried various new features and additions to the solution I created and It never creates anything correctly, I spend more time reviewing the code and trying to make it work with the AI Agent than it would take me to write it myself.
On top of that is using a whole bunch of credits on getting things wrong, at this point it feels like a waste of money more than it helps.
What can I do to improve the functionality of this agent?
Regards Raff
8 Answer(s)
-
0
In ABP Studio v3.x, the AI Agent is still a probabilistic tool (LLM-based). For “framework-shaped” tasks (like extending Setting Management UI with contributors/components), it can drift into non-existing types/namespaces (e.g., inventing
SettingManagementViewComponent) and then spiral while trying to self-fix—burning credits. This is an expected failure mode for agentic coding when the task requires exact ABP API usage and project-specific conventions.To improve success rate and reduce wasted credits, use the agent the way it was designed to be most deterministic:
- Run Analyze on the solution and re-run it after any significant change, so the agent has the correct structural map (projects, modules, ABP roles).
- Prefer Ask mode first to have it locate the exact existing ABP extension points in your solution (e.g., where
SettingManagementPageOptionsis configured in your Web module) before letting it generate code. - Use Plan mode but require it to reference existing types/paths found in your solution (e.g., “use the same pattern as the existing Setting Management contributors already in this solution”).
- Use Custom Workflows so builds/restarts happen deterministically after each agent iteration (this prevents long “try/fix” loops and makes failures obvious quickly).
- Keep agent tasks small and verifiable (one ABP integration point per run): e.g. “only add the setting group contributor + registration” (build), then “only add the view component + Razor view” (build), then “wire up permissions/menu” (build).
- When it makes a repeated mistake, save a Lesson (ABP Studio supports this) such as: “Do not invent ABP types; search the solution for existing Setting Management contributor examples and copy the pattern.”
For cost control:
- Stop the agent as soon as it introduces compile errors that indicate hallucinated APIs (wrong base class, missing namespaces). Switch back to Ask mode and force it to first find the correct ABP classes in the current solution and only then proceed.
- Avoid asking it to do an end-to-end feature in one go; that’s the most credit-expensive path.
If you believe this is a product-quality issue with ABP Studio AI Agent v3.0.2 (e.g., consistent failure even with Analyze + small scoped tasks), please contact us so the team can review logs/session behavior: https://abp.io/contact
Less obvious references (verified):
- https://abp.io/studio/ai-agent
- https://abp.io/docs/10.2/studio/overview
- https://abp.io/community/articles/o1ni0toc
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi Raff,
Sorry about this experience, and thanks for the detailed screenshots.
Cases like yours are exactly what we need to see. Our team will review the issues the AI Agent ran into and work on improving it in the upcoming versions.
Thanks for your patience.
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi,
Understood, thanks.
Does the agent have some sort of learning capability where it learns or remembers from what I'm asking it?
Does it have a memory or a capability to add my own skills? playbooks or commands?
Regards Raff
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi Raff,
Yes to all three — ABP Studio's AI Agent already has memory, custom skills/rules, and custom workflows (playbooks).
Memory (Learned Lessons). The agent can call a
save_lessonaction to record a verified correction into a persistentai-learned-lessonsfile in your solution. Those lessons are automatically injected into every future agent conversation in the same solution, so it stops repeating the same mistake. You can also clear them from the UI.Custom AI Rules / Skills. You can author your own rules as
.mdcfiles (Markdown body + a small YAML header withname/description/alwaysApply). Two scopes:- Solution-level:
.abpstudio/ai-rules/— checked into source control, shared with your team. - Global (user-level):
~/.abp/studio/rules/— applies across all your solutions.
alwaysApply: truekeeps the rule in the agent's system prompt at all times;alwaysApply: falseexposes only the name/description and lets the agent pull the full content on demand viafetch_ai_skills(cheaper on tokens). External.mdskill files can also be imported.Custom Workflows (playbooks/commands). You can define tasks to run automatically before and/or after each agent run — Build, Start/Stop/Restart application, Start/Stop containers, Add migration, Install libs, Generate C# / Angular proxies, or your own Run Task. Workflows can be personal (stored under
.abpstudio/workflows/) or shared via the run profile (.abprun.json). This is the most effective way to make the agent actually verify its changes (e.g. force a Build after each edit) instead of looping on hallucinated code.Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) - Solution-level:
-
0
Thanks I think that will help.
Do you have any of these rules, skills or playbooks available for me to plug into my MVC Tiered solution? Ones that you would use in the development of new features, modules etc...
Thanks Raff
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post) -
0
Hi Raff,
Yes — when you create a layered (MVC) tiered solution with a recent ABP Studio, the official rules ship inside the solution itself. I just generated a fresh MVC + Tiered + EF/PostgreSQL solution on ABP 10.4.0 to confirm. Two folders to look at in your solution root:
.abpstudio/ai-rules/— loaded by the Studio AI Agent automatically.app.mdc— describes the DDD layering, layer dependencies, theWeb(MVC/Razor Pages) project, Mapperly conventions, etc. (alwaysApply: true, so it's injected into every agent conversation.)
.cursor/rules/— these are written for Cursor IDE (.mdcfiles). For your MVC + Tiered + EF setup the template only emits the relevant ones:template/app.mdcmcp-studio.mdcframework/common/—abp-core,application-layer,authorization,cli-commands,ddd-patterns,dependency-rules,development-flow,infrastructure,multi-tenancyframework/data/ef-core.mdcframework/ui/mvc.mdcframework/testing/patterns.mdc
The UI/data ones are auto-pruned for your stack (no Angular/Blazor/Mongo rules in your solution since you didn't pick them). If you want any of these to also be used by the Studio AI Agent, copy the content into a new
.mdcfile under.abpstudio/ai-rules/(solution-level, shared with team) or~/.abp/studio/rules/(user-level, all your solutions). Studio also has an Import Skills button under AI Agent Settings, but note that one currently only accepts.mdfiles, not.mdc.If your existing project was created with an older Studio and these folders aren't there, the easiest path is: create a one-off MVC Tiered solution with current Studio, copy
.abpstudio/ai-rules/and.cursor/rules/into your real project, then commit. They live with your solution and travel with the team.For workflows, there's nothing pre-shipped — you author those yourself per solution in AI Agent Settings → Workflow Settings. A typical first one: add a Build task as an After step so the agent verifies its own changes each iteration.
Thanks
Markdown supported.Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)
