There is a point where a vibe coded project stops being a weekend experiment and becomes software you actually maintain. The first few sessions are awesome. You describe and Claude builds features and fixes bugs without a hassle. However, this eventually creates a problem: every session starts with amnesia, which causes: old bugs to reappear; “verified” changes that are not actually being tested; and knowledge about what works in the agent’s session chat history only. Agentic Maintenance Harness (AMH) is a small operating harness for the transition from vibe coding into serious software maintenance. It consists of a constitution file, tiered memory (mirrors ROM/RAM/Disk/Tape), one verification ladder that both the agent and CI run, machine-checked ledger citations, and a few shell scripts for command guards and redaction. These are answers to the failures that might arise when you try to maintain your solo vibe coded project. AMH is agent-agnostic on purpose. CLAUDE.md is just a thin adapter that points Claude at AGENTS.md. So if you have e.g. Codex work on your repo as well it still works. The AMH repository is maintained under the same rules it ships: very meta. Adopting AMH is mostly an automated flow, point Claude or any AI agent at a new or existing repo and send this: Install the latest stable release of the Agentic Maintenance Harness (AMH) into this repository. Run: git clone --depth 1 --branch amh-v5.2.1 https://github.com/faded-penguin021/AMH.git /tmp/amh /tmp/amh/scripts/amh-init.sh . Once the harness has been instantiated, read AMH-ADOPT.md and follow it completely. Present the light, standard, and full profiles, then wait for my choice before proceeding. Drive scripts/ladder.sh to green, explain any manual actions that require my attention, and delete AMH-ADOPT.md when adoption is complete. Do not invent repository information. Derive it from the repository wherever possible. The ledger and guards are an investment at the start and will only yield benefits after a few sessions have edited the repo. You, the human in the loop, will still have three responsibilities: review and integrate changes, read and perform tasks listed in the owner queue, and record test findings upon request for the next session. If you already have a mature setup with some form of memory, guards, etc… this won’t do much. Point Claude at the AMH repo and ask it to critique your existing workflow against AMH’s principles. This will not boost your productivity (in fact it will make your sessions slower) nor will it make Claude smarter. It is process and governance for the period after the adrenaline of “Claude one shot the entire thing” wears off and you need to maintain the project with just yourself and the agent. If Claude isn’t causing problems due to forgetting, skipping verification, leaking secrets, force pushes, or reintroducing bugs, you probably don’t need AMH. If it is, the light profile is a good place to start. Repo link: https://github.com/faded-penguin021/AMH submitted by /u/v_uurtjevragen
Originally posted by u/v_uurtjevragen on r/ClaudeCode
You must log in or # to comment.