Agent

The agent is the core of Infracodebase. From your enterprise settings, you configure what the agent can do, what it can't do, and what requires approval.

Built-in tool permissions

The agent has built-in tools organized into categories. You control which ones are available across your organization.

  • File Operations for reading, writing, and editing files
  • Search for finding files and searching content
  • Shell for executing commands
  • Web for fetching URLs and searching the web
  • Agent for task delegation and planning
  • Extensions for skills and slash commands

You can enable tools individually or use presets like All, Read Only, or None.

Infrastructure CLI tools

Control which infrastructure tools the agent can use. These span several domains.

  • Infrastructure as Code including Terraform, OpenTofu, Pulumi, and Terragrunt
  • Cloud Providers including AWS CLI, Azure CLI, and Google Cloud CLI
  • Container Orchestration including Kubernetes and Helm
  • Configuration Management including Ansible
  • Security and Quality including Checkov, tfsec, TFLint, terraform-docs, and Infracost

Permission rules

Beyond toggling tools on and off, you can create custom rules with pattern matching for fine-grained control. To create a rule, select a tool from the dropdown, choose a mode, and enter a pattern.

Two modes are available.

  • Deny means the agent cannot take the action at all
  • Require approval means the agent must get human sign-off before proceeding, with a full audit trail

Rules are evaluated in order. Deny rules are checked first, then require approval, then allow. The first matching rule wins.

Patterns support wildcards and vary by tool type. For example, npm run * matches any shell command starting with "npm run", while **/*.tf matches Terraform files anywhere in the tree. See Agent Rule Patterns for full syntax, path prefixes, and examples.

Configuration hierarchy

Enterprise agent settings apply as the baseline across all workspaces. Workspaces inherit these permissions and cannot override denied actions. This means enterprise administrators maintain control regardless of who's building or what workspace they're in.