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

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

На главную

Today on Training Data, the OpenAI team behind ChatGPT agent explain how Agent Mode works, combining: 1) Deep Research (text based research agent) 2) Operator (GUI/action based computer agent) 3) Other new tools (terminal, computer apps) 4) Tied together with shared state to create an agent that's highly capable...

44,149 просмотров • 1 год назад •via X (Twitter)

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

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

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

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,343 просмотров • 1 год назад

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 просмотров • 28 дней назад

What does the reputation model look like for agents? (alpha leak below) And how do we associate the proofs that we have about human beings with the agents who represent them? You may have heard of a process called KYC or Know Your Customer. That's very common with traditional financial applications and services. We have introduced a concept that we call KYA or Know Your Agent, which is a structured way to be able to express what model, how data was used in training, who the deployer is, what entities this agent instance is accountable back to, providing not only provenance but identity of the associated organization or entity. That's also another root of trust that we think about a lot: Enterprises and organizations tied back to things like their domains. To share a little bit of an alpha leak here, a product that we're excited to be rolling out in the next few weeks will allow our enterprise partners to more easily verify and prove the traits and capabilities of their teams as well as their counterparties. On the agent front, that makes it really easy to prove that an agent is acting on behalf of a given business or entity. We've already seen lawsuits where the absence of such technology has been a huge risk, such as with airlines that incorporate ChatGPT wrappers in their support pages. And then those AI enabled interactions end up making up plane tickets that don't exist and those airlines have to honor them. As small of an example as that might be, being able to prove agent accountability also unlocks a huge set of opportunities for use in enterprise for those agent to agent interactions. The Deep Trust Framework that our team has put together that we're excited to be bringing into a friendly SDK form in the next few weeks for some of our partners includes those reputation based capabilities, so how you can basically keep track of the interactions an agent has had, associate all of that to the entity to which they're accountable, and then that creates a sustainable reputation model for these agent to agent Interactions. Source: Billions CEO Evin McMullen evin speaking at House of Chimera Spaces Event Dec 3, 2025

Billions Network

68,484 просмотров • 7 месяцев назад

Systematic literature reviews take 12-18 months to complete. Looks like AI is going to fully automate systematic reviews sooner than later. SciSpace ( SciSpace) just launched an autonomous AI agent that conducts a systematic literature review with a single prompt. Go to scispace[.]com and run the following prompt: "Conduct a systematic literature review on [your topic]" SciSpace agent will generate research questions based on the PICO framework. You can review these questions and edit them according to your specific requirements. The agent will also draft screening criteria that you can edit according to your needs. Then the agent asks you to select the databases you want to use and the date range for paper. After this step, everything is fully automated. The agent will search for papers in the relevant databases, it will combine and rerank the papers. Then it will start the title and abstract screening and include the papers that meet the include criteria. In the next step, it will download the full text of included papers and screen them followed by data extraction. Based on the extracted data, it generates a complete systematic literature review and also a PRISMA diagram. It will also give you a table of papers included along with the rational for including them. The only thing that is keeping AI agents to fully automate systematic literature reviews fields is the papers behind paywalls. Check out the agent at scispace[.]com and see if you find its review useful.

Mushtaq Bilal, PhD

41,855 просмотров • 3 месяцев назад

Introducing LobeHub: Agent teammates that grow with you. LobeHub is the ultimate space for work and life: to find, build, and collaborate with agent teammates that grow with you. We’re building the world’s first and largest human–agent co-evolving network. Two years ago, we built LobeChat, an open-source interface for using different AI models. Today, LobeChat has 70k+ GitHub stars and serves 6M+ users worldwide. How to fully unlock the power of models has always been a shared mission between us and the community. We started with interaction — a fundamentally new, agent-first experience. Agents are no longer passive tools invoked in a single conversation. They should be proactive, always-on units of work. Treating agents as the minimal atomic unit is also the core of our agent harness infra. Today’s agents are mostly one-off executors. Even with memory, it’s often global — and hallucinates. We build long-term agent teammates that evolve with users. Each agent has its own dedicated memory space, editable by users, allowing humans and agents to co-evolve over time. This, in turn, allows us to design clearer rewards for reinforcement learning and create cleaner environments for continual learning. Agent teammates can work in groups. Through a multi-agent system, agent groups operate faster, more cost-effective, and go beyond what single-agent systems can achieve. For example, a single agent often requires heavy user involvement to proceed step by step, whereas LobeHub can execute the same work from a single instruction, with a supervisor orchestrating agents that run in parallel or debate to produce better results. We are building the collaboration network among agent teammates — and between humans and agent teammates as well. Ease of use matters. AI intelligence and shared human intelligence are equally important. With simple instructions and tool selection, you can effortlessly build and team up with agent coworkers to deliver complex, systematic work — even assembling a quant team to execute trades. Through the LobeHub community, anyone can discover, reuse, and remix agents and agent groups, customizing them to fit their own workflows, preferences, and needs. Last but not least, our vision started with LobeChat: multi-model support is the most efficient approach for users. We believe different models excel in different scenarios. By routing across multiple models, LobeHub improves cost efficiency and unlocks capabilities that a single-model setup cannot easily support.

LobeHub

185,212 просмотров • 6 месяцев назад

this chinese developer making $320k/year as a solo contractor his secret: 5 AI agents running in parallel, each one a specialist architect, coder, reviewer, tester, ops they don’t share context, don’t step on each other, just ship he takes on projects meant for teams of 5-8 engineers delivers in half the time keeps the entire budget found this video on bilibili at 3am and watched it four times guy sitting at his desk, two monitors filled with code, and he’s barely touching the keyboard here’s what’s happening on his screen: > agent 1 (architect): designs system structure, breaks down features into tasks, decides what gets built first > agent 2 (coder): writes the actual implementation based on architect’s specs > agent 3 (reviewer): checks every piece of code for bugs, edge cases, security issues > agent 4 (tester): generates test cases, runs them, reports failures back > agent 5 (ops): handles deployment, monitoring, infrastructure five separate claude code instances running simultaneously each one has its own system prompt, its own context, its own specialty they communicate through a shared task queue, not through each other that’s the key insight - no shared context means no conflicts agent 2 doesn’t know what agent 3 is doing agent 4 doesn’t care what agent 1 decided they just pick up tasks, complete them, move on he showed his contract history: > 3D rendering pipeline for a gaming studio: $25k > automated trading dashboard: $33k > enterprise CRM rebuild: $44k all completed solo, all delivered early, all clients thought they were hiring a team the code on his screen is python with blender integration - complex stuff that would normally require 3-4 specialists he’s shipping it in days while the client expects weeks while he’s explaining the system to camera, commits are happening in the background, tests running, deployments going out all while he’s literally not touching the keyboard his API costs run about $2k/month his revenue averages $26k/month that’s a 13x return on his AI investment this is the new solo developer playbook don’t compete with teams become the team

regent0x

183,659 просмотров • 2 месяцев назад