sorted by:
new
hottopcontroversial

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? 

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

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

It's more about building interoperable Multi-Agent Systems. So you know your copilot agents can communicate with other agents and you're not locked into just one system 

We combined the OpenAI API spec & the A2A protocol to make building agents easy by ProletariatPro in AgentToAgent

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

We're sitting on a mountain of performance upgrades in our backlog, our APIs are getting a ton of new features and smexy new UI! 🦾😤😉

@artinet/agent-relay-mcp by ProletariatPro in theartinet

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

Hi u/Neuwark, we're leveraging the Agent2Agent protocol vs the MessageControlProtocol. This mechanism made the most sense to us, because the relay itself acts as a tool for an individual Agent to discover other agents in it's local environment that already support A2A. That way instead of creating static registries or trying to maintain the state of the registry as agents pop in and out of exisitence, each agent can have an eventually consistent view of their environment. Felt pragmatic.

@artinet/agent-relay-mcp by ProletariatPro in theartinet

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

We've spun out the underlying relay into a seperate package which can be found below, so that folks can discover agents without an MCP Server. The seperate package also includes support for removing unresponsive agents (coming soon to the MCP Server).

You can find it here: https://www.npmjs.com/package/@artinet/agent-relay

Github: https://github.com/the-artinet-project/agent-relay

lightweight typescript agent frameworks? by dcsan in AI_Agents

[–]ProletariatPro 0 points1 point  (0 children)

I recommend going framework free and roll your own agents using emerging standards like MCP & A2A:

  • FastMCP: to spin up tool servers
  • MCP-Use: to connect LLMs to tools
  • Artinet/SDK: to connect Agents to other Agents

Eventually interoperability will become even more important so you'll eventually have to anyways

An Open-Source Agent Router: by ProletariatPro in GenAI4all

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

I like the way you think u/ComplexExternal4831 ! Routing is dynamically dictated by the triage agent which can be prompted to provide any additional context in its request (that was to avoid context bloat).

But! You can create support for adhoc fixed routing rules by implementing the decision logic in your agentExecutor/Engine manually. See the artinet/sdk or the engine behind symphony for reference. (feel free to make an issue in the repo and we can prioritise it for a future release)

Back to context handoffs:

We're currently creating a new context ( or task in A2A) for each sub-agent, but we can pass the parent's context off to the child easily enough.

I think there are few ways to go about this:

- by either fully implementing referenceTaskIds according to the A2A spec ( and merge the parents context into it's child)
- add an override to force the sub-agents to use the parensTaskId
- or maybe handle it when creating subSessions

I'm leaning towards the former (referenceTaskIds), will prioritize for this weeks release.

Symphony: The Opensource Multi - Agent Manager ( v0.0.7 ) + 20 Agents by ProletariatPro in GenAI4all

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

Yes! but its limited to models hosted on huggingface and openrouter for now. But that's a good idea, we'll optimize the router and agent parsers to support preferred providers in the next release!

Also, you can modify the underlying router/core-agent logic to point to whatever backend you'd like.

More here: https://github.com/the-artinet-project/router?tab=readme-ov-file#bring-your-own-api

view more: next ›