Secrets

Secrets are encrypted credentials stored in your account that Neo agents can access during task execution. Use them to provide API keys, tokens, passwords, and other sensitive values without exposing them in task prompts or project context. Secrets are accessible from the key icon in the left sidebar or under Settings → Secrets.

​

Adding a secret

Click + Add Another to add a new secret. Each secret has a name (used as the environment variable key) and a value. The value is masked after saving and never displayed in full again.

​

Always on

Each secret has an Always on toggle. When enabled, the secret is automatically attached to every task you run without needing to select it manually. When disabled, you can still attach the secret to specific tasks or automations by selecting it at task creation time. Always on applies to your own tasks only. It never makes a secret available to teammates. To let teammates use a secret, share it with your team or attach it to a project, as described below.

​

Sharing a secret with your team

Secrets belong to the account that created them and are private by default. To let your teammates use one, set its Access to Team in Settings → Secrets.

• Private: only you can use the secret.
• Team: every Admin and Member of your team can use the secret in their tasks and automations. They cannot see or edit its value, and Viewers cannot use it at all.

A secret shared with you appears in your secrets list with a Shared badge that names its owner. Unlike your own secrets, it is never added to a task automatically: select it in the task bar each time you need it. Only the owner can change a shared secret’s value, rename it, delete it, or set it back to Private. Setting it back to Private, or the owner leaving the team, stops new tasks from using it. Use the filters at the top of the list to show all secrets, only your own, or only those shared with you, and to narrow by access.

​

Attaching a secret to a project

To make a secret available only to members of a specific project, rather than the whole team, attach it to that project. Attachment is per secret and per project: attaching WIZ_CLIENT_ID to one project does not attach it to your other projects, and does not attach your other secrets alongside it. Two consequences worth planning around:

• A new project starts with no secrets attached. Creating a project, or sharing an existing one with your team, does not carry your credentials into it. Each project needs its own attachments.

If teammates report that Neo is unaware of a secret you have configured, the secret is usually private to your account and neither shared with the team nor attached to the project they are working in.

​

Using secrets in tasks

When starting a task, click Secrets in the task bar to select which secrets to make available for that run. Any secrets with Always on enabled are pre-selected automatically. Secrets shared with you by teammates appear in the same list with a Shared badge. Secrets are available to agents as environment variables using the name you assigned. For example, a secret named GITHUB_TOKEN is accessible as $GITHUB_TOKEN inside the sandbox.

​

Using secrets in automations

When creating an automation, select secrets from the Secrets field in the Configuration section. The selected secrets are injected into every scheduled run of that automation.

​

Managing secrets

Rotating a secret: Replace a secret’s value in place from Settings → Secrets. The name stays the same, so every project attachment, automation, and schedule that references it keeps working and uses the new value on its next run. There is nothing to reconfigure. Neo can also save a new secret for you during a task. If an agent needs a credential you haven’t stored yet, it can store it as a secret without you leaving the chat. Deleting a secret: Click the trash icon next to it. Deletion is immediate and cannot be undone. Any tasks or automations that relied on that secret will lose access to it on their next run.