正在加载视频...

视频加载失败

I’m joining OpenAI Codex to work on the future of agentic development! At Cursor, I got to see the shift from autocomplete to agents. The next step isn’t a better IDE. It’s an Agent Development Environment (ADE): systems and tools for orchestrating agents, reasoning over their outputs, and making...

759,989 次观看 • 6 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 次观看 • 4 个月前

I went a little overboard with Codex last week and burned through my entire weekly allowance in two days. Luckily, my quota reset today. Otherwise, I’m not sure what I would’ve done. It got me thinking: instead of asking one large model to handle everything from start to finish, why not let a stronger model plan the project and review the work, while a model built for execution handles the day-to-day implementation? So I tried it. The result was better than I expected. I used GPT-5.6 Sol in Codex as the decision-maker, then ran Ling-3.0-flash from Ant Ling inside OpenCode as the execution engine. Together, they built a small 3D farming game. Before writing any code, I had Codex create four documents: SPEC.md defined the product scope and the lines we couldn’t cross. ARCHITECTURE.md laid out the isometric coordinate system, state machine, and module boundaries. TASKS.md broke the project into small jobs Ling could tackle one at a time. ACCEPTANCE.md explained how each step would be tested and what “done” actually meant. Then I gave Ling a very straightforward role: You are the execution model for this project. Read all four documents before you begin. Work only on the task assigned for this round. When you’re done, run typecheck, test, and build. If anything fails, read the error, fix it, and run the checks again. Do not move on to the next task early. Ling handled dependency installation, project structure, strict TypeScript configuration, test setup, and a production build in 6 minutes and 3 seconds. It ran into issues with the Vite test config, a TS6310 error, and a missing jsdom dependency along the way. Instead of stopping at the first error, it kept reading the logs and fixing the problems until all three checks passed. The speed was honestly hard to believe. If you exclude the time spent waiting on tools, it was producing more than 100 tokens per second. That made the whole development loop feel noticeably faster. After this experiment, I’m planning to keep using the same workflow. If the task is small, there’s no reason to call an expensive planning model for every single step. If the task is large, handing the entire project to a Flash model in one prompt isn’t a great idea either. The setup that makes more sense to me is: Use a more capable model such as Codex to explore the project, make architectural decisions, and break the work down. Put the constraints into specs, schemas, types, and tests instead of leaving them buried in chat history. Give Ling-3.0-flash a steady stream of clear, verifiable implementation tasks. Report bugs with structured context and actual error logs, rather than saying, “It still doesn’t work.” Bring Codex back in for architecture reviews, visual checks, and changes that affect multiple parts of the project. The point of this setup isn’t to give AI a big “build the whole project” button. It’s to turn software development into a pipeline with a much more sensible cost structure: Codex figures out the plan, sets the boundaries, and catches problems. Ling-3.0-flash moves quickly, calls tools reliably, and works through well-defined tasks at scale. For agent workflows that involve lots of repetitive edits, production tasks, and tool calls, this may be a more practical answer than simply using the biggest model for everything.

雪踏乌云

23,107 次观看 • 1 个月前

today was the first time i was genuinely impressed with what AI can do i recently decided to buy a whole FPV drone setup knowing basically nothing about the hardware side of it there's a pretty steep learning curve even just to set everything up properly: radios, RF protocols, flight controllers, ESCs, firmware, batteries, goggles, betaflight configs etc as someone that spends essentially 12h a day prompting agents to build software, it's actually pretty rare that i interact with AI on something where i have zero idea what's going on under the hood, and i never really used it for debugging a bunch of physical devices that all have to talk to each other i had codex + voice mode open for basically the entire setup. told it everything i bought, sent it some pics and then just started talking to it >what order do i set all this up in >how do i change this setting on the radio >which of these cables do i use >the drone is flashing pink wat mean >can you make this thing less insane to fly in my apartment and it was surprisingly seamless it would go find the manual for whatever specific thing i was holding, tell me exactly which buttons to press, what port to plug something into, what i should see if it worked etc then when i got to configuring the actual drone i had codex running on the computer it was plugged into, so it could inspect the config, back everything up, change settings, send usb reboot signals and check what happened the insane thing about voice mode is that youre literally hands on with the hardware and just telling codex what it should do, i literally never touched a thing on the computer besides starting voice mode if something doesn't work you tell it what happened and keep going a few hours of this and i had the radio, goggles, charger, batteries, drone firmware and betaflight all set up and had actually flown the thing the part that stuck with me is that i also understood what most of it was doing by the end, every time there was a term or tech i didnt understand id just ask to explain there is something absolutely magical about having proper real time personalized assistance, being able to dump a pile of unfamiliar hardware on your desk and have something figure out exactly what you own and walk through it with you in real time you become the missing physical link pressing the buttons i think spending all day using coding agents has actually made me pretty numb to AI progress. every new model is a bit better at some benchmark or can oneshot some task that the previous one couldn't and you just kinda adjust to it this felt different mostly because i had no existing knowledge to fall back on for the first time the jarvis comparison didn't feel cringe ai for coding and general computer tasks is cool and all but this feels a lot closer to the endgame anyone should be able to just ask any question about whats going on in their life and have realtime support i wonder if more hardware products will actually start exposing some sort of MCP or interface for agents to plug into thinking for example of how elevators in china are increasingly built with interfaces that let delivery robots call them directly instead of having to physically press a button we might actually start seeing hardware design shift from being purely human-interface-first to also being agent-interface-first buttons, screens and menus exist because humans need some way to tell machines what to do. agents don't necessarily need any of that if the hardware exposes an interface directly very curious which side closes the physical world gap first: humanoid robots that can operate hardware designed for humans, or hardware adapting so agents can operate it directly

ultra

18,096 次观看 • 18 天前