NOAN provisions agents for new projects and separates free-plan keys

NOAN’s [November 2 changelog](https://www.getnoan.com/changelog/every‑new‑project‑comes‑with‑its‑own‑agent) makes agent provisioning part of new project creation, including signup, later projects and guest onboarding. Agent identities already existed; the change removes the separate setup step for a fresh project. Free‑plan workspaces also get an allowance of one agent key alongside one personal key. Look in the workspace’s API key settings before connecting an automation: the agent can use its own credential rather than borrowing a person’s. The announcement covers new projects; it does not establish automatic retrofitting of existing projects or verify the permissions of a particular integration.

Before connecting automation, check both the identity it uses and the actions it may request. The [Enterprise System Design Reference](https://opentools.ai/resources/enterprise‑system‑design) covers that broader authority question. Use it to frame an architecture review alongside NOAN’s product documentation. Archival physical‑card access to a computer; context, not NOAN’s interface or staff. Photo: Kendra N. Fulton / U.S. Air Force, distributed by [NIST](https://www.flickr.com/photos/usnistgov/5884514004) / [Wikimedia Commons](https://commons.wikimedia.org/wiki/File:PIV_Cards_(5884514004).jpg). U.S. government work, public domain. Resized and cropped for display.