Original Summary

I’ve been working on Semwright and wanted to share what I’ve got so far. The problem I’m trying to solve is pretty specific: once an agent needs to do work across more than one application, the handoff between those applications gets complicated pretty quickly. The video is a real example of that. It starts with an existing aircraft project in Blender. The workflow changes some of the materials and camera work, renders a new shot, creates the titles in Motion Canvas, and then assembles the video and audio through MLT. The output is a finished video, but it also leaves an editable timeline. Underneath, Semwright is a runtime that exposes structured operations for supported applications and keeps things like permissions, artifact handoffs and readback in the same execution path. MCP is one of the ways an agent can connect to it. I’m still figuring out where this abstraction is genuinely useful and where a direct script or application API is the better solution. That’s probably the part I’m most interested in getting opinions on. I’d appreciate every feedback. Thanks!   submitted by   /u/Miserable-Tiger-3443 [link]   [comments]

  • 情报分类：开源项目与落地
  • 分类依据：内容涉及项目实践、创业、副业或变现
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/11 03:16:25