The author ran Qwen2.5 7B/32B/72B on a single AMD MI300X with vLLM ROCm, priced at $2.99/GPU-hr. The BF16 baseline was 7B at $0.227/M, 32B at $0.77/M, and 72B at $1.67/M output tokens.
Why it matters: The author benchmarked FP8 quantization on the MI300X and found that per-token billing can hide the model's output degrading into gibberish, then gave a reusable way to verify it.
The author open-sourced claudemanager, a local daemon that Claude Code points to via ANTHROPIC_BASE_URL. It only changes the request's Authorization header to route sessions to the Max account with the most remaining capacity in its 5-hour, weekly, and per-model windows, switching at custom thresholds before those windows fill up.
Why it matters: The author also open-sourced a local proxy that automatically distributes Claude Code traffic across multiple Max accounts based on remaining quota, and logs requests along the way.
Flash-Agents is a Claude Code plugin that delegates bounded coding work—implementing slices, porting tests, reviewing diffs, mapping out a codebase—to a DeepSeek V4.1 Flash worker, while Claude keeps architecture, acceptance criteria, and final review.
Why it matters: The author outsources Claude Code's coding tasks to a DeepSeek Flash worker and shares the sandbox, patches, and measured data, so you can judge the cost and safety boundaries for yourself.
The author found that two Codex browser automation tasks consumed 170,123 and 110,180 tokens respectively, so they set out to control usage through model selection, configuration files, and task splitting.
Why it matters: Drawing on real measurements where two browser tasks burned through hundreds of thousands of tokens, the author shares a quota-saving approach: switch models and configurations based on task difficulty.
The author has GPT (gpt-6.1-sol, reasoning tier high) handle planning, key decisions, and acceptance in Codex, and calls DeepSeek-V4.1-Flash through the official DeepSeek Harness to write code, run experiments, and fix bugs—together producing a local PDF toolkit with five working features.
Why it matters: The author splits the work between GPT for planning and DeepSeek for execution to get a PDF toolkit running, and shares three prompts plus cache usage data that can carry over to cutting costs on long tasks.
Artem Gambitsky, co-founder of the Russian e-commerce platform Flawwow, walks through the company's internal product sandbox: it lets colleagues with no engineering background push apps written by AI agents straight to production. In four months, 150 people submitted 262 projects and ran about 5000 deployments—none of that code was ever read by a developer.
Why it matters: The author lays out the four layers of protection that let non-engineers write code with AI agents and ship it safely, plus the resource pitfalls hit along the way. All of it can be adapted to your own in-house sandbox.
OpenAI has released GPT-6.1 Sol for coding, document processing, and task automation. The company says it comes close to GPT-6 Astra on some tests. On DeepSWE 1.1, a benchmark of real-world codebase tasks, the model matches Astra while costing about one-fifth as much to run. On OSWorld 2.0, which tests app control, it beats GPT-6 Sol by 7 percentage points at the highest reasoning tier.
Why it matters: GPT-6.1 Sol matches Astra on DeepSWE 1.1 at roughly one-fifth the cost, which gives you a sense of how the price-performance tradeoff for coding tasks has shifted.
On September 22, Anthropic released its flagship model Claude Opus 5.5, aimed at developers and teams who want agents to handle multi-step tasks like coding and data analysis. The company says it delivers better performance and lower cost than Opus 5.
Why it matters: Anthropic's published pricing and the default workload cost reduction help developers estimate the migration cost for long-running agent tasks.
Why it matters: With about twenty lines of shell, the author decouples Claude Code's harness from the model and shares the routing and pitfalls for four model slots.
GitHub has launched Project HydraFusion as a research preview in the Copilot CLI. It uses runtime orchestration to pick an execution plan across models from multiple providers. Users select it just like any other model, and billing follows each model's standard rates.
Why it matters: GitHub lays out three orchestration modes for HydraFusion and compares cost versus quality across three benchmarks, so you can judge the trade-offs of multi-model orchestration on real coding tasks.
Drawing on a hands-on session where he dispatched 13 subagents to build a storyboard, the author walks through the subagents feature that both Claude Code and Codex have: subagents work in their own separate windows and hand only their conclusions back to the main conversation.
Why it matters: Using a hands-on session where he dispatched 13 subagents to build a storyboard, the author shows how subagents keep their work outside the main conversation and send back only the conclusions.
Anthropic has published a guide dissecting e-commerce AI agents. Drawing on deployment experience with retailers, e-commerce platforms, and teams in travel, entertainment, and telecom, it proposes a single-agent architecture that puts Claude in a standard agent loop, uses skills to cover long-tail needs, and calls tools to work with existing systems. The guide says that in comparative testing, this architecture beats both sub-agent designs and the approach of cramming everything into the prompt.
Why it matters: Drawing on enterprise e-commerce agent deployment experience, Anthropic lays out a complete engineering approach covering a single-agent-plus-skills architecture, latency and cost optimization, and memory and security evaluation.
Cursor supports self-hosted machines: code repositories, build artifacts, and secrets all stay on internal machines within your own infrastructure, and the agent handles tool calls locally. My Machines connects a single laptop or VM to a personal workflow, while Team Pools are named worker queues for teams or enterprises—scaling capacity up with requests and down when workers disconnect. Pools aren't tied to code repositories, and idle machines can sleep and then resume within a reconnection window.
Why it matters: The official docs lay out pooled scheduling and sandbox integration for self-hosted machines, so readers can judge whether tool execution can stay within their own network.
Paper Compute · Engineering BlogSelectedAI score7676