Loading video...

Video Failed to Load

Go Home

> Launching: @TheRepolyze - a free, open-source AI-powered tool that helps you deeply understand any public GitHub repository in seconds. > Just paste the repo URL and instantly get: • Clear, actionable insights into the codebase • Beautiful architecture & dependency diagrams • Code quality overview, strengths, weaknesses &...

manixh's profile picture

Manish Kumar

5,913 subscribers

32,858 views • 5 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

5 Years In The Making, Crementif's Free Zelda BOTW VR Mod Is Out Now! Its open-source and available for free, as long as you have legal copy of the game: Crementif wrote a little technical overview in the GitHub description for those who are interested in how it works. Join the Discord in #zbw-join to get help or the Github repo to started!
2:44

5 Years In The Making, Crementif's Free Zelda BOTW VR Mod Is Out Now! Its open-source and available for free, as long as you have legal copy of the game: Crementif wrote a little technical overview in the GitHub description for those who are interested in how it works. Join the Discord in #zbw-join to get help or the Github repo to started!

Flat2VR Modding

197,032 views • 7 months ago

Claw Code just embarrassed Anthropic. A packaging mistake exposed 512,000 lines of Claude Code source. Within 48 hours, a developer rebuilt the architecture, the repo exploded past 100,000 stars, and GitHub had a full-blown open source war on its hands. This is bigger than “another coding tool.” It shows how fast closed AI products can get disrupted when the architecture leaks, the community moves faster than legal, and demand is already there. The real story is not the repo. The real story is that AI companies used open ecosystems to grow, then tightened access the second those ecosystems became expensive to support. That shift is happening everywhere now. If you run a business with AI, pay attention. Your workflow is only as safe as the company policy behind it.
13:03

Claw Code just embarrassed Anthropic. A packaging mistake exposed 512,000 lines of Claude Code source. Within 48 hours, a developer rebuilt the architecture, the repo exploded past 100,000 stars, and GitHub had a full-blown open source war on its hands. This is bigger than “another coding tool.” It shows how fast closed AI products can get disrupted when the architecture leaks, the community moves faster than legal, and demand is already there. The real story is not the repo. The real story is that AI companies used open ecosystems to grow, then tightened access the second those ecosystems became expensive to support. That shift is happening everywhere now. If you run a business with AI, pay attention. Your workflow is only as safe as the company policy behind it.

Julian Goldie SEO

14,771 views • 4 months ago

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,
0:35

Now that we know how much GitHub Copilot is gonna cost us, let's see what we are paying for :-) New /chronicle feature landed in Visual Studio Code insiders Use /chronicle:tips to get curated set of tips how to improve your token consumption and more and use /chronicle:standup to get list of recent sessions and summary of them This is first step for local indexing and next iterations will add saving this to cloud so you can personally consume it or sharing it for all repo contributors to improve overall repo work by getting deep insights on all members work on the repo Behind a feature flag: "github. copilot. chat.localIndex.enabled": true,

Oren Melamed

13,275 views • 3 months ago

Turn any GitHub repository into LLM-ready text! Simply replace "hub" with "ingest" in a GitHub URL and receive a prompt-friendly text ingest for LLMs. Gitingest is 100% open-source and provides: - Directory structure - A brief summary of the project - The entire content as LLM-ready text Plus, it comes with a nice python package and you can run the UI locally! Stay tuned, I'm working on something really cool with this!✨ Link to the GitHub repo in the next tweet! _____ Find me → Akshay 🚀 ✔️ For more insights and tutorials on ML and AI Engineering!
0:29

Turn any GitHub repository into LLM-ready text! Simply replace "hub" with "ingest" in a GitHub URL and receive a prompt-friendly text ingest for LLMs. Gitingest is 100% open-source and provides: - Directory structure - A brief summary of the project - The entire content as LLM-ready text Plus, it comes with a nice python package and you can run the UI locally! Stay tuned, I'm working on something really cool with this!✨ Link to the GitHub repo in the next tweet! _____ Find me → Akshay 🚀 ✔️ For more insights and tutorials on ML and AI Engineering!

Akshay 🚀

191,400 views • 1 year ago

Skills shopping cart for Claude Code In this video I show how I add Railway Skills to a “shopping cart”. After selecting the Skills I need, I copy a single command and they’re added directly to my project. I built to make the composition of Claude Code components as flexible as possible. You can install settings, hooks, subagents, and anything new that gets added to Claude Code will appear on the site. It’s fully open source and community-maintained. If you want to contribute, you’re welcome to fix or update components, download and use the existing ones, or simply support the project by leaving a star on GitHub. Repo:
1:18

Skills shopping cart for Claude Code In this video I show how I add Railway Skills to a “shopping cart”. After selecting the Skills I need, I copy a single command and they’re added directly to my project. I built to make the composition of Claude Code components as flexible as possible. You can install settings, hooks, subagents, and anything new that gets added to Claude Code will appear on the site. It’s fully open source and community-maintained. If you want to contribute, you’re welcome to fix or update components, download and use the existing ones, or simply support the project by leaving a star on GitHub. Repo:

Daniel San

20,460 views • 6 months ago

Today I saw the launch of another "open-source" AI wearable that has not published anything just to charge you 5x the cost At Mistral AI x Cerebral Valley hackathon in SHACK15 we built FRIEND - an AI Wearable that: - Works 24+ hours on a single charge - Costs ~$20 - Remembers what you say, gives you feedback - Understands you via voice or chat - Has 2 apps (one for device and one standalone) Give us 24 hours to finish the hackathon and publish the GitHub repo
1:07

Today I saw the launch of another "open-source" AI wearable that has not published anything just to charge you 5x the cost At Mistral AI x Cerebral Valley hackathon in SHACK15 we built FRIEND - an AI Wearable that: - Works 24+ hours on a single charge - Costs ~$20 - Remembers what you say, gives you feedback - Understands you via voice or chat - Has 2 apps (one for device and one standalone) Give us 24 hours to finish the hackathon and publish the GitHub repo

Nik Shevchenko

509,183 views • 2 years ago

I just released a beta version of /dev/push. It's basically a (simpler) alternative to Vercel, Render, and the likes. You can log in with GitHub, pick a repo, configure your build and off you go. Whenever you push code to GitHub it will automatically deploy it for you. There's obviously more to it: environments, custom domains, environment variables, custom commands, teams... And I'm working on adding more: custom Docker containers, remote nodes, SQLite database, support for PHP, RoR... It's completely free and open source (MIT license). The online version is for now restricted as I test things up. Links below👇
2:33

I just released a beta version of /dev/push. It's basically a (simpler) alternative to Vercel, Render, and the likes. You can log in with GitHub, pick a repo, configure your build and off you go. Whenever you push code to GitHub it will automatically deploy it for you. There's obviously more to it: environments, custom domains, environment variables, custom commands, teams... And I'm working on adding more: custom Docker containers, remote nodes, SQLite database, support for PHP, RoR... It's completely free and open source (MIT license). The online version is for now restricted as I test things up. Links below👇

Ronan Berder

21,938 views • 11 months ago

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.
3:25

Reviewing AI-generated code is the new bottleneck. Writing code was slow before. Now, in a few minutes, you can generate virtually unlimited lines of code using AI. But developers are now spending 70% of their time checking that code. That's the new bottleneck. I've been using Cline, and they have a feature that actually helps with this: You can click a button and have Cline generate an inline explanation for every single line of AI-generated code. Take a look at the attached video. What it does: 1. You can read the code and the explanation together 2. You don't lose context while reviewing code 3. You understand the "why" behind each change And here is the best part: It works on any git diff. You can use it to review PRs, understand commits from other people, or catch up on a codebase you haven't touched in a while.

Santiago

64,425 views • 8 months ago

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨
0:59

Think of it as the Shopify of Claude Code, but for agents, commands, and MCPs 🚀 Pick what you need, “add to cart,” and… it’s 100% FREE. Just copy the command, paste it in your terminal, and instantly get the perfect Claude Code stack for your project. Built as an open-source project so the community can spin up, share, and install Claude Code stacks in seconds, no setup headaches, no paywalls. Here’s the video showing how I built this post… and yes, if you share the command, anyone can clone the exact same stack you’re using. Enjoy, share, and help others build faster with Claude Code ✨

Daniel San

124,913 views • 1 year ago

Introducing the Clips chrome extension - the easiest way to send bug reports to agents with video, transcript, and browser debug info captured automatically. 100% free and open source. If you are like me and get tired of manually typing instructions to agents, attaching screenshots, pasting debug logs, and all of that, this might be your new favorite tool. With the Clips chrome extension, you can just click the Clips icon, hit record, and start talking. Visually demonstrate your issue, go through the flow, point out what’s broken. Clips will capture everything on your screen, plus network requests, browser logs, client errors, and all the details around them. And it redacts sensitive information. Then it gives you a link you can send to humans so they can play it and take a look. Or, more importantly, just give it to your agents by just pasting the URL to them. The link has special metadata for agents so just from the URL, the agent can pull all information from the clip automatically. No plugin or MCP server required. That means it can "see and hear" what’s in the video - read the transcript, grab snapshots at any timestamp, and inspect the logs and network requests that were shared with it. So whether you want to quickly demo an issue and send all that context to an agent, or get better bug reports from teammates, recording and sending Clips makes that super easy. Unlike expensive apps like Loom, this is all 100% free and open source. The framework that powers this, plus a bunch of other free applications, is open source too. You can just sign up and use it, or fork it and customize it to your needs. This, in my opinion, is the future of software. Rather than bloated SaaS that charges you a ton of money and still doesn’t even have the things you need, we get free open source canonical apps that you can fork and customize in any way you want. I'll link to all this stuff in the replies. If you try it, let me know your feedback.
1:27

Introducing the Clips chrome extension - the easiest way to send bug reports to agents with video, transcript, and browser debug info captured automatically. 100% free and open source. If you are like me and get tired of manually typing instructions to agents, attaching screenshots, pasting debug logs, and all of that, this might be your new favorite tool. With the Clips chrome extension, you can just click the Clips icon, hit record, and start talking. Visually demonstrate your issue, go through the flow, point out what’s broken. Clips will capture everything on your screen, plus network requests, browser logs, client errors, and all the details around them. And it redacts sensitive information. Then it gives you a link you can send to humans so they can play it and take a look. Or, more importantly, just give it to your agents by just pasting the URL to them. The link has special metadata for agents so just from the URL, the agent can pull all information from the clip automatically. No plugin or MCP server required. That means it can "see and hear" what’s in the video - read the transcript, grab snapshots at any timestamp, and inspect the logs and network requests that were shared with it. So whether you want to quickly demo an issue and send all that context to an agent, or get better bug reports from teammates, recording and sending Clips makes that super easy. Unlike expensive apps like Loom, this is all 100% free and open source. The framework that powers this, plus a bunch of other free applications, is open source too. You can just sign up and use it, or fork it and customize it to your needs. This, in my opinion, is the future of software. Rather than bloated SaaS that charges you a ton of money and still doesn’t even have the things you need, we get free open source canonical apps that you can fork and customize in any way you want. I'll link to all this stuff in the replies. If you try it, let me know your feedback.

Steve (Builder.io)

60,399 views • 1 month ago

Today, I'm excited to launch Entelligence AI DeepReviews, the next generation AI-powered code reviews. Vibe coded PRs are not production ready often creating more subtle bugs throughout the codebase than before. Entelligence fixes this by understanding the entire codebase and flags bugs, regressions, and breakages across files before you ship. But it goes beyond review comments: ✅ Auto-generated docs with architecture diagrams ✅ Team Insights to improve process, not just code ✅ Real time code reviews within your editor If you're building or leading a dev team, this is what smarter, context-aware reviews look like. Try it out in the link below 👇
1:13

Today, I'm excited to launch Entelligence AI DeepReviews, the next generation AI-powered code reviews. Vibe coded PRs are not production ready often creating more subtle bugs throughout the codebase than before. Entelligence fixes this by understanding the entire codebase and flags bugs, regressions, and breakages across files before you ship. But it goes beyond review comments: ✅ Auto-generated docs with architecture diagrams ✅ Team Insights to improve process, not just code ✅ Real time code reviews within your editor If you're building or leading a dev team, this is what smarter, context-aware reviews look like. Try it out in the link below 👇

Aiswarya Sankar

95,962 views • 1 year ago

Someone just open sourced a tool that honestly feels unfair for developers. you join a new company. 200,000+ lines of code. zero docs. zero context. normally you’d spend weeks just figuring out “what the hell is going on here”. now? you run ONE command. and the entire codebase just… lights up. → every file, function, class, dependency automatically mapped → full system-level understanding in minutes → interactive graph instead of boring static docs → ask “where is auth handled?” and it traces the entire flow end-to-end → shows ripple effects before you even make a commit → auto-builds architecture layers: API / Service / Data / UI → works with Claude Code, Codex, Copilot, Gemini CLI, everything → fully open source and free this is not “better documentation”. this is your codebase getting a brain. onboarding isn’t slow anymore. it’s instant.
1:55

Someone just open sourced a tool that honestly feels unfair for developers. you join a new company. 200,000+ lines of code. zero docs. zero context. normally you’d spend weeks just figuring out “what the hell is going on here”. now? you run ONE command. and the entire codebase just… lights up. → every file, function, class, dependency automatically mapped → full system-level understanding in minutes → interactive graph instead of boring static docs → ask “where is auth handled?” and it traces the entire flow end-to-end → shows ripple effects before you even make a commit → auto-builds architecture layers: API / Service / Data / UI → works with Claude Code, Codex, Copilot, Gemini CLI, everything → fully open source and free this is not “better documentation”. this is your codebase getting a brain. onboarding isn’t slow anymore. it’s instant.

divyansh tiwari

39,303 views • 2 months ago

XBOW raised $117M to build AI hacking agents. Now someone just open-sourced it for FREE. Strix deploys autonomous AI agents that act like real hackers - they run your code dynamically, find vulnerabilities, and validate them through actual proof-of-concepts. Why it matters: The biggest problem with traditional security testing is that it doesn't keep up with development speed. Strix solves this by integrating directly into your workflow: ↳ Run it in CI/CD to catch vulnerabilities before production ↳ Get real proof-of-concepts, not false positives from static analysis ↳ Test everything: injection attacks, access control, business logic flaws The best part? You don't need to be a security expert. Strix includes a complete hacker toolkit - HTTP proxy, browser automation, and Python runtime for exploit development. It's like having a security team that works at the speed of your CI/CD pipeline. The best part is that the tool runs locally in Docker containers, so your code never leaves your environment. Getting started is simple: - pipx install strix-agent - Point it at your codebase (app, repo, or directory) Everything is 100% open-source! I've shared link to the GitHub repo in the replies!
0:23

XBOW raised $117M to build AI hacking agents. Now someone just open-sourced it for FREE. Strix deploys autonomous AI agents that act like real hackers - they run your code dynamically, find vulnerabilities, and validate them through actual proof-of-concepts. Why it matters: The biggest problem with traditional security testing is that it doesn't keep up with development speed. Strix solves this by integrating directly into your workflow: ↳ Run it in CI/CD to catch vulnerabilities before production ↳ Get real proof-of-concepts, not false positives from static analysis ↳ Test everything: injection attacks, access control, business logic flaws The best part? You don't need to be a security expert. Strix includes a complete hacker toolkit - HTTP proxy, browser automation, and Python runtime for exploit development. It's like having a security team that works at the speed of your CI/CD pipeline. The best part is that the tool runs locally in Docker containers, so your code never leaves your environment. Getting started is simple: - pipx install strix-agent - Point it at your codebase (app, repo, or directory) Everything is 100% open-source! I've shared link to the GitHub repo in the replies!

Akshay 🚀

96,762 views • 9 months ago

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source
0:40

THIS GUY ADDED A LIVE BROWSER TO CLAUDE CODE SO YOU CAN CLICK ANY ELEMENT AND EDIT IT INSTANTLY biggest issue with vibe coding UI is that you have to describe what you want to change. if you prompt it the wrong selector or wrong component, Claude can't find it. now you just click it. your app runs in an embedded browser with Claude Code. you can click any button, any text, any div. Claude instantly knows exactly what you're pointing at. click. instruct. done. no more "change the button in the top right corner of the second card component." all you have to do now is just click the button. AND its open source

Om Patel

152,845 views • 4 months ago

built a dead simple chrome extension for my wife and myself. sharing here as free open source as usual Simple Words we find ourselves spending too much time wordsmithing our email replies, just to make sure we sound friendly and respectful this chrome extension is really simple and quite literally a gpt wrapper that only does one thing - one click turning what you mean to what's ready to send it runs on your own api key, subscription or local LLM. the extension itself is free and open source. if you tried it out, would be keen to hear how it works for you! extension: repo:
0:31

built a dead simple chrome extension for my wife and myself. sharing here as free open source as usual Simple Words we find ourselves spending too much time wordsmithing our email replies, just to make sure we sound friendly and respectful this chrome extension is really simple and quite literally a gpt wrapper that only does one thing - one click turning what you mean to what's ready to send it runs on your own api key, subscription or local LLM. the extension itself is free and open source. if you tried it out, would be keen to hear how it works for you! extension: repo:

Kun Chen

10,975 views • 2 months ago

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.
0:51

The number one question I get in the Claude Code / Cowork Community: "how do I share my Cowork skills with my team?" Here's the problem. You build a great skill. You zip it up. You drop it in Slack. Your teammate downloads it, uploads it, and maybe it works. Maybe they upload it wrong. Maybe you update the skill next week and nobody gets the new version. You're now maintaining skills through chat messages and hoping for the best. That doesn't scale. I just put out a video breaking down the three methods I've tested for sharing skills and plugins across a team. From dead simple to fully synced. Method 1: Shared drive (Google Drive, SharePoint, etc). You put your skill files in a shared folder. Teammates download and upload them into Cowork. It works, but updates are manual and there's no version control. Method 2: Built-in sharing on Team and Enterprise plans. You can share any skill directly with a colleague or publish it to your org directory. When you update the skill, everyone gets the update automatically. This is the easiest path if you're on a paid plan. The catch: there's no approval workflow for org-wide sharing, so set a clear owner. Method 3: GitHub repo. This is what I use. Your entire Cowork workspace -- skills, plugins, claude.md, folder structure, project files -- lives in a private repo. Teammates clone it. When you push an update, they pull it. Everyone stays in sync. You get version history, access control, and a single source of truth. The GitHub method sounds technical, but it's really just two steps: clone the repo, point Cowork at the folder. I walk through the whole thing in the video, including how to use .gitignore to keep personal files (like your morning briefing) out of the shared repo. This works for Cowork, Claude Code, and Open Codex. The infrastructure is the same. Full video linked below. If you've found a different approach that works for your team, I want to hear about it. Comment or reply and let's figure out the best practices together.

JJ Englert

16,176 views • 3 months ago

Open-sourcing GenOffice, the world's first full-featured open-source AI Office for PC and Mac. GenOffice is free for everyone, ad-free. All the editing tools you'd expect, no strings attached. How it started? One engineer, one week, $10,000 in tokens. That's what it took to build the GenOffice Alpha. Help shape the AI office experience We invite you to build the rest of it with us. Join the GenOffice group chat on GenTeam and bring your requests straight to the agent. Not by writing code, but by telling it what you want. You say what you need, and every piece of your feedback becomes part of the product. What's in GenOffice? Docs, Sheets, Slides, and PDF, with all the editing tools you already know. And with Genspark Super Agent built in, powered by top-tier models, it digs into research, crunches your data, then writes the doc or builds the deck for you, using your Genspark credits. This is an Alpha, and we mean it. Come tell us what's broken and what's missing. Everyone who jumps in with real feedback gets 1,000+ Genspark credits as a thank you. GitHub 👉 Download it now 👉
1:26

Open-sourcing GenOffice, the world's first full-featured open-source AI Office for PC and Mac. GenOffice is free for everyone, ad-free. All the editing tools you'd expect, no strings attached. How it started? One engineer, one week, $10,000 in tokens. That's what it took to build the GenOffice Alpha. Help shape the AI office experience We invite you to build the rest of it with us. Join the GenOffice group chat on GenTeam and bring your requests straight to the agent. Not by writing code, but by telling it what you want. You say what you need, and every piece of your feedback becomes part of the product. What's in GenOffice? Docs, Sheets, Slides, and PDF, with all the editing tools you already know. And with Genspark Super Agent built in, powered by top-tier models, it digs into research, crunches your data, then writes the doc or builds the deck for you, using your Genspark credits. This is an Alpha, and we mean it. Come tell us what's broken and what's missing. Everyone who jumps in with real feedback gets 1,000+ Genspark credits as a thank you. GitHub 👉 Download it now 👉

Genspark

472,127 views • 2 days ago

This is a pretty wild model! You can use it to turn an image into a 3D object with texture. The quality is out of this world! I'm not even a designer, and I've been using this nonstop for the last 2 hours. The model is Hunyuan 3D 2.1. It's open source. You'll find model weights, training/inference code, data pipelines, and architecture on their repository. You can even fine-tune it if you want! GitHub Repository: By the way, the model runs on consumer-grade GPUs. You don't need a datacenter for this! I've been using the model from the HuggingFace demo page: To use it, go to the link and upload an image. That's it! Check out the video I recorded for a couple of examples.
2:42

This is a pretty wild model! You can use it to turn an image into a 3D object with texture. The quality is out of this world! I'm not even a designer, and I've been using this nonstop for the last 2 hours. The model is Hunyuan 3D 2.1. It's open source. You'll find model weights, training/inference code, data pipelines, and architecture on their repository. You can even fine-tune it if you want! GitHub Repository: By the way, the model runs on consumer-grade GPUs. You don't need a datacenter for this! I've been using the model from the HuggingFace demo page: To use it, go to the link and upload an image. That's it! Check out the video I recorded for a couple of examples.

Santiago

44,783 views • 1 year ago