Turn one photo into an animatable 3D model, plus a Mac video editor your AI edits alongside you
The most interesting tool this week is an agent skill called img2threejs, and the smart part isn't what you'd guess. It takes a reference photo and rebuilds the object as procedural 3D code you can animate. But the model barely does the heavy lifting. Deterministic Python, standard library only, handles the validation and the code generation. The AI's tokens go only to the visual judgment: look at the image, assess it, check the render. That split is why it stays cheap to run, and it's a pattern more agent skills should copy. That's the thread running through this whole issue. Agents are moving out of the chat window and into real production work. Palmier Pro is a native Mac video editor that hooks into Claude, Codex, and Cursor over MCP, so an assistant can edit the timeline alongside you. RAGFlow grew from a document-parsing engine into a full agent platform sitting on your own files. LangGraph is the framework people reach for when an agent workflow stops being a straight line and starts needing loops, branches, and approval steps. None of these are magic. Palmier's editor is free and open source, but the in-timeline AI generation is the paid, closed part, so know what you're getting. RAGFlow self-hosted is a real ops project, not a docker run. And img2threejs is honest about its own limits: it's strongest on hard-surface objects and tells you when it can't hit the fidelity you want from one photo. That kind of honesty is rare, and it's worth rewarding.
Rebuild the object in a reference image as a code-only, procedural, quality-gated, animation-ready Three.js model. Token-efficient image-to-3D.
The Lens
img2threejs takes a reference image and rebuilds the object in it as procedural Three.js code, using primitives and shaders instead of a downloaded mesh. It is an agent skill, not a library: you install it into Claude Code, Codex, or OpenCode and the agent runs the pipeline. Apache 2.0 since July 2026, when it moved off MIT. The design is the interesting part. Deterministic Python scripts handle validation, quality gates, and code generation using only the standard library, while the model's tokens go to the visual judgment steps: look at the image, assess it, review the render. Version 2.0 turned it into a plugin system with an img2 installer, official plugins for characters and Counter-Strike 2 weapons, and a GLB export path. Web developers who need 3D objects and would rather not model them or license assets are the audience, mostly solo and small teams. Subjects are classified as object, character, or hybrid, and characters route through an anatomy-aware track. The catch: it is strongest on hard-surface objects, and the project says so. Characters come out as stylized reconstructions, not photoreal likeness, even with the new opt-in projection path. It is also token-hungry by the README's own admission, estimating roughly 80k to 180k tokens per object. It will tell you when an image cannot reach the fidelity you asked for.
macOS video editor built for AI
The Lens
Palmier Pro is a native macOS video editor with AI wired directly into the timeline. The editor itself is open source under GPLv3 and free to use with no login. Where it gets interesting: you can generate video and images from models like Kling and Seedance right inside your edit, and it hooks into AI agents (Claude, Codex, Cursor) over MCP so an assistant can edit the project alongside you. There's not much to "host" here, it's a desktop app you install and run. The setup catch is hardware: it's Apple Silicon only and requires macOS 26 (Tahoe), so it won't run on older Macs or anything non-Apple. The core editing, the MCP server, and the agent chat are all in the open source build. The free editor is a capable tool on its own. The generative AI features are the paid part: those run closed source and need a login and a subscription. So the split is clean, free editing forever, pay only when you want in-timeline generation. Solo creators and developers curious about agent-driven editing: the free build is worth a look. If you'd lean on the AI generation daily, price the subscription against how much you'll actually use it. The catch is that the headline feature, the AI generation, is exactly the piece that's closed and paid. The open source part is a solid editor; the "built for AI" magic is a subscription. That's a fair way to monetize, just know going in that "open source AI video editor" is half the story.
RAGFlow is a leading open-source Retrieval-Augmented Generation (RAG) engine that fuses cutting-edge RAG with Agent capabilities to create a superior context layer for LLMs
The Lens
RAGFlow is a retrieval-augmented generation engine built around deep document understanding, and it has grown into an agent platform on top of that. It handles the messy parts of RAG other frameworks hand-wave past: PDFs with tables, slides, spreadsheets and scanned images, with MinerU and Docling parsing. Recent releases added knowledge compilation into wikis, graphs and mind maps, agent memory, and delivery into chat apps like Discord, Telegram and Line. Apache 2.0.
Self-hosting is a real project, not a docker run. You need 4+ CPU cores, 16+ GB RAM, 50+ GB disk, and x86 hardware, since there are no ARM64 images. The compose file brings up RAGFlow plus MySQL, Redis, object storage and a search backend: Elasticsearch by default, with Infinity, OpenSearch and OceanBase among the options. Template-based chunking is still the killer feature: you see and adjust how documents are split before they reach the index.
Solo developers and small teams that want full control can self-host for free. Everyone else can use RAGFlow Cloud, currently $29/mo for 5 seats on Starter or $129/mo for 20 seats on Pro, with Enterprise adding on-premises or bring-your-own-cloud deployment.
The catch is operational weight. Just chatting with a few documents? LlamaIndex or LangChain over a simple vector store ships faster. Note that v0.27 pulled the old GraphRAG and RAPTOR features from the UI, so check tutorials against your version.
Build resilient language agents as graphs
The Lens
LangGraph defines AI agent workflows as graphs, where nodes are processing steps and edges are conditional transitions. Each node is a step (call the LLM, run a tool, check a condition), and edges define what happens next. The graph model matters because real agent workflows aren't linear. An agent might need to: research, then decide if it has enough info, loop back to research if not, then draft a response, then review it, then either revise or submit. LangGraph makes these branching, looping workflows explicit and debuggable. It builds on LangChain but works independently. Supports any LLM provider. State management is built in: each graph execution has persistent state that nodes can read and write. Human-in-the-loop patterns (pause execution, wait for approval, resume) are first-class features. The star velocity tells you where the market is heading. Agent frameworks are the hottest category in open source AI right now. The catch: the abstraction adds complexity. For simple "call an LLM with tools" flows, LangGraph is overkill. The OpenAI or Anthropic SDKs handle that directly. The LangChain ecosystem moves fast and breaks things; APIs change between versions. And debugging graph execution requires understanding the framework's internals, not just your business logic.
Get the next issue in your inbox
Free. No spam. Unsubscribe anytime.