# Time travel using the CLI, improved usage visualizations, and more.

### Neon CLI updates

We've added two new capabilities to our CLI:

- You can now establish time travel connections to a particular point in a branch's history. When using the `neon connnection-string {branch}` command, simply append the timestamp or LSN to the specified branch and an ephmeral endpoint is created for that point-in-time connection.

  Example:

  ```bash
  neon connection-string main@2024-01-01T00:00:00Z
  ```

  For more information, see [How to use Time travel](/guides/postgres-backup-restore-time-travel-assist#how-to-use-time-travel) and [Neon CLI commands — connection-string](/guides/apis-sdks-cli-connection-string).

- The Neon CLI now also includes shared projects when you request a list of all projects using the command `neon projects list`.

  Example:

  ```bash
  Projects
  ┌────────────────────────┬────────────────────┬───────────────┬──────────────────────┐
  │ Id                     │ Name               │ Region Id     │ Created At           │
  ├────────────────────────┼────────────────────┼───────────────┼──────────────────────┤
  │ crimson-voice-99897020 │ frontend      │ aws-us-east-2 │ 2024-04-15T11:17:30Z │
  ├────────────────────────┼────────────────────┼───────────────┼──────────────────────┤
  │ calm-thunder-11283270  │ backend      │ aws-us-east-2 │ 2024-04-10T15:21:01Z │
  └────────────────────────┴────────────────────┴───────────────┴──────────────────────┘
  Shared with me
  ┌───────────────────┬────────────────────┬──────────────────┬──────────────────────┐
  │ Id                │ Name               │ Region Id        │ Created At           │
  ├───────────────────┼────────────────────┼──────────────────┼──────────────────────┤
  │ noisy-fire-516816 │ API │ aws-eu-central-1 │ 2023-04-22T18:41:13Z │
  └───────────────────┴────────────────────┴──────────────────┴──────────────────────┘
  ```

  For more information, see [Neon CLI commands — projects](/guides/apis-sdks-cli-projects#neon-projects-list).

### Improved Usage visualizations

- **Usage** section in **Billing**

  For **Launch** and **Scale** plan users, we've added more detail and better visual cues to help you understand your current consumption against your plan's allowances. This includes displaying your peak usage to illustrate any extra charges that might be applied for the current billing period.

  <img src="../img/site-assets/neon.com/docs/changelog/storage_usage_details.png" alt="billing storage details">

- **Usage** widget in the project dashboard

  We've also added some polish to the **Usage** widget on the project dashboard, with tooltips to explain key metrics.

  <img src="../img/site-assets/neon.com/docs/changelog/usage_widget.png" alt="usage widget">

### Fixes & improvements

- Starting May 1, 2024, we're defining 'reasonable usage' for [egress](/guides/postgres-reference-glossary#egress) on Neon's [Free Tier](/guides/plans-billing-plans#free-tier) plan as a 5 GB per month limit.
- We're updating our [status](https://neonstatus.com/) page to provide per-region metrics, letting you view events and history specific to the region where your databases are running. Coming soon!

### What's new in docs?

- Learn how to sync data from platforms like Stripe, Linear, and GitHub into your Neon database in real time with [Sequin](/guides/integrations-tooling-guides-sequin).

## 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.