惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
V2EX
V
Vulnerabilities – Threatpost
MongoDB | Blog
MongoDB | Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
P
Proofpoint News Feed
Know Your Adversary
Know Your Adversary
aimingoo的专栏
aimingoo的专栏
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
C
Cisco Blogs
C
CERT Recently Published Vulnerability Notes
T
Tor Project blog
A
Arctic Wolf
L
LangChain Blog
L
LINUX DO - 热门话题
G
Google Developers Blog
Google DeepMind News
Google DeepMind News
T
Threat Research - Cisco Blogs
Stack Overflow Blog
Stack Overflow Blog
I
Intezer
爱范儿
爱范儿
P
Palo Alto Networks Blog
WordPress大学
WordPress大学
H
Hackread – Cybersecurity News, Data Breaches, AI and More
T
The Blog of Author Tim Ferriss
G
GRAHAM CLULEY
S
Securelist
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Cisco Talos Blog
Cisco Talos Blog
Security Latest
Security Latest
Martin Fowler
Martin Fowler
AWS News Blog
AWS News Blog
L
Lohrmann on Cybersecurity
C
Cybersecurity and Infrastructure Security Agency CISA
酷 壳 – CoolShell
酷 壳 – CoolShell
Recorded Future
Recorded Future
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
C
CXSECURITY Database RSS Feed - CXSecurity.com
Recent Announcements
Recent Announcements
有赞技术团队
有赞技术团队
Apple Machine Learning Research
Apple Machine Learning Research
V2EX - 技术
V2EX - 技术
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
L
LINUX DO - 最新话题
博客园 - Franky
P
Privacy & Cybersecurity Law Blog
Simon Willison's Weblog
Simon Willison's Weblog
W
WeLiveSecurity
Cyberwarzone
Cyberwarzone
The Hacker News
The Hacker News
A
About on SuperTechFans

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
The AI Agent Ecosystem in PHP - From Simple OpenAI Calls to Multi-Agent Platforms
Samuel Akopyan · 2026-05-31 · via DEV Community

Over the last two years, an entire industry has emerged around AI development within the PHP ecosystem.

Where integrating an LLM once looked like a few lines of code calling the OpenAI API, developers today are building full-fledged agent systems: with memory, tools, workflows, observability, and even teams of specialized agents.

Usually, when people talk about AI development, they talk about Python first. And for good reason. The ecosystem is packed with interesting projects: LangChain, LangGraph, CrewAI, AutoGen - the bulk of the excitement has lived there for quite some time.
But in parallel, an interesting story has been unfolding in PHP as well.

And that makes me genuinely happy.

Just a couple of years ago, PHP developers had to assemble everything manually on top of provider SDKs. Today, however, there is already a complete ecosystem of tools at different abstraction levels - from model clients all the way to platforms for managing multi-agent systems.

Let's take a look at what this landscape looks like today.


From a Single Model Request to a Full-Fledged Agent

Historically, everything started the same way.
Almost every AI project looked something like this:

$response = $client->chat()->create([
    'model' => 'gpt-5',
    'messages' => [
        [
            'role' => 'user',
            'content' => 'Analyze the customer request'
        ]
    ]
]);

For a prototype, this is more than enough.

But as soon as the system starts delivering real business value, additional requirements emerge:

  • Support for multiple models
  • Ability to switch providers quickly
  • Structured output
  • External tool calling
  • Memory management
  • Context management
  • Request tracing
  • Multi-step processing orchestration

At some point, you realize that the code surrounding the LLM is taking up more space than the business logic itself.

That is exactly why specialized AI libraries began to appear in PHP.
If we simplify things a bit, the modern ecosystem can be divided into three layers:

  • AI SDKs
  • Agent Frameworks
  • Agent Platforms

Each successive layer takes responsibility for more infrastructure work.


The modern AI development ecosystem in PHP can roughly be divided into three levels. SDKs solve model interaction problems, frameworks help build agents, and platforms manage the entire agent infrastructure.


Level One: AI SDKs

This is the foundation.

AI SDKs solve one problem: making it convenient to interact with models.

They do not attempt to manage agents or orchestrate workflows. Their responsibility ends with sending a request and receiving a response.

OpenAI PHP

Repository: https://github.com/openai-php/client
Status: Active

The official OpenAI client for PHP.

In essence, it is the most direct way to work with the OpenAI platform without additional abstractions - a low-level SDK.

It provides access to:

  • Responses API
  • Chat Completions
  • Embeddings
  • Audio API
  • Image Generation
  • Fine-Tuning
  • Files API

A typical example is as straightforward as it gets:

$response = $client->responses()->create([
    'model' => 'gpt-5',
    'input' => 'Create a short summary of the customer request'
]);

echo $response->outputText;

The advantage of this approach is obvious: complete control.

The downside is equally obvious.

As soon as you need to support multiple models or providers, you have to build all necessary abstractions yourself.


Prism

Repository: https://github.com/prism-php/prism
Status: Active

While OpenAI PHP focuses on accessing a single platform, Prism was created with a different goal in mind: providing a unified interface for multiple providers.

This is a multi-provider AI SDK.

The idea is simple: business logic should not depend on a specific model.

Today you use GPT, tomorrow Claude, next month Gemini - the application should not notice the difference.

Example:

Prism::text()
    ->using('openai', 'gpt-5')
    ->withPrompt('Hello')
    ->generate();

Switching models is literally a one-line change:

Prism::text()
    ->using('anthropic', 'claude')
    ->withPrompt('Hello')
    ->generate();

Prism becomes especially useful thanks to additional capabilities.

Structured Output

Instead of parsing free-form text, you can define the expected output structure in advance.

For example:

class SentimentResult
{
    public string $sentiment;
    public int $score;
}

The model will then return data in a strictly defined format.

For production systems, this is far more reliable than applying regular expressions to generated text.

Tools

Prism supports tool calling.

In other words, the model can decide for itself when it needs to query a CRM, database, or external API.

This is effectively where the transition from "chatbots" to "agents" begins.

Embeddings

Virtually every modern RAG project ends up using embeddings sooner or later.

Prism allows you to generate them through a unified interface regardless of the chosen provider.


Laravel AI

Repository: https://github.com/laravel/ai
Status: Active

Perhaps the most interesting player to emerge in recent months.

Laravel AI is trying to do for artificial intelligence what Laravel did for databases, queues, and infrastructure.

The main idea here is not model support.

The main idea is making AI a natural part of a Laravel application.

The code feels immediately familiar:

$response = AI::chat()
    ->model('gpt-5')
    ->prompt('Create a short summary of the customer request')
    ->send();

But the real value goes deeper.

AI integrates automatically with:

  • Queues
  • Events
  • The service container
  • Logging
  • Configuration
  • The scheduler

As a result, an LLM starts to feel like just another infrastructure dependency - roughly on the same level as Redis or PostgreSQL.


Level Two: Agent Frameworks

And this is where things start getting really interesting.

Because a model request is not yet an agent.

Imagine a customer support system.

A message arrives:

I've already contacted you three times about my refund. Nobody is responding.

What happens next?

In practice, the system usually needs to:

  • Determine sentiment
  • Assess urgency
  • Retrieve customer information
  • Check support history
  • Prepare a response
  • Save the result
  • Log all actions

You can write dozens of services manually.

Or you can use an agent framework.


In real systems, agents rarely work alone. Usually, a coordinator emerges that distributes tasks among specialized agents and then combines their results into a single response.


Neuron AI

Repository: https://github.com/neuron-core/neuron-ai
Status: Active

Today, this is one of the most mature agent frameworks in PHP.

The approach is fundamentally different.

Instead of describing a request, the developer describes an agent:

$agent = Agent::make()
    ->name('SupportAgent')
    ->instructions('You are a customer support specialist');

The agent then receives a task:

$result = $agent->run(
    'Analyze the customer email'
);

At first glance, it looks simple.

But under the hood, an entire infrastructure appears:

  • Memory
  • Workflows
  • Tools
  • RAG
  • Multi-agent systems
  • Observability
  • and much more

Philosophically, the project is remarkably similar to LangGraph from the Python world.

Why Memory Became Critical

A traditional LLM operates like this:

Request → Response
An agent works differently:
Request
  ↓
Memory
  ↓
Tools
  ↓
LLM
  ↓
Result

Memory allows the agent to consider previous actions and accumulated context.

Without it, long-running business processes are impossible.

Multi-Agent Systems

Another trend of recent months is the move away from universal agents.

More and more teams are adopting specialized roles:

Coordinator
   |
   +-- CRM Agent
   |
   +-- Sentiment Agent
   |
   +-- Reply Agent

The approach closely resembles the structure of a real team.

Each agent is responsible for its own domain.


LarAgent

Repository: https://github.com/maestroerror/laragent
Status: Active

If Neuron AI aims to be a universal agent framework, LarAgent is focused primarily on Laravel developers.

You can immediately feel Laravel's familiar philosophy:

class SupportAgent extends Agent
{
    protected string $instructions =
        'You are a support specialist';
}

Minimal infrastructure code and maximum Laravel integration.

For many teams, this may be the fastest way to start working with agents.


PapiAI

Repository: https://github.com/papi-ai/papi-core
Status: Active

A relatively young project that emphasizes strong typing and provider independence.

Architecturally, PapiAI feels like an attempt to bring modern PHP development practices into the AI world.

Its primary focus areas include:

  • Types
  • Contracts
  • Middleware
  • Tools
  • Structured responses

It's fascinating to watch AI tooling gradually inherit the architectural principles of traditional PHP frameworks.


Atlas

Repository: https://github.com/atlas-php/atlas
Status: Active

Another representative of the new generation of agent solutions.

The project is being built with modern requirements in mind:

  • Voice interfaces
  • Multimodality
  • Agents
  • Tools
  • Tracing
  • Monitoring

Atlas cannot yet be called a mature market player, but it clearly demonstrates the direction in which the ecosystem is moving.


Level Three: Agent Platforms

At a certain scale, a new problem emerges.

The challenge is no longer building an agent.

The challenge becomes managing dozens of agents.

Questions begin to arise:

  • Who handles task routing?
  • How do we track response quality?
  • How do we test changes?
  • How do we manage memory?
  • How do we understand the root causes of failures?

This is where Agent Platforms come in.


PromptlyAgent

Repository: https://github.com/promptlyagentai/promptlyagent
Status: Active

This project focuses on building complex agent ecosystems.

Its primary emphasis is on:

  • Visual orchestration
  • Multi-agent workflows
  • Tool integration
  • Agent management

In essence, it represents a shift from programming individual components to managing an entire AI infrastructure.


Vizra ADK

Repository: https://github.com/vizra-ai/vizra-adk
Status: Active

Another interesting project from the Laravel ecosystem.

It covers nearly the entire agent lifecycle:

  • Development
  • Testing
  • Memory
  • Workflows
  • Observability
  • Sub-agent interaction

Looking at industry trends, solutions like this are gradually becoming the next level of abstraction.


Where the Market Is Heading

Interestingly, PHP is now following almost exactly the same path that Python followed a few years ago.

The evolution looks like this:


Virtually every AI project goes through a similar evolution. It starts with a simple model call, then adds tools and structured output, and eventually grows into a network of interacting agents.

Everyone starts with a simple model request.

Prism::text()
    ->using('anthropic', 'claude')
    ->withPrompt('Привет')
    ->generate();

Then come tools.

Then memory.

Then workflows.

After that, specialized agents become inevitable.

And eventually comes the realization that all of this infrastructure needs to be managed somehow.

That is why orchestration and agent management platforms are currently evolving faster than SDKs themselves.


Conclusion

A few years ago, conversations about AI in PHP typically ended with discussions about which HTTP client to use for calling OpenAI.

Today, the situation looks completely different.

The ecosystem already contains solutions for virtually every level of complexity:

  • OpenAI PHP and Prism for model interaction
  • Laravel AI for deep AI integration within Laravel applications
  • Neuron AI, LarAgent, PapiAI, and Atlas for building agents
  • PromptlyAgent and Vizra ADK for managing complex agent systems

And it seems this is only the beginning.

If developers once designed APIs, services, and queues, in the coming years they will increasingly be designing agents, their memory, their tools, and the ways they interact with one another.

It is already becoming clear that a single model call is gradually turning into the new function, while an agent is becoming the new service.

That is why understanding the capabilities of the PHP AI ecosystem is becoming an essential skill for any backend engineer planning to build the next generation of AI products.

Are you ready for these changes?

If you're interested in AI in PHP, you can dive deeper into the topic through my free book: "AI for PHP Developers: Intuitively and Practically."