After MCP, A2A, & AG-UI, there's another Agent protocol.
It's fully open-source and launched by IBM Research.
Here's a complete breakdown (with code):
ACP is a standardized, RESTful interface for Agents to discover and coordinate with other Agents, regardless of their framework.
Just like A2A, it lets Agents communicate with Agents. There are some differences, which we shall discuss later.
Let's dive into the code first!
Here's how it works:
- Build the Agents and host them on ACP servers.
- The ACP server receives requests from the ACP Client and forwards them to the Agent.
- ACP Client itself can be an Agent to intelligently route requests to the Agents (like MCP Client does).
Check this 👇
We’ll create a research summary generator, where:
- Agent 1 drafts a general topic summary (built using CrewAI)
- Agent 2 fact-checks & enhances it using web search (built using Smolagents).
Start by installing some dependencies and a local LLM using Ollama.
Check this 👇
In our case, we’ll have two servers, and each server will host one Agent.
Let’s define the server that will host the CrewAI Agent and its LLM.
Here's how we do it 👇
Next, we define an Agent on this server.
- Line 1 → Decorate the method.
- Line 6-21 → Build the Agent and kick off the Crew.
- Line 23 → Return the output in the expected ACP format.
- Line 26 → Serve on a REST-based ACP server running locally.
Check this 👇
Next, repeat these steps for the 2nd server to host the Smolagents Agent and its LLM.
- Line 1-10 → Imports + define the Server & the LLM.
- Line 12 → Decorate the method.
- Line 21-28 → Define the Agent with a web search tool.
- Line 31 → Serve the Agent.
Check this 👇
Finally, we use an ACP client to connect both agents in a workflow.
- Line 6-7 → Connect the client to both servers.
- Line 11-14 → Invoke the first agent to receive an output.
- Line 18-21 → Pass the output to the next agent for enhancement.
Check this 👇
Almost done!
Run the two servers as follows 👇
And then run the client to get an output from a system that’s powered by ACP using `uv run acp_client[.]py`
Check this 👇
This demo showcases how you can use ACP to enable Agents to communicate via a standardized protocol, even if they are built using different frameworks.
It's also important to understand how ACP differs from A2A.
Check this out👇
That's a wrap!
If you found it insightful, reshare with your network.
Find me → @akshay_pachaar ✔️
For more insights and tutorials on LLMs, AI Agents, and Machine Learning!
dLLM is a Python library that unifies the training & evaluation of diffusion language models.
You can also use it to turn ANY autoregressive LM into a diffusion LM with minimal compute.
100% open-source.
Here's why this matters:
Traditional autoregressive models generate text left-to-right, one token at a time. Diffusion models work differently - they refine the entire sequence iteratively, giving you better control over generation quality and more flexible editing capabilities.
You're in a Research Scientist interview at Google.
Interviewer: We have a base LLM that's terrible at maths. How would you turn it into a maths & reasoning powerhouse?
You: I'll get some problems labeled and fine-tune the model.
Interview over.
Here's what you missed:
When outputs are verifiable, labels become optional.
Maths, code, and logic can be automatically checked and validated.
Let's use this fact to build a reasoning model without manual labelling.
We'll use:
- @UnslothAI for parameter-efficient finetuning.
- @HuggingFace TRL to apply GRPO.
Let's go! 🚀
What is GRPO?
Group Relative Policy Optimization is a reinforcement learning method that fine-tunes LLMs for math and reasoning tasks using deterministic reward functions, eliminating the need for labeled data.
Here's a brief overview of GRPO before we jump into code:
NOBODY wants to send their data to Google or OpenAI.
Yet here we are, shipping proprietary code, customer information, and sensitive business logic to closed-source APIs we don't control.
While everyone's chasing the latest closed-source releases, open-source models are quietly becoming the practical choice for many production systems.
Here's what everyone is missing:
Open-source models are catching up fast, and they bring something the big labs can't: privacy, speed, and control.
I built a playground to test this myself. Used CometML's Opik to evaluate models on real code generation tasks - testing correctness, readability, and best practices against actual GitHub repos.
Here's what surprised me:
OSS models like MiniMax-M2, Kimi k2 performed on par with the likes of Gemini 3 and Claude Sonnet 4.5 on most tasks.
But practically MiniMax-M2 turns out to be a winner as it's twice as fast and 12x cheaper when you compare it to models like Sonnet 4.5.
Well, this isn't just about saving money.
When your model is smaller and faster, you can deploy it in places closed-source APIs can't reach:
↳ Real-time applications that need sub-second responses
↳ Edge devices where latency kills user experience
↳ On-premise systems where data never leaves your infrastructure
MiniMax-M2 runs with only 10B activated parameters. That efficiency means lower latency, higher throughput, and the ability to handle interactive agents without breaking the bank.
The intelligence-to-cost ratio here changes what's possible.
You're not choosing between quality and affordability anymore. You're not sacrificing privacy for performance. The gap is closing, and in many cases, it's already closed.
If you're building anything that needs to be fast, private, or deployed at scale, it's worth taking a look at what's now available.
MiniMax-M2 is 100% open-source, free for developers right now. I have shared the link to their GitHub repo in the next tweet.
You will also find the code for the playground and evaluations I've done.
Claude Skills might be the biggest upgrade to AI agents so far!
Some say it's even bigger than MCP.
I've been testing skills for the past 3-4 days, and they're solving a problem most people don't talk about: agents just keep forgetting everything.
In this video, I'll share everything I've learned so far.
It covers:
> The core idea (skills as SOPs for agents)
> Anatomy of a skill
> Skills vs. MCP vs. Projects vs. Subagents
> Building your own skill
> Hands-on example
Skills are the early signs of continual learning, and they can change how we work with agents forever!
Here's everything you need to know:
Skills vs. Projects vs. Subagents:
If you found it insightful, reshare with your network.
Find me → @akshay_pachaar ✔️
For more insights and tutorials on LLMs, AI Agents, and Machine Learning!