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

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

На главную

GPT-6 Astra has solved the problem of 3D anatomy tools and created an Anatomical Atlas with WebMCP support 3D anatomy tools have had a control problem for years, and almost nobody built a real fix. Every viewer forces the same workflow: click, drag, zoom, repeat, just to reach the...

24,675 просмотров • 21 часов назад •via X (Twitter)

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

Фото профиля Curious Nori | AI · Food · Travel
Curious Nori | AI · Food · Travel21 часов назад

Really enjoyed this.

Фото профиля Zentrix⌚️
Zentrix⌚️21 часов назад

Now this is something new. It looks really cool

Фото профиля Leonardo Correa
Leonardo Correa16 часов назад

That is impressive @ZentrixHQ!! Would you share the code on GitHub? Can you open source it? Thanks!!

Фото профиля OpenGradient (∇, ∇)
OpenGradient (∇, ∇)19 часов назад

one good example where learning and teaching becomes fun and interactive thru ai built techs 😎

Фото профиля Zentrix⌚️
Zentrix⌚️19 часов назад

yes, when AI turns learning into something interactive, it stops feeling like studying and starts feeling like exploring

Фото профиля Fajar M Reza
Fajar M Reza19 часов назад

WebMCP could make 3D anatomy tools more accessible when interactions remain auditable.

Фото профиля Dipanshu Kushwaha
Dipanshu Kushwaha21 часов назад

That's incredible! It sounds like a huge breakthrough for 3D anatomy tools. Great job on solving th

Фото профиля Mihnea
Mihnea13 часов назад

it did let you generare a penis?

Фото профиля Mr.SahaRok
Mr.SahaRok21 часов назад

The bigger breakthrough isn’t the anatomy atlas. It’s turning passive software into something an AI agent can actually operate. If WebMCP makes existing tools agent-controllable without rebuilding them from scratch, the browser could become one giant API. 👀

Фото профиля ROBINHOOD KING 👑🚀
ROBINHOOD KING 👑🚀11 часов назад

Let's pump it 💪 Can we talk privately? Dm me now 📥

Фото профиля volovuk
volovuk14 часов назад

Astra solved 3D anatomy’ is doing a lot of work for what’s actually a WebMCP wrapper — the model isn’t what changed, the tool exposing its actions to any agent is. Swap Astra for any other model with function-calling and this works identically. The framing credits the LLM for what’s really a UI/API design choice

Фото профиля Peik Gabriel
Peik Gabriel17 часов назад

the webmcp layer is the real unlock, the atlas is just the first convincing proof

Фото профиля catman
catman20 часов назад

the cross-section scrolling is the real test here: can an agent preserve the same anatomical landmark while moving through slices? if it can, that seems more useful than simply automating the camera angle.

Фото профиля Patryk | AI Lead & Automation
Patryk | AI Lead & Automation18 часов назад

WebMCP replacing click/drag/zoom is the interesting bit agent-operable controls beat another screenshot loop (claiming Astra here — treating that as the author's label)

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

WebMCP by Microsoft and Google is HERE and I'm surprised more people aren't talking about it. Why does it matter? BILLIONS of dollars are about to move through agents, and the internet isn't built for them yet. 1. SEO was about Google understanding your page. 2. AEO was about AI citing you. 3. WebMCP is about the agent actually finishing the job (buying, researching, requesting quote etc). WebMCP is basically websites with agent buttons. Instead of an agent scanning a page like a human, screenshotting and guessing where to click, the site just tells it "here's how to search, here's how to book, here's how to buy." 2 cash flowing businesses you could start today using WebMCP: 1. A WebMCP conversion agency Make boring business websites agent-ready. Law firms, HVAC, med spas, dentists. Build them the first tools (request a quote, book a consult), sell the setup for $2k, then charge a few hundred a month to monitor and improve it. 2. An agent mystery shopper. Test whether agents can actually complete the important journeys on someone's site, buying the hoodie, booking the consult, filing the claim. Hand them a report on where the agent got stuck, missing tools, bad descriptions, lost conversions. Charge monthly, then turn the repeated fixes into software. Full episode on The Startup Ideas Podcast (SIP) 🧃 with Vinny below You'll learn what WebMCP really is, see examples of it IN ACTION, and hear more about 2 startup ideas using WebMCP you can start today. WebMCP is pretty cool. Watch.

GREG ISENBERG

179,354 просмотров • 19 дней назад

your agent has thirty tools. it calls two of them. the other twenty eight are not sitting idle somewhere. they are in the request, every request, and they are doing damage in two places at once. first the obvious one. tool schemas go into the prompt, and a schema is not a name. it is a description, a parameter list, types, required fields, an example. thirty of those is a few thousand tokens that ship with every single call, including the ones where the agent just says thanks and stops. you are paying rent on twenty eight tools that have never fired. second, and this is the one that costs more. when the request says cancel the order, the model picks by matching against everything available. four of your tools are plausible: cancel_order, refund_order, update_order, void_order. it is choosing among them based on the descriptions you wrote, one afternoon, months ago. every tool you add is another candidate in that shortlist. the twenty eight you never call are not neutral. they are noise in the one decision that determines whether the run works. > why it grows without anyone deciding to nobody adds thirty tools on purpose. you add one for a task, it works, it stays. six months later the registry is a catalogue and no one has ever removed anything, because removing a tool feels risky and adding one feels free. and there is no feedback telling you otherwise. the unused ones never error. they never appear in a failing trace. they are invisible in exactly the way that lets them accumulate. > what to actually do count calls per tool over the last thousand runs. this is one group-by and it usually shocks people. the ones at zero are pure cost. ship the tools the task needs, not the whole registry. a research phase does not need deploy. a writing phase does not need the database. swap the set between phases instead of loading everything up front. same agent, different tools, depending on where the run is. and when two tools could both plausibly answer the same request, that is not redundancy you can ignore. it is a coin flip you built into the system. the twenty eight tools are not unused. they are used every time, by the part of the run you cannot see.

Hanako

24,656 просмотров • 1 месяц назад

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.

Avi Chawla

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