# Changelog Aug 09, 2024 - Neon

### Safer project deletes

We've heard you. Where it might have felt just a little _too_ easy to delete a project — along with its branches, databases, and roles — we've added a bit more friction to the process. You now have to type out the name of your project by hand before you can delete.

<img src="../img/site-assets/neon.com/docs/changelog/confirm_delete-wmtmo7.png" alt="type project name to confirm delete">

### Local File Cache (LFC)-aware autoscaling

As we continue to mature our Autoscaling offering, we've rolled out LFC-aware autoscaling to all regions.

<img src="../img/site-assets/neon.com/docs/changelog/autoscaling_real.png" alt="Alt text">

_One hour of real-time autoscaling from a selection of your databases._

The idea behind this feature is to improve performance by keeping your entire working set (a subset of frequently accessed or recently used data) in memory. We already [recommend](/guides/manage-operate-manage-computes#sizing-your-compute-based-on-the-working-set) this in the docs, and we've now made it a native part of how autoscaling works: your compute now dynamically resizes to fit your working set within the LFC.

If you're not familiar with Neon's Local File Cache (LFC), you can learn more about it here: [What is the Local File Cache?](/guides/postgres-extensions-neon#what-is-the-compute-cache)

:::accordion{title="Fixes & improvements"}
- The authorization flow initiated by `neon auth` now asks for additional permissions. This update is part of the groundwork for the upcoming Early Access release for Organization accounts. Stay tuned!
- We now dynamically set the maximum size of the LFC (Local File Cache) according to your compute's max CU. Previously, the max size was set to a static 100 GiB, which sometimes caused compute to run out of space in the LFC disk.
- We've renamed our **Free Tier** to **Free Plan** everywhere: our website, our docs, and our console.
- Fixed a mismatch between a selected timezone range (UTC) and the local timezone showing on different graphs on the Monitoring page, which sometimes caused misleading reports or missing data.
:::

## Related pages

- [Add users and authentication](./auth-index.md)
- [AI tools for Agents](./ai-agents-on-neon-index.md)
- [APIs & SDKs](./apis-sdks-index.md)
- [Changelog](../changelog.md)
- [Explore the full platform: functions, object storage, AI Gateway, and more](./neon-docs-index.md)
- [Integrating with Neon](./building-on-neon-index.md)
- [Lakebase Postgres](./postgres-index.md)
- [More](./more-index.md)
- [Neon AI Gateway](./ai-gateway-index.md)
- [Neon community](./community-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.