# Personal Cloud Agent environment missing documented Agent Network Access

**URL:** <https://forum.cursor.com/t/personal-cloud-agent-environment-missing-documented-agent-network-access/177684>\
**Category:** Help\
**Tags:** cloud-agents, security\
**Created:** [November 8, 2026, 2:03am UTC](https://forum.cursor.com/t/personal-cloud-agent-environment-missing-documented-agent-network-access/177684 "2026-11-08T02:03:10Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [November 8, 2026, 11:41am UTC](https://forum.cursor.com/t/personal-cloud-agent-environment-missing-documented-agent-network-access/177684/5 "2026-11-08T11:41:29Z")

</div>

Hi @Vadim_Karpenko1, environment-level network settings, including Allowlist only, are supported on personal accounts and don’t need an upgrade. The new dashboard’s environment page doesn’t show the Agent Network Access control yet, which is why the docs link lands on a page without it. I’ve passed that to the team.

In the meantime, if the environment is repo-managed, you can set it in that repo’s `.cursor/environment.json` and then trigger a new build:

```json
"egressMode": "network_settings_only",
"egressAllowlist": ["api.example.com"]

```

Only that environment changes. Your other environments keep inheriting your user setting.

---

_[View the full topic](https://forum.cursor.com/t/personal-cloud-agent-environment-missing-documented-agent-network-access/177684)._