Core Concepts
IronShift is built on three foundational pillars: flexible operation modes, human-in-the-loop safety, and a structured tool system. Understanding these concepts will help you get the most out of IronShift.
Three Operation Modes
IronShift offers three distinct operation modes, each designed for different workflows:
| Mode | Description | Best For | Tool Access |
|---|---|---|---|
| Chat | Conversational Q&A — explains HOW to do things. Shows Terraform code, CLI commands, and step-by-step instructions without executing anything. | Learning, quick answers, code snippets | None (explanatory only) |
| Plan | Step-by-step planning — shows reasoning process, clarifies ambiguities, breaks tasks into numbered steps before execution. | Complex multi-step operations | Full tools |
| Agent | Maximum autonomy — clarifies once upfront, then chains multiple actions automatically, fixes errors autonomously (max 2 retries). | Hands-free automation | Full tools |
Human-in-the-Loop Safety
IronShift never runs a command without your explicit approval. Every action goes through a safety review:
- Request Analysis — IronShift understands your request and determines the best approach
- Command Preview — You see the exact command(s) that will run, with full parameter transparency
- Risk Assessment — Each operation includes a risk indicator so you understand the impact
- Your Decision — Approve, modify, or reject. Complete control at every step
- Live Execution — Approved commands execute with real-time output streaming
important
CLI commands are used only for read-only discovery (list, describe, show). All infrastructure changes go through the generate_infra tool which generates IaC files for your review before any modification.
The Tool System
IronShift uses a structured tool system to interact with your infrastructure:
| Tool | Purpose | Execution |
|---|---|---|
execute_terminal_command | Run read-only CLI commands to discover and query existing resources | On your machine via IDE terminal |
generate_infra | Generate IaC files (Terraform, Ansible, Kubernetes) for creating, configuring, or deploying resources | Files generated → you review → you confirm → commands execute |
analyze_workspace_project | Scan your IDE workspace to analyze project structure, tech stack, and deployment files | Read-only analysis on your machine |
IaC Generation: Two-Phase Flow
Infrastructure as Code generation follows a safe, two-phase process:
- IaC files are generated and saved to
.ironshift/infra/<timestamp>/ - Files are opened in the editor with a summary of each file's purpose
- You review and confirm before any command executes (
terraform init/apply, etc.) - If existing Terraform files are detected, new files go into a separate folder — nothing is overwritten
- If execution fails, IronShift self-heals: diagnoses the error and regenerates fixed code automatically