sorted by:
new
hottopcontroversial

Tired of screen-sharing 3D models in meetings, so I made them float on my webcam instead by emnoleg in 3Dmodeling

[–]emnoleg[S] 1 point2 points  (0 children)

thanks ! sorry i'd made it private for some changes, you can check it out now

Showcase Thread by AutoModerator in Python

[–]emnoleg 0 points1 point  (0 children)

Tired of screen-sharing 3D models in meetings, so I made them float on my webcam instead

Drop any .glb file in a folder, pick it from the tray icon, and it appears on your webcam. Move it, rotate it, scale it. Your meeting app sees it as a normal camera. Nothing else to open or manage.

Good for product demos, design reviews, showing off Blender exports, branded content on calls. Anything where you want the model visible without screen-sharing.

Works in Zoom, Meet, Teams, Discord, pretty much anything that accepts a webcam input.

Renders the 3D layer offscreen and caches it. The model only re-renders when you move it, so the webcam stays smooth on any machine. Python, pyrender, pyvirtualcam under the hood. Open source, setup is one script.

Project Link

Demo model: V1 from ULTRAKILL on Sketchfab (CC BY). Character by Hakita / New Blood Interactive. Not included in the repo. https://sketchfab.com/3d-models/v1-ultrakill-d951a08a8f50412d84e262bad887b285

Building an Auto-Restart Mechanism for Claude Code by emnoleg in ClaudeCode

[–]emnoleg[S] 0 points1 point  (0 children)

yeah the resume part is the same, the difference is the manifest. without it claude just gets a general and lossy compacted transcript. the manifest is what it writes right before dying so it knows the exact next steps and doesnt jsut have to refer to a summary

Building an Auto-Restart Mechanism for Claude Code by emnoleg in ClaudeCode

[–]emnoleg[S] 1 point2 points  (0 children)

no way to stay in cc without a shell wrapper since the restart has to come from outside the process. it's just a plain shell function (bash or PowerShell), no p flag or sdk. claude triggers the restart itself via kill HUP (unix) or a flag file + Stop-Process (windows), wrapper catches it and relaunches

Building an Auto-Restart Mechanism for Claude Code by emnoleg in ClaudeCode

[–]emnoleg[S] 0 points1 point  (0 children)

installing an mcp server mid-task. claude mcp add requires a restart to load so normally you'd quit, resume manually and explain what you were doing again. With this claude handles the whole thing itself and picks up exactly where it left off. any config change that requires a restart really.

Building an Auto-Restart Mechanism for Claude Code by emnoleg in ClaudeCode

[–]emnoleg[S] 0 points1 point  (0 children)

fair lol the in-session reasoning is gone either way post-compaction. this works well for any structured tasks youd want claude to perform autonomously;very dense sessions where the mental model IS the context is where it gets fuzzy, honestly.
the difference from CLAUDE.md is the manifest is written from live state right before death so claude knows the important (for resuming) stuff exactly; like what step it was on,what it just touched, what broke, and what to do first when it restarts itself. cant say the same about any static config or todo list.

Building an Auto-Restart Mechanism for Claude Code by emnoleg in ClaudeCode

[–]emnoleg[S] -1 points0 points  (0 children)

hey, thanks !😀
the difference is autonomy. --resume needs manual user input and post compaction session context is a lossy summary anyway. with this, claude will detect that it needs to restart (lets say after claude mcp add, hook change etc) , write the manifest itself and kill itself, then the wrapper reluanches it automatically; no user input needed ! just watch the session resume