July 1, 2026. Version 11.3 maintenance release. Build 44417.

Hi,
If I posted the wrong place, please let me know and I will repost to a proper forum.

I have been using the new AI assistant in PHPRunner 11.3 on a real production project (a quotation / delivery note / invoice system with master-detail relationships), and I would like to share my experience and a feature request.

What worked well
I asked the AI to help with tasks such as:

• Pulling delivery location and payment terms from the customer master table into the invoice header
• Calculating detail line totals, subtotal (net amount), and consumption tax, then updating the parent record
• Adding an address field to a PDF report

The AI's answers were accurate, and importantly, it told me exactly where to make each change: which event to use (e.g., JavaScript OnLoad, Before/After record events) and what code to put there. I implemented the changes by hand following its instructions, and everything worked.

In my view, this is the real strength of the AI in an event-driven tool like PHPRunner: the hardest part is not writing the code, but knowing which event the code belongs in. The AI handles that judgment very well. As a side note, it also works in Japanese, which makes PHPRunner much more accessible to my non-technical team members.

Feature request
The one thing missing: the AI session output disappears once the work is done. All the valuable information — which table/page/event was changed, what code was added, and why — exists only in the chat history.

I would like to request an "Export AI Session Summary" feature:

• Export the AI's proposals from a session as a Markdown (or HTML) file, structured as: target table / page / event name / code added / reason for the change
• Optionally, accumulate these entries inside the project as an "AI change log" that can be searched later

This would turn the AI from an implementation assistant into a documentation co-author. For teams that need to maintain design documents and change histories (which is mandatory for many of us working with enterprise clients), this would be a major productivity gain — the documentation would essentially write itself as a by-product of development.

Thanks for considering this, and thanks for a very promising first version of the AI assistant.

Akira,

thank you, it makes. We will be doing something similar in version 11.4 where we will allow AI to make changes to the whole project and more detailed change info would be relevant.