You really don't need "software factory" or "loop engineering" to work effectively, or in this case burn $10K per month on a subscription of $200/month. A few very simple tips: * make every ticket ready to start -- pay attention to the grooming and design phase of any task -- ruthlessly delete tickets; * set up a separate repo for the OS that's different than the code repo -- this repo stores working agreements, workflows, learnings, docs. Keep the code repo(s) clean and dry -- pure code and nothing else. * always start working from the OS repo: OS + linear tickets == durable work context. Code is just a short-lived artifact * if you actually need to use goals, write them down in the OS first and then issue them to agents. * don't ever read code, but design a few "gates" your agent have to go through. For me: pixel gate for me to review UX, code review gate(automatic), release gate (automatic). * Design your "squad" -- a group of agents together doing one task. One squad for one complete epic. Tickets should be filed at squad level, such as "finish onboarding v2", not at task level, like "add a button to onboarding". -- 过去的 30 天其实没有用任何所谓的“软件工厂”/loop/graph，就是遵照一些基本的软件工程的原则，默默地就烧掉了 13B 的 tokens，折合 API 价格 $10110. 就是几个很普通的原则如上

Agent frameworks for developers are still at an early stage, with the likes of @vercel's eve and @Cloudflare's Flue — both launched this year — setting the early template. We talk to Flue creator @FredKSchott, who you may know better as the creator of web framework Astro. Fred tells us why agents need a harness and how React influenced Flue 2.

Agent traffic is starting to outpace human traffic on the internet, and that breaks the old ad model for publishers. @cuysheffield on the latest episode of Tokenized with cohost @sytaylor and guests @natalyathakur and @TuongvyLe12 said: Cloudflare's answer is a payment gate for bots. Block them, or let them crawl for a fee. “Yeah sure you can crawl my site but I'm gonna charge you one cent or 2 cents you know for doing that.” The harder problem sits on the buy side. Give an agent its own wallet, spun up from a parent account, so it can pay its way across the web when it hits a paywall. 🎙️ Listen to the latest on tokenizedpod(dot)com

Agent identity ≠ wallet address bolted onto a bot. On @SvpChain, agents are on-chain principals: 📍 Discoverable ⭐ Reviewable 🛡️ Reputation-bearing 🔐 Permissioned First-class citizens get first-class infrastructure. #SvpChain# #AIAgents# #OnChain# #Web3#

Agent payments on the XRP Ledger now support @Mastercard’s Verifiable Intent standard. Through our x402 Facilitator, developers can prove who authorized a payment, under what limits, for which purchase, and Trustline screens it before settlement. More:

Agent coordination is where it's all headed. Agent-to-agent unlocks new harnesses, workflows, and experiences that are just hard to imagine today. I still verify results, but even these I have converted to judge agents that enable me to do more at unprecedented scale.

Agent and Exa Connect are now live in our MCP! Find any data both on the web and from providers like Similarweb and Zoominfo directly within Claude and Codex