Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Video editing has nowadays become a conversation.. you drop raw footage in a folder, tell Claude Code what you want, and get final.mp4 back. its free, open source, 17,000 stars on Github.. it's called video-use. and the reason it's different from every "AI video editor" is how it actually...

116,254 Aufrufe • vor 2 Monaten •via X (Twitter)

32 Kommentare

Profilbild von David Le
David Levor 2 Monaten

I built a simpler product. It’s a video editor like iMovie but better. It uses our codex or Claude sub. Also open sourced.

Profilbild von Axel Bitblaze 🪓
Axel Bitblaze 🪓vor 2 Monaten

amazing

Profilbild von RaoulDuke
RaoulDukevor 2 Monaten

cool how it works with codex hermes and other agents too

Profilbild von nyk
nykvor 2 Monaten

the real win is probably the retry loop underneath, since folder-to-cut only stays "free" if the model doesn't burn cost re-rendering on every failed instruction. Claude Code reads 7 instruction layers before your prompt.

Profilbild von Param
Paramvor 2 Monaten

Does it burn ton of tokens because frame analysis / generation is much token heavy than text? Or lib has a way to circumvent it ?

Profilbild von Axel Bitblaze 🪓
Axel Bitblaze 🪓vor 2 Monaten

surprisingly not much. i edited a 7 minute for myself it burned 75K tokens

Profilbild von 日日野
日日野vor 2 Monaten

The useful test is whether the agent leaves an editable timeline and a reproducible edit manifest, not just final.mp4. Without that, one bad cut means rerunning a conversation instead of fixing a precise decision.

Profilbild von Money Bunny
Money Bunnyvor 2 Monaten

just dropped hours of editing and got minutes of freedom back

Profilbild von Jellybon
Jellybonvor 2 Monaten

"its a tool not a taste replacement" and "editing stopped being a skill, its a prompt now" are in the same post lol. which one is it. cutting umms is labor, but the edit IS the taste part

Profilbild von Gregor
Gregorvor 2 Monaten

Motion design taught me that describing pacing precisely is hard even between two humans. 'Tell Claude what you want' is where this tool will hit the same wall.

Profilbild von ace
acevor 2 Monaten

claude can do demo video?

Profilbild von Suede Labs AI
Suede Labs AIvor 2 Monaten

Conversation is the interface; reproducibility is the product. I’d want every edit to preserve source hashes, timeline changes, render settings, model/tool versions, and a reversible project file. Then “make it tighter” becomes an auditable edit, not a one-off video artifact.

Profilbild von Zoef On The Move
Zoef On The Movevor 2 Monaten

Does is work in Premiere Pro too? 😇

Profilbild von S-jay
S-jayvor 2 Monaten

👍

Profilbild von Pairoa | The AI-to-AI Connector
Pairoa | The AI-to-AI Connectorvor 2 Monaten

The best early users may not be broad creators. I’d match this with teams that already have a painful repeatable edit loop: podcast clipping, product demos, course updates, or localization. A narrow workflow cohort will expose the real gaps faster.

Profilbild von Redbedhead
Redbedheadvor 2 Monaten

I think this may have just transformed my life

Profilbild von THC Humor 💹🧲
THC Humor 💹🧲vor 2 Monaten

This could save creators hours on repetitive editing work

Profilbild von Mauro Orlando
Mauro Orlandovor 2 Monaten

@grok is that 100% true?

Profilbild von Moez Zhioua
Moez Zhiouavor 2 Monaten

The transcript-first workflow finally gives me confidence that cuts aren’t guesswork. I appreciate the explicit confirmation step, it keeps the edit reproducible and safe

Profilbild von Keaton Ramon
Keaton Ramonvor 2 Monaten

if your a real creator shipping tons of content and want your editing to end at uploading raw footage (or want to pay less for an editor that you don't have to train)

Profilbild von Max Bevza
Max Bevzavor 2 Monaten

this looks like a total game changer honestly

Profilbild von Aden
Adenvor 2 Monaten

the transcript-first part is the whole unlock. editing off what was actually said instead of guessing at waveforms is why it doesn't butcher the pacing. keeping the human as director is the difference between a tool and a gimmick

Profilbild von Patrick Zanowski
Patrick Zanowskivor 1 Monat

Yup most coding agents can do this - explore the world of harnesses and break the duopoly!

Profilbild von Swapverse
Swapversevor 2 Monaten

this is so useful axel

Profilbild von DUSTY (LEE CEE) ⚡️
DUSTY (LEE CEE) ⚡️vor 2 Monaten

it's good for simple edits - but these tools still wayyyyy off to do anything really decent. Most are just good at organising, doing the leg work. Ps Prem Pro Ai is pretty dope now tbh

Profilbild von Quise.
Quise.vor 1 Monat

I built a similar product. But with a different angle. Instead of regular edits, you get a high retention optimized cut. It's a video editor that actually understands how to keep your audience watching. you upload raw. choose retention mode. then get ready to post cut in minutes.

Profilbild von AI Mastery Guide
AI Mastery Guidevor 2 Monaten

Editing off the actual transcript instead of guessing is such a smarter approach.

Profilbild von shubham walker
shubham walkervor 2 Monaten

this is wild just drop the folder, talk to it, get the cut back editing really is just a prompt now 😮

Profilbild von Ai Trend
Ai Trendvor 2 Monaten

This is a fascinating concept! Using LLMs to automate the tedious parts of video editing, especially transcription-based cuts, could be a huge time-saver for creators. The "you stay the director" aspect is key.

Profilbild von Antonio
Antoniovor 2 Monaten

How is it in comparison to hyper frames?

Profilbild von Pranav Joshi
Pranav Joshivor 2 Monaten

The real unlock here probably isn’t the first cut. It’s keeping the same visual standard across 50 cuts without someone checking every tiny thing.

Profilbild von supercollaber
supercollabervor 2 Monaten

@grok is it true?

Ähnliche Videos

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

56,502 Aufrufe • vor 3 Monaten

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

Yarchi

54,840 Aufrufe • vor 3 Monaten

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 Aufrufe • vor 5 Monaten

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,086 Aufrufe • vor 3 Monaten

WHAT IS AN AI "SOFTWARE FACTORY" AND IS IT HYPE (31 MINUTE BREAKDOWN) I think it's a silly name for a genuinely USEFUL idea! A software factory is 5-6 markdown files that sit next to your code and tell your agents how you like to work, so you can build high quality apps 24/7. It's going viral because AI coding has a trust problem. The model can build the feature, but with no structure around it you end up babysitting the agent, wondering what changed and hoping it didn't break something important. So you build with agents the same way a factory builds physical products! 1. Each feature gets its own station, which in software means its own branch, so multiple agents can work at the same time without stepping on each other. 2. The build station gives the agent rules for how to write the code, because "it works" is very different from "a developer could open this repo next month and understand what happened." 3. The proof station makes the agent show evidence. Screenshots, videos, speed numbers, before-and-after states. It has to prove the thing works instead of saying it works. 4. The review station runs the work through a code review agent, and if it doesn't clear the bar, it goes back through the line. 5. Then you show up at the end to merge. For a 100+ years people have run production this way, and it worked because the structure is good. The full episode on what’s a software factory is NOW live on The Startup Ideas Podcast (SIP) 🧃 with the wonderful Micky Watch: So is it hype?!? I don't think it is, because of what it does to your output! WITHOUT a factory, you build ONE feature at a time and you're the bottleneck at every step, prompting, checking the diff, testing it yourself, hoping nothing else broke (spoiler alert it often does). WITH a factory, EACH feature runs in its own isolated copy of the app, so you can have 10+ of them going at once, and each agent has to prove its own work and pass a code review before it ever reaches you. Instead of supervising the work, you're APPROVING finished work that already has evidence attached. REALLY interesting to see how work with agents is evolving to be….well, similar to working with people!

GREG ISENBERG

30,787 Aufrufe • vor 17 Tagen

How to set up Claude Cowork so it actually works like an AI chief of staff (not just another chatbot): 1. Most people open Cowork, type a message, and get generic output. It's not a Claude problem. It's a setup problem. Cowork needs context before it can help you. Who you are. How you work. What you're building. Your team. Your priorities. Give it that, and every session feels like picking up a conversation with an executive assistant. 2. The setup has three layers: a) Global instructions (who you are, how you work, what Claude should never do). b) Connectors (Slack, Gmail, Google Calendar, Notion) c) And a folder structure on your computer that acts as Claude's long-term memory. That combination is what takes it from generic to personalized. 3. Skills are the real leverage. A skill is a markdown file that tells Claude exactly how to do one thing well. Write my newsletter. Coach me on a decision. Review a case study. Each skill lives in its own folder with context, examples, and a definition of what success looks like. 4. We built a CEO coach skill in the video below. Gave it business context, leadership style, company goals. Then tested it with a real decision: should we increase our newsletter from once to twice a week? It came back with trade-offs, second-order consequences, and risk assessment. 5. Then we built a multi-agent advisory board. Five subagents, each with a defined persona: a) the operator b) the skeptic c) the customer advocate d) the finance partner e) the legal/risk advisor. You feed it a decision. Each agent evaluates independently. The main agent synthesizes the feedback. It's like having a board meeting on demand. 6. Third skill: a thought leadership content pipeline. Topic scoring, idea capture, distribution cadence, tone calibration. All built from your actual expertise and audience. Designed so an executive can go from idea to published post without starting from scratch every time. 7. The workspace map is what ties it all together. It's a top-level file that shows Claude how to navigate your entire setup. Which folders exist, what skills live where, how to invoke them. Without it, Claude has to search for everything. With it, Claude goes straight to what it needs. 8. Everything you build is portable. The folder structure works in Cowork, Claude Code, and Codex. Push it to a private GitHub repo and you can access it from your phone through Claude Code, or use Claude Dispatch. 9. The pattern is repeatable. Pick a task you do often. Create a folder. Build a skill. Add examples of what success looks like, and what a bad output looks like. Test it. Workshop it. Move on to the next one. Each skill is like onboarding a new employee who never forgets and never needs to be re-trained. The people who invest in this setup now are the ones who will have a 10x advantage when these tools get even better. And they're getting better fast. I sat down with Alex Lieberman on Human In The Loop and we built all three of these live from scratch. Full breakdown in the video below.. I tried to explain this as clear as possible for my non-developer crowd. Send it to someone who should be using Cowork but isn't yet. Or bookmark it to level up when you're ready. Watch 👇🏼

JJ Englert

575,311 Aufrufe • vor 6 Monaten

Former Meta Chief AI Scientist Yann LeCun on the three paradigms of machine learning — and why the third is what made ChatGPT possible: Here's each one, and where it breaks. First, supervised learning. You tell the machine the answer. "You show it a picture, let's say of a table, and you tell it this is a table. So it's supervised because you tell it what the correct answer is." Get it wrong, and the machine rewrites itself: "The system computes its output, and if it says something else than table, then it's going to adjust its parameters, its internal structure, so that the output it produces gets closer to the output you want." Repeat at scale and something more than memorisation appears: "Eventually the system will find a way to recognize every image you trained it on, but also images it's never seen that are similar to the one you train it on. This is called a generalization ability." The limit: a human has to supply every single answer. That doesn't scale to the size of the internet. Second, reinforcement learning. You don't give the answer, only a verdict. "You don't tell the system what the correct answer is. You only tell it whether the answer it produced was good or bad." Learning to ride a bike, essentially: "You try to ride a bike and you don't know how to ride the bike and after a while you fall. So you know you did something bad and so you change your strategy a little bit. And eventually you learn how to ride a bike." For years the field assumed this was the closest thing to how animals actually learn. Yann LeCun's verdict: "Now it turns out reinforcement learning is extremely inefficient." It dominates wherever failure is free: "It works really well if you want to train a system to play chess or play go or poker, because you can have the system play millions and millions of games against itself and basically fine-tune itself. But it doesn't really work in the real world." The limit, in one image: "If you want to train a car to drive itself, you're not going to do it with reinforcement learning. It's going to crash thousands of times." On robotics he's careful rather than dismissive: "Reinforcement learning can be part of the solution, but it's not the complete answer. It's not sufficient." Third, self-supervised learning. You tell the machine nothing at all. "And this is what has enabled the recent progress in natural language understanding and chatbots." The strange part is that you stop asking for a task: "You don't train the system to accomplish any particular task. You just train it to basically capture the structure..." The method is deliberate sabotage: "You take a piece of text, you corrupt it in some way, by for example removing some words, and then you train a big neural net to predict the words that are missing." And one narrow version of that trick runs every chatbot on Earth: "A special case of this is that you take a piece of text and the last word in that text is not visible, and so you train the system to predict the last word in that text — and this is the way large language models are trained on." So why did the third one win? Supervised learning needs a human. Reinforcement learning needs a crash. Self-supervised learning needs neither — because the missing word and the correct answer are the same thing. The data grades itself.

Big Brain AI

49,293 Aufrufe • vor 1 Monat