正在加载视频...

视频加载失败

Introducing NEO: The first Autonomous Machine Learning Engineer. It works like a full-stack ML engineer that never sleeps: handling data exploration, feature engineering, training, tuning, deployment, and monitoring, end to end. Powered by 11 specialized agents, NEO runs autonomously, saving ML engineers thousands of hours and making them 10x...

861,524 次观看 • 1 年前 •via X (Twitter)

39 条评论

Neo AI 的头像
Neo AI1 年前

Get early access: ✅ Neo is production-ready: ✅ Native integrations: Snowflake, Databricks, BigQuery, and more ✅ Deployable in your own VPC

Neo AI 的头像
Neo AI1 年前

Watch NEO develop multiple ETA prediction models and perform comparative evaluation:

Neo AI 的头像
Neo AI1 年前

Doing sleep stage data exploration and feature analysis using a publicly sourced wearable dataset:

Neo AI 的头像
Neo AI1 年前

Improving the word error rate for whisper model on clinical speech dataset:

Neo AI 的头像
Neo AI1 年前

Decomposing word-word correlation matrix and computing non-negative matrices:

Rumi Guzder 的头像
Rumi Guzder1 年前

I've been using it all day, and I'm actually blown away by what it can do. The only problem is, you kind of have to be an ML Engineer to truly appreciate how good it really is.

Dipti Sharma 的头像
Dipti Sharma1 年前

NEO looks like a total game-changer—ML engineers are about to get superhuman!

Yohannes Melese 的头像
Yohannes Melese1 年前

This marvels Ai creating ai this mindblowing

SARAH 的头像
SARAH1 年前

Love how @withneo demonstrates real applications from model evaluation to speech improvement. Practical AI in action

Tobe Duru 的头像
Tobe Duru1 年前

the end of human engineers is near

Tinormous 的头像
Tinormous1 年前

@threadreaderapp unroll

H A J R A 的头像
H A J R A1 年前

Sounds like a game changer

Matheus | IA 的头像
Matheus | IA1 年前

Isso parece incrível!

sanket patel 的头像
sanket patel1 年前

can it weild dspy

Neo AI 的头像
Neo AI1 年前

That’s a work in progress

sanket patel 的头像
sanket patel1 年前

looking forward. that's what I would want from an "AI" Engineer, as opposed to an "ML" Engineer.

Shanti Greene 的头像
Shanti Greene1 年前

Has the early access started yet?

Neo AI 的头像
Neo AI1 年前

Almost there…

Muhammad Ayan 的头像
Muhammad Ayan1 年前

soooo insaneeeee nothing crazier than an “engineer” that never sleeps

Aaliya 的头像
Aaliya1 年前

This is next-level 👀 Turning ML engineers into superhumans sounds like a real game-changer.

Kim Noël ⚡ 📖 的头像
Kim Noël ⚡ 📖1 年前

Yet another startup to be deleted by an update of Codex of Claude Code

Rippa Sats 的头像
Rippa Sats1 年前

🤯🤯🤯 You knocked it out of the park The Human in the loop feature is the 🍒 on top 🤌

Himanshu Kumar 的头像
Himanshu Kumar1 年前

Automation's potential is vast. Consider the implications for accessibility and scaling expertise. What breakthroughs might this unlock?

Rasel Hosen 的头像
Rasel Hosen1 年前

This sounds amazing! Can't wait to see how NEO changes the game in ML. A 24/7 engineer? Sign me up!

Alice The Ai Expert 的头像
Alice The Ai Expert1 个月前

NEO is incredible truly superhuman ML engineering that never sleeps!

Metabolic Uncle 的头像
Metabolic Uncle1 年前

Guys, that´s a Sigma in your logo. Not an Epsilon.

Sheral Tech 的头像
Sheral Tech1 个月前

NEO is revolutionary making every ML engineer truly superhuman now. 🤖🚀

Abigail Parker 的头像
Abigail Parker1 年前

Love it

Enzo Sanchez | IA 的头像
Enzo Sanchez | IA1 年前

Hey let’s Connect us

Kunwar Nabeel 的头像
Kunwar Nabeel1 年前

So greattt!!!!

Silicon 的头像
Silicon1 年前

@VictorOkporiaku

Dan Ciobanu 的头像
Dan Ciobanu9 个月前

I am currently building and app with NEO and I started paying for credits, I am asking i NEO to build and make available an apk kit for testing its functionality and it provided a very basic mock app. I have sent instructions to improve it, but nothing happens, loops taking money

Mykhailo Sorochuk 的头像
Mykhailo Sorochuk1 年前

Impressive tech, but will it replace engineers or just boost their productivity?

Neo AI 的头像
Neo AI1 年前

We are about augmentation. Neo is designed to help ML engineers build faster.

Anissa 的头像
Anissa1 个月前

Autonomous ML engineering is moving fast. NEO handling the full workflow is seriously impressive. DM me please

Aria Tech 的头像
Aria Tech1 个月前

11 agents doing the full ML loop is insane

Paul Cox 的头像
Paul Cox1 年前

Can you pls send me a DM? Got an issue with my credentials...

mmkz 的头像
mmkz11 个月前

Hi, is there anyway can I try your service? I'm in the middle of the Time series forecasting project where I want to accelerate the entire process but I don't see any subscription plan.

Ella Tech & Tool 的头像
Ella Tech & Tool1 个月前

This is insane 🔥 10x ML engineers just got real

相关视频

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 年前

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

229,643 次观看 • 6 个月前

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 次观看 • 4 个月前