What’s new in Codespaces for Organizations

GitHub has introduced new features to manage Codespaces effectively, aiming to reduce waste and ensure compliance with budgets for organizations. Inactive Codespaces will now automatically delete after 30 days of inactivity, with users notified 24 hours prior to deletion, and this retention period can be adjusted up to 30 days. Organization administrators can set a maximum retention period that overrides individual settings, providing more control over costs and security. Additionally, organization-level REST API and CLI commands are now in public beta, enabling admins to programmatically manage Codespaces at scale, including listing, stopping, and deleting them across repositories. These updates apply to new Codespaces created after the release and are available across GitHub Free, Team, and Enterprise Cloud plans, with a call for user feedback to refine these features further.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.