· via dev.to (home feed)
Neuron AI 4 rewrites workflow engine, swaps Guzzle and widens UI protocol support
Neuron AI 4, the new major release of the PHP agentic framework, rewrites the workflow engine, replaces chat history with a message store and swaps Guzzle for an ext-curl client.

Neuron AI, a framework for building agentic applications in PHP, has released version 4. Announced in a post on dev.to dated 1 October, the release rewrites the internal workflow engine, replaces the chat-history API with a message store, drops Guzzle as a dependency and broadens support for the frontend protocols that carry agent output into user interfaces.
A rewritten workflow engine
The Workflow engine, introduced as the framework's core architecture in version 3, was rebuilt from the ground up to slim down the public API. The maintainer's own critique of v3 is that developers had to reach too far into the execution machinery to get things done; in v4, starting an agent, approving a tool call and resuming execution are meant to be short, readable operations.
The announcement frames v3's workflow-first design as a gamble that paid off, with developers shipping production agents on top of it. That result, the maintainer writes, is the ground v4 now builds on.
A new message store
Chat history was reworked with two aims: separating persistence from history and context-window handling, and making it easier to embed Neuron in an existing application.
In practice, ChatHistoryInterface is gone. The new public APIs sit on MessageStoreInterface, which does nothing but store messages in a persistence layer. When messages fall outside the model's context window they are flagged as archived rather than discarded, so the model sees a trimmed conversation while the application keeps the complete record — a useful property for long-running agents.
Performance and the HTTP layer
The internal streaming pipeline received a thorough review, and the announcement claims streaming is now quicker and steadier, with several bugs and bottlenecks eliminated along the way. Applications that lean on streaming are advised to upgrade promptly.
Guzzle is no longer a dependency. The default HTTP client is now a low-level implementation built on PHP's ext-curl extension, a change the maintainer attributes to performance.
Frontend protocol support
Integration with UI protocols now renders custom events and human-in-the-loop checkpoints automatically. The post argues that wiring agents into the user interface is critical for shipping real products, and that limits in v3's architecture made full protocol support awkward. In v4 the streaming adapter system moves out of the Agent component and becomes part of the underlying Workflow engine.
The PHP question
Much of the announcement addresses the scepticism that dogged the project's first year: whether PHP could genuinely match Python for agent work. The maintainer, a professional PHP developer since 2011 by their own account, says those questions faded once v3 shipped. The stated ambition now is for PHP to become a leading environment for what the announcement calls "agentic-native" applications — software shaped by the agent's reasoning loop, its capabilities and memory, and the checkpoints where a human steps in, rather than a conventional web app with an AI feature attached at the edge.
For existing users, the maintainer describes migration from v3 as an afternoon-sized job that could be delegated to a coding agent. The project has also begun offering kickstart training sessions for teams adopting the framework.
Why it matters
Agentic tooling has so far been concentrated in Python and TypeScript, leaving PHP teams with an awkward choice: pick up a second stack under delivery pressure, or pass on agent work altogether. Neuron's arc — production agents shipped on v3, a simplified API in v4 and now formal team training — suggests the PHP ecosystem is assembling a workable alternative.
The upgrade is not free: a public interface has been removed and the default HTTP client has changed, so v3 users should test the transition rather than take the "one afternoon" framing on faith. Still, if the streaming improvements and the workflow-level adapter system hold up in production, version 4 makes it materially cheaper for PHP shops to build agent-driven software in the language they already run.
- #php
- #ai-agents
- #llm
- #php-framework
- #developer-tools