Loading video...

Video Failed to Load

Go Home

been building an agent-native, node-based, real-time environment. as a test, I gave gpt-5.6 sol a prompt to plan out its own setup and go into a loop of creative exploration until it felt that it was done. it invented every node, every data type, every connection and all of...

22,863 views • 3 months ago •via X (Twitter)

25 Comments

Finn McKenty's profile picture
Finn McKenty3 months ago

Love to see people building weird shit just because they can! That’s always where the coolest ideas come from

andrew pignanelli's profile picture
andrew pignanelli3 months ago

touchdesigner but you have to be even more autistic

Jeffrey Emanuel's profile picture
Jeffrey Emanuel3 months ago

Very cool

🧪Morgen's profile picture
🧪Morgen3 months ago

so glad to run into your account again Cers! I gotta hop in the discord soon! Miss seeing you guys and your bad ass creations!! Hope you are well!!

Tinseltown Pixels's profile picture
Tinseltown Pixels3 months ago

Amazing Spencer keep building

𝖒𝖆𝖈𝖇𝖊𝖙𝖍's profile picture
𝖒𝖆𝖈𝖇𝖊𝖙𝖍3 months ago

Yesssssssssss

srolkk's profile picture
srolkk3 months ago

RIP

Stas's profile picture
Stas3 months ago

Remember hearing you at the comfy meet up in nyc a couple years ago and was impressed back then but this is 🤯

Evan's profile picture
Evan3 months ago

Wizardry 🤯

Stern - uɹǝʇS's profile picture
Stern - uɹǝʇS3 months ago

Killing it Spencer

Rohan Arun's profile picture
Rohan Arun3 months ago

Hey Super, build a single-page browser tool called 'Agent Node Studio' where an autonomous planning agent designs a creative node-graph pipeline that visitors steer in real time. The first viewport shows a dark Konva.js canvas with a left-side prompt dock ("What should the agent build?") and a right-side agent reasoning panel ("Thinking… proposing source node"). The visitor types a creative intent like "a generative ambient music sequencer that responds to text mood" and clicks Compose. The agent immediately begins spawning nodes — Input(text), Analyzer(mood_score), Mapper(scale/tempo), Sequencer(drone/arpeggio), Mixer, Output(audio_graph) — with bezier connections animating as they wire. Each node is a draggable rounded rectangle with editable parameters (sliders, type selectors, value fields), color-coded by category (teal input, violet transform, amber combine, rose output, slate control). While the agent plans, the user can pause, reject a proposal, redirect with a steering prompt ("make it more glitchy"), or jump in and edit any node's parameters — the agent then adapts its next proposal to compensate. The graph runs live: audio nodes use Tone.js for real playback, visual nodes draw to the canvas, data nodes show live charts. Pin Konva.js v9 as the canvas engine and Tone.js v15 for any audio nodes. Persist the current graph and agent state to localStorage so a refresh restores the workspace, with a visible Reset button and iteration rollback. Handle empty prompts by auto-suggesting three starter intents the user can click to launch the agent. On mobile, collapse the side panels into a bottom sheet so the graph stays the primary interaction surface with full touch-drag support. When the visitor clicks Done, the canvas reveals an export panel with a clean, human-readable JSON recipe of the entire graph, ready to copy or download. The agent's planning loop is a deterministic local state machine driven by the prompt's detected domain (audio, visual, data, text) — no external API keys, no cloud calls.

Ronny Khalil's profile picture
Ronny Khalil3 months ago

holy

Mr. Decentralized's profile picture
Mr. Decentralized3 months ago

Is there appropriate chaos? Is there a controller? Is there blockchain based snapshots? Can a snapshot be bidded on?

Meta-Gnome's profile picture
Meta-Gnome3 months ago

Insane!

Surf's profile picture
Surf3 months ago

Could you please put this on github? I’m interested in the visual aspects of it. What kind of hardware does it need or is it webgpu? Thanks

Jordan Thompson's profile picture
Jordan Thompson2 months ago

Cool. What the fuck is it? This looks like a whole lot of broken scalar noise layered up and randomly masked by other scalar. Can't any 3D DCC do this today? I think many have MCP hooks too now.

Gaurav Joshi's profile picture
Gaurav Joshi3 months ago

Wow! Looks amazing.

JQ's profile picture
JQ3 months ago

👀

Evan Boehm's profile picture
Evan Boehm3 months ago

soo interesting to watch new aesthetic vibes

Moon's profile picture
Moon3 months ago

holy..

SpazeCraft's profile picture
SpazeCraft3 months ago

Did you just say you built this in chat gpt??

Spencer Sterling's profile picture
Spencer Sterling3 months ago

The entire software was built mostly with claude all in c++. The actual visuals in this example were vibecoded with chatgpt using the built in terminal and mcp!

SpazeCraft's profile picture
SpazeCraft3 months ago

@cerspense I hear that, it’s just gpt & Claude is getting expensive on my “freelance not much work career” diet lol & im having way too much fun making my life’s work come to life in Claude. I’m bout to phase GPT out sadly, and I’m praying to install comfy UI this weekend. Wish me luck lol

Caidan's profile picture
Caidan3 months ago

Dude this is so cool! Similar to some of the stuff I'm working on

hansfrom.space's profile picture
hansfrom.space3 months ago

Building something similar. Very inspiring to see! My system is also nodebased and aims to create audiovisual organisms "truly" random. Let's have a chat if you like!

Related Videos

Only if education could be this interactive ❤️‍🔥 I've had a looong wish to build something genuinely useful through vibe coding, and I finally did it. A 3D human anatomy application built with Three.js using GPT 5.6 Sol. It all started with a single design image that I created using GPT Image 2.0. I then used it to generate every 3D organ image, one by one. Next, I converted each of those images into 3D models using Tripo (and no, they didn't sponsor this 😄). After that, I opened Codex, wrote a master prompt based on the design, and gave it the prompt, the design image, and all the 3D models. Codex built the first version beautifully, but there was one big problem. Every single 3D model was nearly 120-150 MB. That obviously wasn't practical for the web and was giving a performance of 16fps. After a few iterations, Codex optimized each model down to roughly 2–5.5 MB while preserving the visual quality, reducing the total asset size from ~900 MB to just 28.6 MB. And each model loads on demand. Along the way, Codex also generated those anatomical illustrations showing where each organ sits in the human body, and even created the interactive hotspot markers that explain different parts of every organ. It handled all of that. The process wasn't exactly one shot, but it also wasn't difficult. You just have to do it step by step. It genuinely felt like building something that could make learning anatomy much more engaging. The inspiration came from Dilum Sanjaya's 3D animal plant cell project. I remember seeing it and thinking, "I want to build something like this one day." And I did it :D Live: Code:

The Bugged Dev

2,123,870 views • 2 months ago