Loading video...

Video Failed to Load

Go Home

🔥 Introducing `npx agentlytics` a local, offline analytics dashboard for your AI editors. If you're switching between: you finally have one place to see all your sessions, tokens, tool calls, and model usage 👀 No cloud or sign-up required. →

37,697 views • 4 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I just vibe coded a Meta Ads creative analytics tool in Claude Code 🤯 It plugs into your ad accounts, AI-analyzes every creative you've ever run, and tells you exactly what's working, what isn't, and WHY. Built 100% in Claude Code. Perfect for DTC brands and creative agencies who are sick of staring at Ads Manager trying to reverse-engineer why one ad scaled and another tanked. If you're pulling weekly reports that show you spend, ROAS, CTR, and hook rate but never tell you WHY any of it is happening — and you're stuck watching videos one by one, guessing at angles, and making kill/scale calls on gut feel... This tool runs the entire loop for you: → Connect your Meta ad accounts in one click → AI watches every video and analyzes every static → Auto-labels each ad by asset type, messaging angle, hook tactic, and funnel stage → Win rate analysis broken down by every category → Kill/scale recommendations segmented by TOF, MOF, and BOF → AI-generated iteration recommendations for every underperformer No manual video watching. No guessing at what's working. No spreadsheets to track creative performance. What you get: - A full creative analytics dashboard pulling live from your accounts - AI classification on every ad you've ever run - Iteration priorities ranked by ads with real spend behind them - Weekly reports surfacing top and bottom performers with AI insights Built 100% in Claude Code as a real tool, not a one-off script. I recorded a full walkthrough showing exactly how this works and what every feature does, including ALL the prompts I used so you can build it yourself. Want access to all the prompts for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

54,627 views • 2 months ago

Introducing Pods Hyperspace Pods lets a small group of people - a family, a startup, a few friends, to pool their laptops and desktops into one AI cluster. Everyone installs the CLI, someone creates a pod, shares an invite link, and the machines form a mesh. Models like Qwen 3.5 32B or GLM-5 Turbo that need more memory than any single laptop has get automatically sharded across the group's devices - layers split proportionally, inference pipelined through the ring. From the outside it looks like one OpenAI-compatible API endpoint with a pk_* key that drops straight into your AI tools and products. No configuration beyond pasting the key and changing the base URL. A team of five paying for cloud AI burns $500–2,000 a month on API calls. The same team's existing machines can serve Qwen 3.5 (competitive on SWE-bench) and GLM-5 Turbo (#1 on BrowseComp for tool-calling and web research) for free - the hardware is already on their desks. When a query genuinely needs a frontier model nobody has locally, the pod falls back to cloud at wholesale rates from a shared treasury. But for the daily work - code reviews, refactors, research, drafting - local models handle it and nobody gets billed. And when it is idle, you can rent out your pod on the compute marketplace, with fine-grained permissions for access management. There's no central server involved in inference. Prompts go from your machine to your pod members' machines and back: all of this enabled by the fully peer-to-peer Hyperspace network. Pod state - who's a member, which API keys are valid, how much treasury is left - is replicated across members with consensus, so the whole thing works on a local network. Members behind home routers don't need port forwarding either. The practical setup for most pods is three models covering different jobs: Qwen 3.5 32B for code and reasoning, GLM-5 Turbo for browsing and research, Gemma 4 for fast lightweight tasks. All running on hardware you already own. Pods ship today in Hyperspace v5.19. Model sharding, API keys, treasury, and Raft coordinator are all live. What Makes This Different - No middleman. Your prompts travel from your IDE to your pod members' hardware and back. There is no server in between reading your data. - No vendor lock-in. Pod membership, API keys, and treasury are replicated across your own machines using Raft consensus. If the internet goes down, your local network keeps working. There is no database in someone else's cloud that your pod depends on. - Automatic sharding. You don't configure layer ranges or calculate VRAM budgets. Tell the pod which model you want. It figures out how to split it across whatever hardware is online. - Real NAT traversal. Your friend behind a home router with a dynamic IP? Works. No VPN, no Tailscale, no port forwarding. The nodes handle it. - Free when local. This is the part that matters most. Cloud AI bills scale with usage. Pod inference on local hardware scales with nothing. The marginal cost of your 10,000th prompt is the electricity your laptop was already using. Coming soon: - Pod federation: pods form alliances with other pods. - Marketplace: pods with spare capacity can sell inference to other pods.

Varun

308,089 views • 2 months ago