From the field.
What Jigar learns building and training, shared as posts. Specifics over slogans.
Cursor's agent swarm economics: why frontier planners and cheap workers beat solo GPT bills
Cursor's July 2026 swarm write-up rebuilt SQLite in Rust from the docs and measured planner vs worker spend. Frontier-only GPT-5.5 hit about $10.5k; Opus 4.8 planning with Composer 2.5 workers landed near $1.3k at similar quality. Here is how I translate that into routing rules for production graphs.
MCP 2026-07-28 is live: day-one field notes after the cutover
July 28 shipped. MCP's fifth spec release makes the protocol stateless at the core, hardens OAuth, graduates Tasks and Apps into a versioned extensions framework, and updates Tier 1 SDKs. Here is what I verify in the first 48 hours that the pre-GA checklist could not prove until clients actually moved.
MCP GA is four days out: the final cutover checklist I run before July 28 goes live
The MCP 2026-07-28 final specification publishes July 28. You already did inventory, header security, and handle migration. These four days are cutover discipline: freeze pins, delete sticky sessions only after round-robin passes, confirm cacheScope with two identities, and staff an on-call window for clients still sending Mcp-Session-Id.
Graph engineering with Claude Code: the 14-step roadmap I use when linear agents stall
A straight-line agent is a degenerate graph. Claude Code dynamic workflows move orchestration into JavaScript so subagents fan out, verify, and converge without stuffing every intermediate result into one context window. Here is the 14-step roadmap I map onto production work, with topology diagrams, contracts, and the patterns I already ship.
Gemini 3.6 Flash shipped, 3.5 Pro did not: the routing checklist I run after July 21
On July 21, 2026 Google released Gemini 3.6 Flash ($1.50/$7.50 per million), 3.5 Flash-Lite ($0.30/$2.50, ~350 tok/s), and a limited-access 3.5 Flash Cyber via CodeMender. Gemini 3.5 Pro stays in partner testing. Here is how I re-benchmark cost per completed task against Sonnet 5 and Fable without betting the roadmap on Pro.
Claude Code Week 29: live MCP artifacts change the blast radius of a shared dashboard
Claude Code Week 29 (July 13–17, v2.1.207–v2.1.212) lets published artifacts call MCP connectors on each view through the viewer's own connections, with first-call approval. Public sharing links, editor roles, screen reader mode, and auto-background for long MCP calls shipped in the same window. Treat live artifacts like production integrations, not pretty exports.
MCP just got a rival enterprise protocol: the portability playbook I run before teams pick a side
In mid-July 2026, reporting put Google, Microsoft, Salesforce, Snowflake, and ServiceNow behind a shared enterprise agent backend protocol framed as a counter to Anthropic's MCP. Protocol wars are procurement stories dressed as plumbing. Here is how I keep tool contracts, auth, and gateways portable while MCP 2026-07-28 still ships on July 28.
Claude Code Week 28: the desktop browser and /doctor checklist I run before enabling it org-wide
Claude Code Week 28 (July 6–10, releases v2.1.202 through v2.1.206) shipped a sandboxed in-app browser on Desktop and upgraded /doctor from a read-only report into a repair tool. Auto mode also blocks transcript tampering. Here is the governance checklist I run before teams turn browsing and auto-fix on for every engineer.
MCP stateless GA is 18 days out: the week-three handle migration sprint I run before July 28
The MCP 2026-07-28 spec publishes July 28 with a stateless core: no initialize handshake, no Mcp-Session-Id, routing on Mcp-Method headers, and application state as explicit tool handles. Week 3 is where teams either mint basket_id-style handles or learn from 502s. Here is the sprint checklist I run 18 days before GA.