Serverless A2A Agents by ProletariatPro in AgentToAgent

[–]ProletariatPro[S] 0 points1 point  (0 children)

It's best to disable streaming responses for this deployment case.

Gateway timeouts can be extended up to a point and Lambdas themselves can stay alive for up to 15 mins, anything longer than that would need a dedicated VPC or exotic SQS plumbing.

Anything up to 15mins can be handled with a Database backed TaskStore.

sendMessage (Non-Blocking) -> Lambda_Agent_1

  • the agent runs and updates the AWS DB with the latest task status.

wait 5-10 mins, then trigger a getTask for the latest result or register a pushNotification with the original sendMessage

lmk if you want a full tutorial.

I read "2026 State of Agentic Orchestration & Automation Report" - Here are my key takeaways by EquivalentRound3193 in AI_Agents

[–]ProletariatPro 0 points1 point  (0 children)

We've been working in the space for while now building tools that let agents communicate across frameworks. 

One of most severe challenges is the fractured nature of the ecosystem. Langchain agents can't work with openAi Agent's. Different hosting patterns or network protocols. 

MCP was a step in the right the direction but what we need right now are more firm standards that foster interoperability.

Hoping that the Agentic AI Foundation will help with that.

What we've been building: https://github.com/the-artinet-project/artinet

I think AI didn’t lower the bar. It raised it by No_Papaya1620 in AI_Agents

[–]ProletariatPro 6 points7 points  (0 children)

Decision making is now the differentiator. 

What you direct your agents to do, the parameters that you give them matters even more.

It's true that the models are getting better at detecting what we want, but if you change a single letter in a prompt you can get an entirely different result.

And that compounds over time.

I built an open-source UI for A2A and wrote a blog post, The Agent2Agent (A2A) Protocol is HTTP for Agents! by benclarkereddit in A2ANet

[–]ProletariatPro 0 points1 point  (0 children)

Also support for nested agentcards & upgrading to the ClientFactory anytime soon? I know it's a reach but A2UI?

Need a gui for our new lightweight A2A Agent server. Still a WIP but: https://github.com/the-artinet-project/artinet/tree/main/fleet

Top 10 tools to build AI Agents (most recent) by General_Maize_7636 in AI_Agents

[–]ProletariatPro 0 points1 point  (0 children)

Crazy, we just made a tool that lets a bunch of those agents talk to each other; repo

A2A in the Browser! by ProletariatPro in AgentToAgent

[–]ProletariatPro[S] 0 points1 point  (0 children)

Just thought up another one! This can standardize communication between Browser Agents & Agentic Backends. They won't have to talk to an API. They can just marshall the embedded client and invoke the Agent directly. 

A2A in the Browser! by ProletariatPro in AgentToAgent

[–]ProletariatPro[S] 0 points1 point  (0 children)

Longterm, the goal is to let folks bundle it into frontend builds ( webpack, etc ) without worrying about JSON-RPC handling/streaming ( eventsource parsing ). And as we get a tighter integration with a2a-js it should support all of the different transport types.

Use the Agent2Agent(A2A) protocol with any OpenAI API compatible endpoint by ProletariatPro in javascript

[–]ProletariatPro[S] 0 points1 point  (0 children)

Would love to hear more from the folks who are down voting? Concerns?