Loading video...

Video Failed to Load

Go Home

Here’s the result of my second run with Codex. The first run turned a reference image into an interactive 3D container-terminal simulation. This time, I asked Codex to audit the system in depth, suggest improvements, and implement them. Harbor now includes: - An experiment lab for saving runs and...

17,986 views • 1 month ago •via X (Twitter)

11 Comments

Veyra | AI & Tech's profile picture
Veyra | AI & Tech1 month ago

Timeline replay and branching for terminal ops is genius

Vera Ai | Tools & Updates's profile picture
Vera Ai | Tools & Updates1 month ago

That second pass turns a prototype into a genuinely useful simulation lab

Sehan @ Zyner's profile picture
Sehan @ Zyner1 month ago

So in real world do we have to have GPS and other trackers connected to these vehicles, machines and etc?

Joachim Ferdinand's profile picture
Joachim Ferdinand1 month ago

This is nice

Botanium's profile picture
Botanium1 month ago

Can you share the prompts and tools and skills you have used?

Junho Yeo's profile picture
Junho Yeo1 month ago

For this demo, I just used the ChatGPT web chat

Coffee Cat's profile picture
Coffee Cat1 month ago

让 agent 审自己的系统,有个隐藏风险:它审的是「它理解的系统」,不是你线上跑的那个。我的做法是先让它输出一份它以为的架构图,人先对一遍——图错了,后面所有改进建议都是空中楼阁。

Vinicius Gehlen's profile picture
Vinicius Gehlen1 month ago

What is the prompt and models you have used? Any external mcps?

Junho Yeo's profile picture
Junho Yeo1 month ago

nothing

DreW's profile picture
DreW1 month ago

Woah

dualtron.uk's profile picture
dualtron.uk1 month ago

what did you use to improve rendering + controls

Related Videos

this is f*cking insane, Claude Code agents turned a reading list into a lab you can run in your browser Boris Cherny (creator of Claude Code) gave 12 agents 64 research papers and one assignment: build a browser lab where readers can rerun the experiments pick a fluid simulation, change the conditions and watch how the result changes switch methods while keeping the same scene. inspect the equations, code and measurements beside the animation give each group a specific job: → readers extract equations, assumptions and experimental settings → builders turn the methods into runnable code → reviewers compare outputs against the papers → interface agents build the controls for exploring each experiment a simulation can look convincing while producing the wrong answer reviewers check whether it preserves mass, stays stable and matches the paper's measurements before accepting the implementation every experiment has to show: > the claim being tested > the conditions used > the difference from the reference result > the details still needed to verify it the lab covered 11 methods across 28 reference scenes. seven matched the selected reference results within the stated tolerances; four stayed marked for further review give Claude Code your paper collection, then ask: "Turn these papers into an interactive browser lab 1. Extract implementable methods, equations and experimental settings. Attach page references and flag missing details 2. Assign independent methods to separate agents. Use shared inputs and measurement tools so the results can be compared 3. Have reviewers check each implementation against the paper. Record discrepancies and keep unverified results clearly marked 4. Build controls for changing parameters, comparing methods and opening the code behind each result" start with one paper and reproduce one reference experiment before adding more agents include the inputs, dependencies and checks so the next reader can rerun it from a clean checkout watch the agents at work below

Mika

847,312 views • 1 month ago

this is getting f*cking dangerous: Claude Code agents can turn a stack of research papers into a lab u can run right in ur browser i made $3,650 overnight with this approach Boris Cherny, the creator of Claude Code, gave a dozen agents 64 research papers and asked them to build a platform where anyone could reproduce the physics experiments themselves u open a fluid simulation, change the conditions and immediately see how the flow changes while the experiment is running, u can switch algorithms, open the formulas and inspect the code calculating what happens on screen so u take a complicated paper sitting in ur “i’ll read this someday” folder and get something u can actually play with each agent got its own job: → analysts extract formulas, assumptions and experimental conditions from the papers → developers turn them into working models → reviewers compare the results against the original research → separate agents build controls for each scene and this is where it gets interesting the fluid can look beautiful while the calculations underneath are completely broken. u might never notice just by watching so reviewers check whether mass is conserved, whether changing parameters breaks the calculations and whether the results match the paper’s data next to each experiment, u can see: what’s being tested which values are being used how far the result differs from the original what still needs checking the write-up describes 11 approaches and 28 test scenes. seven approaches passed within acceptable tolerances, while four needed more work i borrowed this way of organizing the work for my FOMOBILL: breaking down how memecoin buys and sells work so i can check what wallets did after entering, before making my own trade the physicists have the original paper. i have the original transaction i can open and verify if u wanna try this approach, upload ur materials to Claude Code and give it this task: “Turn these materials into an interactive tool: 1. Extract the algorithms, rules and testing parameters. Cite the sources and flag missing details 2. Assign separate parts to independent agents. Use the same input data for comparisons 3. Set up independent checks of the results. Log errors and visibly label anything unverified 4. Build an interface where users can change parameters, compare results and inspect the source code” start with one document and one testable example. scaling the team is easier once the first result can be reproduced save the dependencies and source data so someone else can run the project too my overnight result was paper trading; execution and results can differ with real money lyrics breaks down the full approach and how im applying it in FOMOBILL in the article below ↓

Logics

128,132 views • 1 month ago