Cursor gave teammates’ agents a shared view of plans and tasks. Replit let its agent prepare purchases for approval, and Cloudflare introduced spending limits that can pause billable activity. Builders choose what agents can read and spend. A hosting limit also means choosing what work can stop when the bill gets too high.

Coding Agents: Shared project context and a Copilot model deadline

Cursor Projects added team workspaces in beta. A shared board shows agent tasks and their proposed code changes. Teammates’ agents can read the same specs and designs, while each person chats separately with their own coordinator, the agent that delegates work. Put decisions that everyone needs in the shared specs, and keep credentials and sensitive customer data out of them.

GitHub said it would retire six Copilot models on December 14, including Claude Fable 5 and Kimi K3. Individual subscribers on annual plans can keep Claude Haiku 4.5. If your team pinned a model, test its replacement in the same workflow and check that your organization lets people select it.

AI Builders: Replit adds purchases and ad campaigns with approval

Replit Agent can prepare a purchase or a Google Ads campaign. In the US launch, Core and Pro users could have Agent fill a cart for a one-time purchase, then approve the final total at checkout. For ads, the agent drafts the campaign and suggests a budget. A person reviews and approves it before launch.

The purchase approval covers one transaction. An ad campaign can keep spending after launch, so check the campaign budget and monitor actual spend in Google Ads.

Infra & Deployment: Cloudflare caps spending and Netlify keeps a server running

Cloudflare added spending limits in beta for Workers and Durable Objects on pay-as-you-go accounts. Workers runs application code, and Durable Objects keeps shared state. Billable work can pause when the limit is reached. Usage may still accrue while the limit takes effect, and background jobs can stop. Set an alert below the limit so you have time to respond.

Netlify introduced a backend that stays running between requests, so apps can hold open connections for features like live chat. In Early Access, all server instances stop after five minutes without requests. Save chat history or unfinished work in a database so it survives a restart.

GitHub Actions had a 52-minute disruption on November 9 UTC. GitHub says 28% of runs were affected on average. Some automated jobs failed to start or update, and some stuck jobs kept taking up slots after service recovered.


End of article