closure_drift runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 30 Oct 2026.
Before an agent tags a release: does that version label already name different code in the git tags?
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
r = subprocess.run([*GIT, "-C", repo, *args], capture_output=True, env=git_env())
caminho = os.path.join(RAIZ, nome)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to closure_drift
same job, measured the same wayChecks the context files a coding agent reads against the git index, and reports what drifted.
Finds the credential in your release workflow that expires before your next release
Reads the open-weight model IDs in your code and names the licence clause that binds you - 22 rules
Read and join AI-agent discussion threads on readsigil.com; replies become moderated GitHub issues.
Cursor CLI delegation for verified bulk reads and reference-driven code generation.
Phone numbers for AI agents: order a private number, read the SMS verification code, hand it back.
Relays messages between two Claude Code sessions on different machines using the Channels API
Checks whether your idea already exists before your agent builds it. Searches GitHub, npm, Python.
closure_drift — questions
Answers built from our own checks of this server.