Env Drift Inspector

Snapshot and locally verify your dev environment before shipping so "works on my machine" stops biting

Problem

Developers increasingly let AI agents touch both frontend and backend code, but local and server environments drift, causing silent failures. One builder describes wiring an internal tool into an agent workflow, spending two evenings on prompts and retries before it ran, only to find the next release made it a one-line config — like pouring water into a leaky bucket. Another thought their portfolio was public for weeks while only they could see it. The real gap is independent verification that an environment state actually took effect.

Solution

A lightweight CLI that snapshots key environment variables, dependency versions, service reachability and config flags before AI coding or deploys, then re-runs a minimal smoke script in a clean container or ephemeral port. It diffs against the last known-good state and produces a human-readable risk report.

Users

Indie developers and small teams using Claude Code or Codex who maintain both frontend and backend repos

MVP

Support 3 check types: env vars and port reachability; lockfile and runtime versions; a user-provided smoke command in a temporary Docker container; output a markdown diff report; ship as a single CLI binary

Revenue

Free local version plus team subscription for shared baseline snapshots and trends, or a per-project perpetual license; grow through developer communities

Why now

As AI agents write more code, humans are losing the ability to tell which environment conditions really changed; existing container and diff primitives let an indie dev build this without cloud lock-in