warp code feels like a combination of a cli... agent and cursor-style ux design it's a cli that looks like an ide because it gives you: - editor code view - project explorer - one-click to view command output - switch between agent/cli - context/credit spend tracking - task lists - shared context with warp drive there is a learning curve because it's a different workflow, but the agent was top of terminal bench until recently and i can see why would love to see them add: - subagents - an agent sdk - sidebar fonts increasing with cmd +/- not being paid to post this, btw (feel like i have to add that these days 😉) i have been using warp for a long while as a terminal and sometimes agent on the $15/mo planshow more

Karpathy's Agentic Engineering finally has proper tooling! (built by... Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.show more

subagents are just recursive agents where you can apply... different prompts + models depending on the task. since they’re just a primitive, Cursor cli can actually spawn subagents by calling cursor-agent in headless mode via shell commands. that’s what makes the cli so nice. you can extend it, experiment, and have a lot of fun exploring orchestration patterns. here’s one way to do it w. dynamic model selection: 1. create a subagents.mdc rule 2. drop in: ``` --- alwaysApply: true --- ALWAYS spawn subagents by running `cursor-agent -p [task] --output-format=text --force --model [model]` in the terminal. Each subagent should return a summary of the changes it made. Subagents should be used for ALL tasks You can adopt a fan-out pattern where you spawn subagents to perform parallel isolated tasks, and then fan-in the results. Use the following models: - `--model gpt-5` for reasoning, researching, and planning - `--model sonnet-4` for implementation ``` 3. start cursor cli and try it out you can also adjust the rule to be more explicit when it should use subagents, when not to, which models when etc.show more

Something that AI unlocks is being able to try... a few different variations of a feature quickly. I often ask my coding agent to come up with a few different variants and add a switcher so I can easily swap between them. It also saves your selection as a query param so I can show a specific variation to a colleague. This + a library like Leva for controls that directly influence an interaction makes prototyping and coming up with different ideas extremely easy.show more

so tired of wasting my time clicking through terrible... dashboards and UIs i strongly believe that everything should work directly from your agent so we built @lifi/cli for devs and agents who need access to onchain infra without navigating a ui everyone's been shipping mcp servers for onchain actions. and frankly, we did too. but i believe that a cli is even better for many uses cases it's less setup, more token efficient, works in any terminal, container, or ci pipeline and not just claude, codex or cursor. now you can swap, bridge, deposit, and literally anything else onchain from your terminal. ‘npx @lifi/cli chains’ to startshow more

New open-source agent harness just landed! I got early... access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.show more

Dynamic workflows are a generalization of harnesses, automations, loops,... routing, and graphs. It's the most powerful feature I have built into my agent orchestrator. Supports all kinds of patterns that leverage different agent backends (claude, codex, pi, hermes,...). It's a meta-harness approach that unlocks new forms of test-time compute. Example of use cases it supports: > LLM councils to get different perspectives from LLMs or plan more intensively > Dynamically routing tasks to different agents based on needs (e.g., cost efficiency and optimal intelligence) > Advisor/Judge + executor workflows and pretty much any complex graph-based pattern required by the task. I find it especially useful for long-running work and code reviewing. > Agent teams that talk to each other if needed for the task. I like to use this for AI editing, artifact creation, and other creative tasks. And I am sure it supports so many things that I haven't discovered yet. I got inspired by the dynamic workflow feature released by the Claude Code team. I had actually built it earlier this year but wanted to generalize it across different agent backends. I think this is going to become more popular in the coming days. I will share more of my findings soon.show more

Midjourney sref + Sora 2 Pro is the sauce.... With one Midjourney style image, you can give a specific style for your entire project. I created two different 12-second clips and edited them together. Some details aren’t fully consistent, like the iPod or AirPods because the clips were made separately from a single image (Character in a specific style). It could be fixed in post-production, but that would take more time, and this was more of an experimental test. It would be great to add the actual product image with the current one to maintain product consistency. I feel like if there were a way to add 2–4 images into this workflow, it could open up a lot more possibilities and consistency. With an API, it could be possible. Or let’s see what Veo 3.1 has to offer.show more

2 Cursor Composer agents working together on the same... project. one builds the project, the other reviews once the first agent is done and writes a report. cursor rules file is in comment to achieve this. first agent is instructed to build the project second agent is instructed to write a monitoring script to determine when the project is done then to review the project for errors and write a report This prompt can be improved. This is meant as a baseline If you are interested in learning how to use Cursor more in depth, I have a 28 chapter 1000x Cursor Course building full apps from scratch with 19 hours of content. link is in my bio if you are interestedshow more

Alright, now that we know *what* an agent is,... how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.show more

I say this, and in no means throwing shade... at Cursor, but using the new design mode really makes me appreciate the speed of interactions in Figma and Framer. I will absolutely be testing it out in my own workflow, and love that an IDE finally is adding a browser view and selection UX for local dev support, especially one as powerful as cursor... But i'll wait until undo works. I mean... how am I supposed to design without cmd+z?show more

Replit, Vercel, and OpenAI have built very cool agent-native... applications, but nobody else has passed the demo stage. Building agents that work is complex. Teams aren't shipping agents because we don't have good tooling yet (and most of us don't know how to do this well.) A couple of days ago, the CopilotKit🪁 team announced a collaboration with . You can now use LangGraph with CoAgents to build agent-native applications, and here is everything you need to know about that: CoAgents is fully open-source, and you can use it to do the following: • Human-in-the-loop to steer and correct the agent • Stream intermediate agent state • Real-time state sharing between the agent and the application • Agentic generative UI to build trust that the agent is on the right path Start this GitHub Repository: Thanks to the team for giving me early access and collaborating with me on this post.show more

Michael Arnaldi suggested cloning the effect repo as a... git subtree, giving it to Claude, then using that as docs It sounds absurd, but it's actually kind amazing lol Setup a custom OpenCode agent that has all the context on where the files are then it kinda just works I feel like this could definitely be refined but idk if I even care enough. Stuff like cursor/opencode/claude code is already so good at searching codebases that I don't really care to do anything moreshow more

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:show more

more frontend vibecoding tips (results below): WHY YOUR VIBECODED... FRONTENDS ALL LOOK THE SAME AND SUCK: when asked to make a frontend, the agent/llm will default to the center/average of its training data (in a very loose sense). through the training process, the model essentially converges on some default UI style. it's very capable of doing things that are different from this style, but you have to ask! for instance, ChatGPT tends to reply in the same tone for all users untill you interact with it and instruct it differently ("be sassy", "eli5"). the second reason is that most of us are not good at coming up with designs and describing them precisely (see my tweet on a crash course in common components, which i'll link below). treat frontend generation just like any other eng task! you need to provide a good detailed spec. TIPS: 1. give ur agent screenshots of designs you like (you may not know the right words to describe them but the agent will! a pic = 1000 words) where to find ui inspo? Behance, Dribbble, Mobbin (Mobbin is paid but worth it!) 2. ask ur agent for proposals, this helps "seed" different directions so the final frontend stands out. don't be afraid to go back and forth. 3. ban certain tendencies: no Inter/Roboto, no shadcn (controversial), no gradients, no emojis 4. encourage the agent to be extreme and make bold decisions, not safe ones. i think that the underlying models tend to get taught during RL/fine-tuning to make conservative choices that produce reasonable but boring frontends 5. give ur agent Figma MCP. the best results will come if you mockup your vision in Figma first. 6. Ideally choose an agent with vision capabilities TLDR: Most people are tremendously underusing agents for frontend design. They are much better than you might expect.show more

I ABANDONED LOVABLE AFTER SEEING WHAT CLAUDE CODE CAN... ACTUALLY DO basic generators are great for quick ideas but trying to build a premium site with Lovable feels like playing in a sandbox I gave Claude Code a few custom design skills instead 4 minutes later it built a premium design they would have quoted me $7,500 for the difference between generic templates and a skilled local agent is literally worth thousands grab the full guide below 👇show more

I tried Hedra Agent by Hedra to see if... one conversation could replace the usual mess of switching models, rewriting prompts, and juggling tools. So I started with a simple idea, Hedra Agent: - Selected the right models on its own - Generated refined visuals - Suggested multiple stylistic directions - Then turned the chosen frames into a cohesive video All within the same conversation while remembering every detail we discussed. I was able to shift the mood, adjust the lighting, refine the composition, explore different angles, and even adapt the format simply by giving natural feedback. I did not have to restart or rebuild anything from scratch. The Agent handled the workflow from idea to finished, platform-ready content. What stood out was not just the output quality, but also the continuity. Instead of operating tools, it felt like collaborating with a system that understands context and builds with you step by step. Check how it works 👇🏻show more

LangGraph. CrewAI. Agno. Which one to pick? The good... news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.show more

I still think Hermes agent is the most slept-on... AI tool of 2026. For literally $6/mo, you can launch multiple subagents that work for you 24/7. Most people don't know you can do this, but it's a complete game-changer. Instead of one Hermes assistant doing everything sequentially, you run specialized agents in parallel, each with its own job, its own context, and its own memory. Practical example: → Research agent: scans your watchlist and competitors overnight, delivers a morning brief → Content agent: drafts and schedules your posts based on what's trending in your niche → Ops agent: manages your inbox, flags anything urgent, drafts replies for your review All three can run simultaneously and improve over time. How to start: 1. Install Hermes Terminal command: curl -fsSL | bash (can also download desktop) 2. Prompting Simply tell Hermes directly: "I want to run separate subagents for [task 1], [task 2], and [task 3]. Set them up to run independently and report back to me." For the cheapest setup, you can use a $4/month VPS with Hostinger, plug in DeepSeek V4 Flash as your default model. There isn't another AI tool with this much value in 2026. Hermes is still so underrated.show more

So lemme show you what i am working on... rn Klick (might change the name later) It’s basically gonna be a cursor click animation library, you will be able to add really cool click animations to your cards, pages, and components with just one CLI command. And this is the homepage i designed for it, tell me how it looks This project is gonna be crazy, i have spent a lot of time making sure everything feels really polished and good, just wait till i complete it, it’s gonna be insaneshow more