{"slug": "github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23", "title": "GitHub Copilot cloud sandboxes start drawing from Actions compute on November 23", "summary": "GitHub announced that cloud sandbox billing for Copilot coding agents begins November 23, 2026, with CPU and memory usage drawing from the same included compute allowance shared with eligible Actions runners. CPU is metered at $0.000024 per vCPU second and memory at $0.000003 per GiB second, while retained snapshots are billed separately at $0.005 per GiB-month until deletion. Local Copilot CLI and app sessions are unaffected, and model usage and AI credits remain separate from the infrastructure charges.", "body_md": "A long-running coding agent uses more than model credits. In a November 19 update, GitHub said **cloud sandbox billing starts November 23, 2026**. CPU and memory draw from the compute allowance shared with eligible Actions jobs; retained snapshots are metered separately. The announcement gives no rollout time or timezone.\n\nThis change covers **Cloud** sessions in GitHub-hosted isolated Linux sandboxes. It does not impose a separate cloud sandbox charge on **local** Copilot CLI or app sessions running on your computer. Sessions using **Actions** follow the usual billing rules for the runner. Model usage and AI credits are separate from the infrastructure charges below.\n\nStandard GitHub-hosted runners for private or internal repositories share the included compute allowance with cloud sandbox CPU and memory. No eligible usage type gets priority, and the allowance resets at the start of each billing cycle. Standard hosted runners for public repositories remain separately free. That does not make every Copilot cloud sandbox attached to a public repository free.\n\n| Meter | What GitHub measures | Published rate (USD) | Draws from included compute | \n|---|---|---|---|\n| CPU | Running vCPU seconds | $0.000024 | Yes | \n| Memory | Allocated GiB seconds while running | $0.000003 | Yes | \n| Snapshot | Stored GiB-month after stop until deletion | $0.005 | No | \n\n**Hypothetical calculation, not a measured bill.** Suppose 2 vCPUs and 4 GiB are allocated for 30 minutes. CPU costs 3,600 vCPU seconds × $0.000024 = $0.0864. Memory costs 7,200 GiB seconds × $0.000003 = $0.0216. The total is **$0.108**; 20 identical sessions would use $2.16 worth of included compute. This is not necessarily an extra charge if your allowance covers it. The example excludes snapshots and AI credits. Stopping a sandbox ends CPU and memory metering, but its saved snapshot remains metered until deletion.", "url": "https://wpnews.pro/news/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23", "canonical_source": "https://dev.to/uulab/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23-4497", "published_at": "2026-11-20 05:09:17+00:00", "updated_at": "2026-11-20 05:14:15.143561+00:00", "lang": "en", "topics": ["ai-tools", "developer-tools", "ai-agents", "mlops"], "entities": ["GitHub", "GitHub Copilot", "GitHub Actions"], "also_reported_by": [], "takeaway": "Copilot cloud sandbox CPU and memory now draw from the same included compute allowance as eligible Actions runners, at $0.000024 per vCPU second and $0.000003 per GiB second, while stopped sandboxes keep incurring $0.005 per GiB-month for retained snapshots until deleted.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23", "markdown": "https://wpnews.pro/news/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23.md", "text": "https://wpnews.pro/news/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23.txt", "jsonld": "https://wpnews.pro/news/github-copilot-cloud-sandboxes-start-drawing-from-actions-compute-on-november-23.jsonld"}}