Hi João Paulo.

OutSystems has just launched Mentor, which empowers developers to build apps from scratch using AI. That means creating the first version and making further changes using AI capabilities.

I believe that's the direction OutSystems will follow, so don't expect significant enhancements on Service Studio for O11.

Regards.

Yeah, I’m familiar with Mentor, but I don’t think it’s exactly what I need. Mentor is a great tool for starting new development projects, and as an accelerator, it’s definitely useful. While it can open existing apps, my focus is more on having an AI agent that works alongside the developer at all times—like a pair programming assistant. Similar to Co-Pilot, it would be great to have an integrated agent within Service Studio that suggests new code and improvements in real time. 

Ok, I see what you mean. In my opinion, the current AI-powered assistant should be improved to become more like the co-pilot you envision.

it is good thought.  While Mentor is helping developers start projects faster what you have said like a real-time, context aware AI assistant that stays with us as we build and refine logic inside Service Studio.

Imagining an assistant that understands your current flow, suggests logic improvements, catches possible errors, autocompletes expressions, or even recommends best practices based on your app structure like a true AI pair programmer.

 it will boost productivity by reducing repetitive logic patterns and this feature help new developers quickly learn from AI suggestions.
 
I have one concern that is to consider security and privacy as top priorities. Since developers might be working with sensitive business logic there should be safeguards such as on-premise AI processing admin-controlled access or sanitization of shared logic. This ensures enterprises can benefit from AI assistance without compromising on data integrity or compliance.

 But i think even starting with an extension or optional co-pilot mode could really help the community. 

Yeah. Mentor should be embarked to the studio as we see in windsurf or cursor. 

In addition, the capability of the auto-complete showing the next nodes similar to the disabled look and feel. Then the developer can take it or not. 

All the low code developers are amazed with the high code AI capabilities built into the vscode forks. It should be the opposite. So mentor was a great advance but imho the direction is not what the market is expecting / being prepared. If we incorporate the chat with mentor and auto complete capabilities + low code, the devs, the market, the potential costumers will come under their knees. Any efforts and investment in that direction would be the right shot. 

In addition, I believe OutSystems could release the studio publicly so the other companies could create forks and bring their contributions selling it for standard prices in the market. 

Or invest on that or make it available for other partners make it. 

Best Regards,

Ric

I think this is a very valid suggestion. The people who know best how to generate OutSystems code are the people in the community, the developers who create applications for customers. These emerging tools, such as cursor, claude, windsurf, etc., will be able to improve their code generation models more and more because there are DEVs using them to generate code, correcting what is not generated well and thus providing feedback so that the model becomes increasingly better.

I think it is very likely that in the future these models will be so good that we will see versions more focused on no code. 

OutSystems would greatly benefit from an agent in SS trying to help DEVs generate logic. They could also describe the logic created, suggest comments in the logics, understand patterns and guide DEVs to pay attention to good practices in a more proactive way. Today, what we have is AI Mentor showing what is wrong in the architecture of applications that needs to be corrected later, but an AI agent in SS would have a much more immediate effect and an absurd gain in improving the OutSystems code generation model by having thousands of DEVs correcting what it is generating and this being used to better train the model.