Neuron AI - PHP Agentic Framework

02/09/2026

Heading to Basilicata this September? 🇮🇹

Our CTO Valerio Barbera will be on stage at Come to Code 2026, a community conference for developers, makers and curious minds from all over Italy, at Palazzo Gaeta in Pignola on September 26 and 27.

His talk is "Agents Building Agents." 🤖 What does it mean for agents to build other agents? Valerio will make it concrete, and show how you can build it without leaving the tools you already use.

Every level welcome, no experience needed, just curiosity. Talks, workshops, panels and a few social nights too.

Come along.
Details: https://www.cometocode.it/
Tickets: https://ticket.cometocode.it/PLUGAPS/ctc26/

01/09/2026

Two talks, on one of the PHP world's longest-running stages. 🇩🇪

Our CTO Valerio Barbera is speaking at the International PHP Conference in Munich, running October 26 to 30.

The talk we can share: "Let's Build A Travel Agent that Buys Tickets for You, in Pure PHP." 🤖 A real agent that books your travel, built entirely in PHP.

And the scene is paying attention: the conference blog recently featured an AI coding agent built in pure PHP on top of Neuron.

Munich, end of October. If PHP is your world, this is a good place to be.

Talk details: https://phpconference.com/php-core-coding/ai-agent-pure-php-coding/
Program: https://phpconference.com/munich/

31/08/2026

Heading to Bologna? 🇮🇹

On October 22nd our CTO Valerio Barbera will speak at DrupalCamp Italy, the Italian Drupal conference, with a talk called "Agents building agents." 🤖

Drupal runs on PHP, and building AI agents no longer means leaving PHP behind. Valerio will show how agents can build other agents, and how to bring that into your own projects without changing your stack.

One day, one room full of Drupal and PHP people, Drupal AI and agents on the table. Come along.

Details here: https://www.drupalcampitaly.it/2026

28/08/2026

The old way: software that only follows the rules you wrote.
The new way: applications that understand, decide, and get the job done, and that you can actually measure.

Agentic-native, born agentic from the first line of code, built in PHP.

The next generation of software is already buildable. 👇

27/08/2026

"And in six months, when things change?"
Clients don't just buy what works today, they buy what keeps working.
An agentic system you can measure is one you can keep improving without breaking the promises you made: on every change, the same checks run again. It gets better over time, not more fragile.
That is the difference between a project you deliver once and a client who stays.
Built in PHP with Neuron.

26/08/2026

"What if the agent does something it shouldn't?"
It is the fear that stalls every agentic budget. The answer is not "it won't", it is "it can't, and we prove it".
On the risky actions, a person approves first. The agent never does anything irreversible on its own, and a test fails the moment it tries.
You are not selling a black box. You are selling control your client can see.
Agentic-native software, built in PHP with Neuron.

25/08/2026

Your client will ask one question that decides the deal: "how do I know it works?"
For agentic software, "trust me" is not an answer. A number is.
You run it on real cases and measure how often it actually gets the job done. That is your success rate, and you put it in the contract. "Good enough" stops being an argument at delivery: it is agreed up front.
That is how you sell an agentic project with confidence, and defend your price.
Built in PHP with Neuron.

24/08/2026

There are two kinds of software.
One is an app that exists for something else, with AI added along the way. The other is born agentic: the agent is the architecture from the first commit, driving how the whole system reasons, acts, and works.
Your next application will be that second kind. And you can build it in PHP, with Neuron.
Agentic-native.
Which side will your next project be on? 👇

21/08/2026

If you are on one framework and you plan to stay there, the official AI SDK for it is a reasonable choice. I mean it, and it is the honest starting point for everything else I am about to say.

In early 2026 Symfony and Laravel shipped their own AI SDKs. That was a relief on our side. It validated a direction we had been working in since March 2025, and it told the PHP community that this is real engineering and not a side quest.

So the question is no longer whether your framework can call a model. They all do that well now, and it is no longer where anything gets decided.

The question that is actually hard is which decisions you can still change later. Durable ex*****on, resuming after a crash, pausing for human approval, streaming a real interface to a user: these are not things you consume, they are things that change how ex*****on works. Adding them to a layer designed to abstract provider calls means reopening the foundations, which is why they tend to arrive late, when they arrive.

That matters once you are past the prototype and the agent is carrying real work. Discovering an architectural limit at that point is the most expensive version of that discovery.

I am obviously not neutral here, so do not take the criterion from me. Take the question and apply it yourself: what does my agent need to do in eighteen months, and can the layer I pick today grow into it.

Full clip: https://youtu.be/rTV-s03_4RA

20/08/2026

🧩 You saw the agent create a full Spryker product from one plain sentence, live on the storefront. The interesting part is not what it does. It is how it is built.

Here is what is actually running, and why it all stays in PHP:

🔹 It is not a chatbot bolted onto Spryker. The agent runs inside the back office, in the same stack that already runs the store. You enable it from the admin config and it is there. No separate AI service to host and keep in sync.

🔹 Structured extraction first. One sentence becomes concrete fields: product name, SKU, description, variants, price, stock per unit, category, tax set. The model reads intent, the framework turns it into a typed plan the back office can act on.

🔹 It acts through tools, not prompts. The agent calls real back office functions: list_categories, list_tax_sets, set_product_stock, assign_product_to_category, approve_product. Each is a defined tool with a defined result, not text it hopes is right.

🔹 Missing data does not break it. When the category is missing, a rigid script stops with an error. The agent notices, asks, searches the store for the closest existing category, and binds the product to it. That is a workflow with state, not a single call.

🔹 A human stays in the loop by design. Before it writes anything, it shows the exact tools it will call and a summary of the product. Nothing is created until you approve.

🔍 This is the line between a framework and a wrapper. You can follow every step: the plan, the tool calls, the state between them. When something looks off, you can see why. An agent you can inspect is one you can actually run in a real back office.

And all of it stays in PHP, inside Spryker. No rewrite, no separate service, no leaving your stack. What scales is not typing product forms by hand, it is reviewing one plan per product while the agent does the rest.

Full demo built by Hidran Arias, running inside a Spryker back office on Neuron.

Neuron, the framework that brought AI agents to PHP.

▶️ Full demo by Hidran Arias: https://www.youtube.com/watch?v=HIMS4LGxCoQ

I walk through the full flow: enabling the product creation agent i...