Loading video...

Video Failed to Load

Go Home

The W&B MCP server is officially LIVE! Coding agents could always read your code. Now they can read your experiments, monitor training, and drive their own research loops. 20 tools, hosted on every W&B deployment, plugs into Claude Code, Cursor, Codex, Gemini-CLI, and LeChat.

16,305 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Karpathy's Agentic Engineering finally has proper tooling! (built by Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.

Akshay 🚀

254,599 views • 16 days ago

Andrej Karpathy, the CEO of Obsidian, and Claude Code just built the smartest second brain on earth. It started with a 1-page gist that 21M people read. Karpathy frame flips everything you know about notes: Obsidian is the IDE, Claude Code is the programmer, and your notes are the codebase. You don’t ask AI questions it forgets by tomorrow you make it maintain a living wiki. 3 commands run the whole system. Ingest: drop an article, a podcast, a PDF, and Claude splits it into atomic pages linked to everything you already know. Query: ask anything and it answers from your own notes, in your own words, citing your own pages instead of guessing from training data. Lint: once a week Claude walks the entire vault, flags contradictions, kills stale claims, and wires orphan notes back in. Then Steph Ango made his move. The Obsidian CEO didn’t bolt an “Ask AI” button onto the app he shipped 5 skill files that teach Claude to write Obsidian’s native language: wikilinks, Canvas, Bases, the CLI. The repo crossed 13,900 stars in weeks and sits at 41,000 now. Karpathy runs it on his own reading: 100 articles and 400,000 words, cross-linked and maintained while he sleeps. No vector database, no embeddings, no $20 a month memory app just a folder of plain markdown and an agent that never gets tired of the boring part: the linking, the filing, the upkeep that killed every Zettelkasten since 1965. Your vault has 3,000 notes nobody will ever reopen. His read all of themselves by breakfast. Every app promised a second brain this is the first one that thinks.

West Lord

469,682 views • 2 days ago

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

56,183 views • 2 months ago

Meta just shipped the official Ads CLI 🤯 The first time you can plug Claude Code directly into your Meta ad account without a third-party connector or (allegedly) getting your account banned. Plug it into Claude Code and Claude can pull live performance data, build dashboards, and analyze creative fatigue, all from one prompt. Here's what's possible inside Claude Code: → Pull last 30 days of campaign performance into a styled HTML dashboard → Find every ad with frequency over 3.0 or CTR drops over 20% week-over-week → Generate weekly client reports written in your brand voice → Run anomaly detection on spend, CPM, and conversions → Build creative fatigue alerts that flag dying ads before CPAs blow up The biggest difference from every third-party Meta MCP that's been floating around: This one is built and maintained by Meta themselves. Most folks running Meta ads won't touch third-party connectors because the ban risk is real. The official CLI (mostly) eliminates that. It's your token, your app, your direct connection to Meta's API. I put together the complete playbook: → The exact 15-minute setup: Meta Developer App, system user, asset assignment, token generation → 20+ prompt templates for reporting, fatigue detection, opportunity scoring, and anomaly analysis → A weekly operating cadence: Monday performance pull, Wednesday creative review, Friday exec brief → Rate limit guardrails so you don't trip Meta's automated enforcement → The 5 prompts to run first Want it for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

35,406 views • 2 months ago