CodeBot for Delphi: The Product Philosophy

RemObjects Software released CodeBot for Delphi, an agentic coding assistant that plans, writes, compiles, and revises code inside the Delphi IDE, with curated Delphi knowledge and a per-seat subscription that includes AI usage. The company emphasizes that source code is not stored on its servers or used to train AI models, and it targets existing line-of-business Delphi apps to boost senior developer productivity and upskill new developers. Managing Director Javier Tarí Agullo of a Delphi-using company advised, 'My advice would be starting with CodeBot, but not tomorrow, and not today: yesterday.'

CodeBot is out now Why did we build it, where do we see the dev world going, and what is RemObjects doing that will help you, your projects, and your business? The short version - What it is: CodeBot https://www.remobjects.com/codebot/delphi.aspx is an agentic coding assistant – butIt plans, writes, compiles, and revises real work in your codebase. built for Delphi https://blogs.remobjects.com/2026/07/30/codebot-the-story/ . - Got an existing line-of-business Delphi app? CodeBot has your back: it supports your codebase, increases productivity for senior devs, and upskills new devs. - Where it runs: inside the Delphi IDE, where your developers already work. It understands your projects, your third-party components and your own libraries — and it works in the form designer, with the designer open. - Why not a generic agent: they're built for Typescript, Python and Swift. CodeBot is built with curated Delphi knowledge — it knows what good Delphi looks like, not just Delphi that compiles. - What you buy: One vendor, one bill, one support line, one data policy, one solution for your team. per-seat subscription https://remobjects.com/codebot/pricing.aspx with AI usage included. - Your source code: not stored on our servers, and never used to train AI models. See the authoritative data safety notice https://www.remobjects.com/codebot/privacy.aspx – send it to your Legal or Approvals team. - If you're evaluating: start with CodeBot for Managers and Decision Makers https://codebot.docs.remobjects.com/Delphi/CoreConcepts/ManagersAndPurchasers/ , or see the questions worth asking any AI coding vendor https://blogs.remobjects.com/2026/08/10/how-to-evaluate-an-ai-coding-tool/ . Or just download it https://www.remobjects.com/codebot/delphi.aspx and try it on a real project. My advice would be starting with CodeBot, but not tomorrow, and not today: yesterday. – Javier Tarí Agullo, Managing Director of a Delphi-using company That's the summary. The rest of this post is the thinking behind it: - what AI is doing to software development; - what that means if your business runs on Delphi - why we built CodeBot the way we did - and what it means for you next time you discuss business direction. We all know AI is greatly changing coding. That it has greatly changed coding. The question for every business and every developer is simply when it will arrive for you, and whether you get there first and learn it, or let it hit you — unprepared. Management philosophy Some background first. When responsible for product or business viability, I follow the guiding ethos: that I may not be able to predict the future, but I can make sure that whatever the future may become, we will be ready to meet it. The technologies I’ve built since my first job out of university right through to today – decades of experience – demonstrate this focus on stable foundations and flexible technology and tooling. Some call it ‘modernity’ in that it can appear a push forward, but really, it’s preparedness and agility : risk assessment, building foundations, solidity, an anchor against which to speed. This is how 'ready to meet the future' works when – as with everyone – you cannot wholly predict the future: first, you understand where you are, and then you ensure you have the foundation such that whatever direction you need to move, you know you will be able to do so. The worst situation to find yourself in is in a changed world, with a set of past decisions that have restricted your options. The best is that you've built so you'll have options, flexibility, agility, and so that whatever changes, you can move forward. It's like giving a runner a good starting block to push against https://www.neuff.co.uk/blogs/athletics-product-guides/everything-you-need-to-know-about-sprint-starting-blocks . Then when you need to: using it. This ethos is even more true now: in software development, we are in a period of incredibly fast movement and change. Preparedness ahead of time, to meet change and agility to adapt to change when it hits are key, and those who have not prepared for today with foresight, or cannot move fast, are at high risk. This matters for you. If you’re a developer reading this, your job has transformed in the past year. If you’re a manager or business owner reading this, the way your business does its software has transformed in the past year. It might not have caught up with you yet, but it will. RemObjects and CodeBot are here to help. Growing Your Software The foundation here is that we love Delphi, and we support both Delphi and its owner Embarcadero. And in the middle of the radical change we see, we want to help you — whether ‘you’ are a Delphi developer, or ‘you’ are a company that relies on Delphi-built software. That includes if you lead one of those companies. the libraries Delphi businesses run on https://www.remobjects.com/delphi/ , a modern Pascal https://www.remobjects.com/elements/oxygene/language.aspx in Oxygene, and cross-language interop https://www.remobjects.com/elements/ in Elements: that's preparedness in practical concrete form, and it's why we saw this coming. With that in mind, let’s rewind one year ago to June 2025. Things have moved really fast in AI, so it’s astonishing to recollect: - Late 2022-early 2024: AI was largely chat. You could ask for a script and get a reply in text, but there was no interaction with your code. - Mid 2024: That was the era of Cursor https://devqube.com/ai-coding-history-future/ and Copilot in VSCode, with AI powered code completion as gray text in the editor. As late as September 2024, Microsoft was still recommending prompting your AI by writing comments https://web.archive.org/web/20240926064849/https://visualstudio.microsoft.com/github-copilot/ . Agents were on the horizon eg Devin, the first agentic loop, in March 2024 https://www.taskade.com/blog/ai-coding-history , and in tools like Copilot, AI could directly edit your code and do simple work for you. - Sep 2024: Delphi added Smart CodeInsight. The feature was an AI-powered chat; as this video shows https://www.youtube.com/watch?v=S71vRppdnqg&t=1379s its answers were unaware of Delphi, it had no access to your source without manual steps not demo-ed but buttons visible in that video , and its code completion inserted commented-out text https://www.youtube.com/watch?v=S71vRppdnqg&t=1379s . - June 2025: Claude Code became publicly available https://www.anthropic.com/news/claude-4 . It was already clear this was an extraordinary change in coding. By the next month, July, I would be doing almost all my personal coding via Claude Code. Every agent today – Codex, OpenCode, Pi, Cursor – they all have roots in what Claude Code showed was possible. At RemObjects, that concerned us. It's also why we're well placed to help. We believe that AI poses both risk and opportunity: Languages Large language models LLMs are at their core about 'language'. How will the language of code change? Consolidation : All code migrates to the languages LLMs know best. JavaScript, Typescript, and Python have a headstart here. Obfuscation : Natural language replaces code completely. Proliferation : The barriers for any language fade away, AIs can code equally well in whichever language you already use, and the best language is used for each task. In the industry, the answer – and even how to measure it – is not yet settled https://danluu.com/pl-tokens/ . Porting and migrations Every long-lived codebase eventually faces two questions — 'can we still hire for this?' and 'can we still move fast?' – and at the foundation of CodeBot, I worried for Delphi: to a company asking these questions, was a time coming into sight when AI might make a rewrite away from Delphi seem the easy answer to both? And a year later, we’ve seen a very famous proof https://simonwillison.net/2026/Jul/8/rewriting-bun-in-rust/ that rewrites can indeed be done, though not without significant controversy https://www.theregister.com/devops/2026/07/14/zig-creator-calls-buns-claude-rust-rewrite-unreviewed-slop/5270743 . It may only get easier or more reliable from here https://arxiv.org/abs/2607.28271 . The same three options, with a new perspective: Consolidation: the industry settles on one language – and it's not your language. You port away or you're left behind. Obfuscation: your devs, separate from the code, lose track of what they're building. In a year you've lost everyone who knows your core IP. When customers realize, they won't trust you. If up for acquisition, diligence will find an empty gap instead of a solid core. Proliferation: all libraries come to you. An AI's knowledge comes to you. Through porting towards you, not away; through interoperability; and through knowledgeable AI, your codebase has access to more functionality than before: this means your business options and what your technology can achieve widens dramatically. Interoperability and porting If porting away is an option or risk, would AI make porting easy, in the other direction? Will companies with large Delphi codebases realize rewrites carry risk, but AI lets them move smaller, safer useful code and libraries the other way, into their app? Provide a blood transfusion? We’ve experimented porting libraries with no equivalent like BeautifulSoup to Pascal, and it’s highly positive. Could AI breathe new life into Delphi? And this is risk — maybe we will see people moving away from Delphi — and it is opportunity — maybe we can make it easy to move to Delphi. For a business with a core app written in Delphi, this means we can bring ongoing reliability for the future to the software you've built and rely on. Creating options Delphi provides great libraries, like the VCL, and is a wonderful language to write. If AI makes interoperability flow in every direction, does that mean other programming languages will get access to Delphi's libraries, like the VCL? RemObjects is already providing Delphi Island https://www.remobjects.com/elements/island/ and a way for developers to use Delphi libraries from any language in Elements: you can write a VCL or FMX app in C or Swift or Go. In fact, a common thread in many of the scenarios above – whether language irrelevance, or simplicity, or ease of porting – is interoperability . Most apps already are built with and benefit from multiple languages, and a language without good interop, or a developer using such a language, has access to fewer capabilities – which ultimately affects your options as a business. Interop brings those capabilities and broadens your options . Interop, and bringing devs to you RemObjects’ ongoing multi-decade DNA is that interop is key. Want a C library in your Pascal codebase? Easy. Want to bring a C developer into your Pascal codebase? Easy. Want to add Pascal to your Swift or Java codebase? Easy. Want to build a Mac and Windows app from the same mixed-source .pas/.cs/.go codebase? Easy. This is our DNA. This is all about bringing people, libraries and options to your software. RAD Studio acknowledges this value too: the entire point of RAD Studio itself is interop between two languages. And no codebase today is a single language. They’re all stacks. Single language is dead. In many ways this presages where AI is going. Whether it’s porting one way or the other, or writing anew, we’re seeing huge movement of code en masse. And developers are able to get on board with new languages and codebases — like your existing codebase — incredibly faster than before. We want to make developers and code come to you and the Delphi app your business relies on. And this led us to CodeBot. CodeBot for Delphi We can't predict the future precisely, but it's clear things are changing fast. We and you can be ready for it. So how does RemObjects ensure that risk is instead opportunity for Delphi, your codebase, and your business? Our answers to the above questions are: - AI will make you able to write in any language, and we make AI better at writing Delphi. We tilt this in Delphi’s direction. CodeBot fundamentally understands the language, the IDE, the libraries, your codebase, and the philosophy of good clean Delphi code. This lets any dev — including new hires who don’t know the language yet — work with your codebase. And it makes experienced developers even more productive. - We can make it easy via AI to continue your Delphi codebase, and move developers to your codebase, and use libraries and functionality in your codebase. If your business relies on a Delphi app, we can provide what you need to rely on that, and grow it, and modernize it, for the next twenty years. To continue the timeline: - June 2025: Embarcadero previewed RemObjects' vision for AI for Delphi https://www.youtube.com/live/S71vRppdnqg?si=JarG1zl-Z6RdShl4&t=626 in the form of CodeBot. - October 2025: we previewed an early build of CodeBot at EKON in Germany, showing agentic coding a given task, such as building a specific app, and doing it autonomously and working in the form designer. - January 2026: Embarcadero showed our beta of CodeBot for Delphi https://www.youtube.com/live/1xg60qJfYJM . Beta users have been using agentic AI in Delphi ever since. - July 2026: CodeBot fully publicly available https://blogs.remobjects.com/2026/07/30/codebot-the-story/ – for everyone, which means you Designed for Delphi What would an AI coding tool built not by forcing a square peg into a round hole, but designed from the beginning for the tech you use, look like? It was very clear that we could not leave this to a generic AI agent. Generic agents are built for the most common languages: Typescript, Python, Swift. And they're not built for the unique ways that environments like Delphi work. Delphi is highly based on visual design. Its forms are visually designed. It has a unique ecosystem of third party components. The AI labs build superb models — we use them — but no generic provider like Anthropic or OpenAI is going to spend the time to, say, add visual form hooks from their app into the form designer. It just isn't going to happen. There's also far less modern Delphi out there as training material than there is Python. A generic agent has potentially read much less good Delphi than your senior developers have written — and judgement about what good Delphi looks like, which component to reach for, how to structure a unit, has to be built in deliberately. While some developers may switch over to CLIs easily, many developers are at home in the Delphi IDE. Something available inside the IDE, that works with it – that's useful. If you introduce AI, then rather than forcing devs to use new workflows, instead add it where your devs are already happy working. So we built the agent ourselves, and we provide the AI service ourselves, under our own commercial agreement with the model provider OpenAI. That choice is what makes the rest possible: we can tune behavior specifically for Delphi; we can make firm commitments about your source code and data retention; and one subscription covers everything — there's no separate AI subscription to buy, manage, or budget for. With CodeBot there is one vendor, one bill, one support line, one data policy. And if CodeBot gets something wrong in your codebase, it being our tech under our design and our control means you can look to us to fix it. CodeBot CodeBot is an agentic coding assistant like Claude Code or Codex, but one built for Delphi. If your business sees value in any of these, you will see value in CodeBot. CodeBot: Works like one of your developers does, in the same place they work, whether that's coding or designing UI. Knows your tech stack: your third party libraries, your internal code. Upskills new devs, and makes experienced devs more productive. Read about the story and features https://blogs.remobjects.com/2026/07/30/codebot-the-story/ , or the developer-focused https://codebot.docs.remobjects.com/Delphi/UsingCodeBot/ and team-focused documentation https://codebot.docs.remobjects.com/Delphi/UsingCodeBot/TeamUse/ . CodeBot will support your Delphi codebase as your business grows. And it doesn't make your developers come to it. CodeBot comes to your developers. Evaluating an AI coding tool Whatever you choose, a few questions are worth asking any vendor: - Is AI usage included, or do you need a separate AI subscription on top — and what's the real cost per developer, per month? - What happens to your source code, and can you get that in writing for your approvals team? - Does it work with the whole IDE — including the form designer, with the designer open — or only the text editor? - Who do you call when it goes wrong? We think those are fair questions to ask us too, so we've answered them, along with nine more, in How to evaluate an AI coding tool https://blogs.remobjects.com/2026/08/10/how-to-evaluate-an-ai-coding-tool/ with our answers. If this is a decision you're weighing, both this post and CodeBot for Managers and Decision Makers https://codebot.docs.remobjects.com/Delphi/CoreConcepts/ManagersAndPurchasers/ are written to be forwarded, and the data safety notice https://www.remobjects.com/codebot/privacy.aspx is written for your Legal or Approvals team. You can also read our announcement blog post https://blogs.remobjects.com/2026/07/30/codebot-the-story/ and point your developers to our thorough documentation https://codebot.docs.remobjects.com/Delphi/ including Core Concepts https://codebot.docs.remobjects.com/Delphi/CoreConcepts/ and Using CodeBot https://codebot.docs.remobjects.com/Delphi/UsingCodeBot/ . Questions? Contact us https://www.remobjects.com/contact.aspx — we're here to help.