The software world
CI
continuous integration
The automated checks a project runs on every change — typically on every pull request. Tests, linting, a build, sometimes a review pass. They run on someone else's machine, not yours, and report back pass or fail on the PR.
Why it matters
Part of Building Claude into your own software → CI is where automated work becomes team policy rather than personal habit: a check that runs in CI runs for everyone, every time, whether or not they remembered. It's also the most common place to host an unattended Claude — a review pass or a fix attempt triggered by a pull request, running in headless mode with no one watching, which makes the permission scope you give it matter a great deal.
see also