Загрузка видео...

Не удалось загрузить видео

На главную

Codex is a monster with 2D games. But what is it worth with 3D and Three.js? 👀 Codex + GPT Image 2.0 + a crazy prompt = • playable 3D forest scene • humanoid character fully made of leaves 🍃 • dense foliage covering the whole body • third-person...

60,609 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Introducing GGEZ: The Nextjs for ThreeJS Games It's an open source framework which adds all the missing pieces to vibe code better ThreeJS games It has full codex integration, so a $20 ChatGPT sub is enough to build games! Literally "bun run start" and you have the full development environment on localhost 0. GGEZ Runtime - Abstraction layer over physics libraries - Character Controllers - It's just ThreeJS, no magic - Load ggez scenes and animations automatically 1. Trident - a World Editor - Codex World agent - A full editor to build scenes - Including Mesh editing, vertex, edge, face - Terrain sculpting - Physics and Player Controller settings - It's just exporting json files and glb assets, no magic 2. Animation Studio - The best you can find on the web - Codex Animation agent - Build state machines and animation graphs - Multi dimensional blend trees - Clip Editor: Create new animations with codex or edit keyframes - Equipment Editor: Never miss the placement of your rifle anymore - ROOT MOTION SUPPORT 3. GGEZ CLI Yea relax, it works fully headless and you can just create new games with bunx create-ggez new-game But at this point just use vanilla threejs?? Anyways if you are like me and you can't guess with code where objects should be placed and you are fifty prompts deep into figuring out where that box should be placed, this is for you If you are an anti AI game developer who insists that this is slop, then just leave a raging comment below please it's good for the algo 🙏 The whole thing is absolutely experimental and things will break as i move very fast, but I will be building my game with it so i will make sure it becomes stable asap! Link to repo below

robot

44,009 просмотров • 3 месяцев назад

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

42,501 просмотров • 22 дней назад

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 просмотров • 1 год назад