explaingit

air-verse/air

📈 Trending23,549GoAudience · developerComplexity · 2/5ActiveLicenseSetup · easy

TLDR

Live-reload tool for Go development that automatically rebuilds and restarts your application whenever you save a file.

Mindmap

mindmap
  root((air))
    What it does
      Auto-rebuilds on save
      Restarts application
      Watches file changes
    How to use
      Run air command
      Configure with TOML
      Customize build steps
    Use cases
      Web server development
      Quick iteration loops
      Framework projects
    Tech stack
      Go language
      TOML config
      Docker support
    Features
      Environment variables
      Ignore patterns
      Custom arguments

Things people build with this

USE CASE 1

Speed up Go web server development by automatically restarting your Gin or other framework server on every code change.

USE CASE 2

Eliminate manual rebuild-and-restart cycles when iterating on CLI tools or backend services written in Go.

USE CASE 3

Run live-reload development inside Docker containers without needing to manually rebuild images between code changes.

USE CASE 4

Load environment variables from .env files automatically before each rebuild during local development.

Tech stack

GoTOML

Getting it running

Difficulty · easy Time to first run · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Air is a live-reload tool for Go applications. The problem it solves is a tedious development loop: when you change your Go code, you normally have to stop the running program, recompile it, and restart it manually before you can see the effect. Air automates all of that, you run it once in your project folder, and whenever you save a file, it automatically rebuilds your program and restarts it in the background. You just run the "air" command in your project directory, and it watches for file changes. When it detects one, it runs your build command (typically "go build"), and if the build succeeds, it kills the old process and starts the new one. Configuration is done through a TOML file where you can customize which directories to watch, which to ignore, what build command to run, and how to pass arguments to the resulting binary. It also supports loading environment variables from .env files before each build, and it can run inside Docker containers. You would use this during Go development whenever you are iterating quickly on code and don't want to manually restart your server or application after every change. It is especially common when building web servers with frameworks like Gin. It is strictly a development tool and is not meant for production deployments. The tool is written in Go.

Copy-paste prompts

Prompt 1
How do I set up Air for my Go project and what does the TOML configuration file look like?
Prompt 2
Show me how to configure Air to ignore certain directories and only watch my source code folder.
Prompt 3
How do I use Air with a Gin web server to automatically restart on code changes?
Prompt 4
Can I run Air inside a Docker container and what configuration do I need?
Prompt 5
How do I pass custom arguments to my Go binary when using Air for development?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.