Seniority used to mean years of knowing where everything is. Now that knowledge is one question away, for the new colleague as much as for the expert.
Every answer starts in a code index of your own application, so the assistant follows the real path from a screen to the database instead of guessing.
Right inside the RCD Designer: the assistant reads the ticket, finds the code, writes the change, compiles it and explains it. Nothing is saved.
The proposal opens next to your own version, with the reason for every change. Accept it, discard it, or ask a follow-up.
Why this change: payments were saved without looking at the customer’s credit limit. The check runs in ValidateRecord, before the record is written, so it also covers imports that use this endpoint. A limit of 0 means “no limit”, as everywhere else in the application.
In the designer and in the code editor, in your own words.
A senior does not invent field names. Neither does the assistant: it works from your real application and proven RCD patterns, and code checks every result.
Every table, field, format and value list is looked up in your actual database definitions before a line is written.
A library of confirmed screen and endpoint shapes, cross-checked against real production applications.
The RCD linter and the real OpenEdge compiler catch recurring mistakes for free, before anyone reviews.
It may read the RCD framework and legacy windows to understand them, but it never changes them. Read-only designer accounts cannot use it.
While your team sleeps, the assistant updates its knowledge of each project, with low priority and mostly without AI.
lessons/screen-captions-translation.md, and uses it in later conversations for the whole team. Each project keeps its own knowledge.No. It takes the searching, the routine changes and the checks off their hands, so every developer can work with the knowledge of a senior. Developers still decide what is saved.
No. It only proposes changes. The designer shows the changed screen and the code editor shows every changed file before and after; you save what you accept.
It uses a code index of your application (who calls what, which programs read or write a table or field, which endpoints a screen uses), the database definitions and the confirmed RCD patterns. The index is refreshed every night.
Yes. With your own Jira account it reads the ticket and its attachments. If the fix is clear it proposes it; otherwise it asks at most three precise questions and shows what it found.
The RCD framework and legacy windows: it may read them to understand your application, but it never changes them.
The checks and the code index run without AI. Questions use an AI model, with a cost limit per question, and the nightly summaries use a small, low-cost model.
Fill in the form below and we will contact you as soon as possible!
"*" indicates required fields