1. Docs
  2. Infrastructure AI
  3. Settings

Neo Settings

    Organization-level settings control how Neo behaves and what capabilities are available to your team.

    Neo Access

    Neo is enabled by default. To control Neo access for your organization:

    1. Navigate to Neo Settings from the Pulumi left navigation
    2. Select the “General” tab
    3. Toggle “Enable Neo for organization” on or off

    Toggle Neo access

    If Pulumi Copilot was previously disabled, Neo will need to be enabled as outlined below.

    Custom Instructions

    Custom Instructions teach Neo your organization’s standards, preferences, and requirements so they’re applied automatically to every task. Instead of repeating context in each task, you define it once from a central location.

    What to Include

    Custom Instructions can define many things, including:

    • Naming conventions: How resources, stacks, and projects should be named
    • Compliance requirements: Required tags, labels, or configurations
    • Technology preferences: Preferred languages, frameworks, or cloud services
    • Cost guidelines: Budget considerations or cost optimization preferences
    • Automatic actions: Behaviors Neo should apply automatically, like including cost estimates

    Example

    All AWS resources must follow these standards:
    - Naming convention: {service}-{environment}-{region}
    - Required tags: environment and owner
    - Use encryption at rest for all storage resources
    - Always include estimated monthly costs in pull requests when proposing new infrastructure
    

    When you ask Neo to create resources, it automatically applies your organization’s standards without you needing to repeat them in every conversation.

    Configuring Custom Instructions

    1. Navigate to Neo Settings in Pulumi Cloud
    2. Select the “Organization instructions” tab
    3. Enter your organization’s standards and preferences
    4. Save changes

    Custom Instructions configuration

    Custom Instructions Best Practices

    • Keep instructions concise and focused on standards that apply across all tasks
    • Update instructions as your team’s practices evolve
    • Test instructions in individual prompts before rolling out broadly

    Slash Commands

    Slash Commands capture proven prompts as shortcuts that anyone on your team can use. When you type / in a Neo conversation, you’ll see available commands. Selecting a command sends the full prompt to Neo.

    Built-in Commands

    Neo includes several built-in commands for common infrastructure tasks:

    CommandDescription
    /get-startedLearn what Neo can do and how to structure effective requests
    /policy-issues-reportLists your most severe policy violations
    /component-version-reportLists components that are outdated in your private registry
    /provider-version-reportLists providers that are outdated

    Creating Custom Commands

    You can create organization-specific commands to capture your team’s proven prompts:

    1. Navigate to Neo Settings in Pulumi Cloud
    2. Select the “General” tab
    3. Scroll to the “Slash commands” section
    4. Click “Add custom slash command”
    5. Enter a name and description
    6. Define the prompt
    7. Save the command

    Slash Commands configuration

    Once saved, the command is immediately available to all team members.

    Viewing Slash Command Instructions

    When you have selected a slash command in a new or existing Neo task, click on the highlighted command name to view the actual prompt.

    Slash Command Best Practices

    • Create commands for frequently-used prompts that have proven effective
    • Use clear, descriptive names that indicate what the command does

    Task Modes

    Task modes are presets that control what actions Neo can take automatically. Each mode represents a predefined configuration of allowed commands. New tasks start with a default mode, which users can adjust or override during the task.

    Available Modes

    Organization administrators can set the default task mode. The available modes determine how much automation Neo applies:

    • Auto mode: Automatically approves all requests without user intervention
    • Balanced mode: Automatically approves requests that don’t run pulumi up
    • Review mode: Requires manual approval before any request runs

    Configuring Default Task Mode

    1. Navigate to Neo Settings in Pulumi Cloud
    2. Select the “General” tab
    3. Locate the “Task mode” section
    4. Select the default mode from the dropdown
    5. Save changes

    Task mode configuration

    Task Mode Best Practices

    • Start with the most restrictive mode – it’s best for most organizations
    • Remember, users can override the default for individual tasks when needed
      Neo just got smarter about infrastructure policy automation