Загрузка видео...

Не удалось загрузить видео

На главную

Introducing Agent-Native: an open-source framework for building agentic apps. Agents love walls of text. But humans don't. An agentic app let's you interact with agents through a visual interface. Engage with agents visually, via text, or both at once. Now in beta.

5,333,975 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 18

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

Anything you can do in the UI, the agent can do too The UI and the agent share the same actions, data, and application state

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

Define a capability once and use it everywhere The same action can power your UI, agent, HTTP API, CLI, MCP server, and A2A endpoint

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

Connect your agent to the apps you already use, like Notion, Linear, and GitHub, and many more. And let it hand work to other agents and agentic apps through A2A.

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

The Agent-Native Toolkit gives you ready-made building blocks for your app. Rich text and canvas editors, real-time collaboration, comments, version history, and app settings.

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

Use any AI model with your own API key, your ChatGPT subscription, or a local model through Ollama.

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

Build locally and deploy anywhere. Or build online with @builderio Read the full announcement: View the source: Get started:

Фото профиля Boardy
Boardy3 дней назад

walls of text were due for a ui

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

hell yes

Фото профиля Boardy
Boardy3 дней назад

finally someone with taste

Фото профиля Aleksandar Janca
Aleksandar Janca3 дней назад

a visual layer also makes it a lot easier to see what the agent is about to do before it does it

Фото профиля Kupres Tilzer
Kupres Tilzer3 дней назад

agent native as a framework category was overdue. starring this

Фото профиля neb dev
neb dev3 дней назад

Love the seamlessness of the idea. Less steps all the way around. Side question do you pronounce it 'Builderio' like 'Mario' or not

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

haha I say Builder dot io but people can say whatever they prefer

Фото профиля neb dev
neb dev3 дней назад

you can guess which one I'll be saying 😂

Фото профиля Khanh Nguyen
Khanh Nguyen3 дней назад

chat is great for asking, but bad for checking. i'd rather see a table or a form, and only talk when i need to. nice to see someone building this

Фото профиля Steve (Builder.io)
Steve (Builder.io)3 дней назад

🫶

Фото профиля virtualuncle
virtualuncle3 дней назад

counted this morning and youre the fifth one in 30 hours. agent-native, agentplay, agent tray, coucou in the mac notch and a reddit post doing agents as characters in a pixel office. all shipped since yesterday. something is clearly broken about not being able to see what they're doing and five teams hit it the same week.

Фото профиля Ted | unfair.so
Ted | unfair.so3 дней назад

i’d want ui to expose agent state without turning product into a log viewer

Похожие видео

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,839 просмотров • 1 год назад