Verdent: make the code change and its rollback inspectable

Start from a known repository state

The 26 January 2026 description presents Verdent AI for large existing codebases, with visible diffs, code reviews, rollback and parallel agents. It lists Claude, Gemini and ChatGPT model support. Begin with the project’s actual behaviour and a bounded requested change so the resulting diff has a clear purpose beyond producing code.

1. Use the retained product route: https://www.verdent.ai/?id=700133.
2. Follow the interface overview at 1:39 and existing-codebase demonstration at 2:39.
3. Record the starting state and expected behaviour before asking the agent to modify the repository.

Review the change and its recovery route

Testing appears at 3:55, Git integration at 4:10 and built-in review at 4:55. These are different forms of evidence. The diff explains what changed, a test examines a behaviour, and source control provides a history. A review result should be read against the actual implementation rather than accepted as a universal safety certificate.

1. Read the changed files and inspect unexpected edits outside the intended scope.
2. Run the relevant user journey or check and compare the result with the starting requirement.
3. Review findings from the built-in code review and distinguish verified defects from suggestions requiring further investigation.
4. Understand the rollback target before relying on it, including which version the project would return to and what later work might be affected.

Add parallel work and project instructions deliberately

Multi-agent execution starts at 5:38, followed by agents.md and MCP support at 6:42. Parallelism can organise separate jobs, but tasks that touch the same files still need a combined review. Instructions and connected tools also need to fit the specific repository rather than being assumed from another project.

1. Give each agent a bounded responsibility and identify overlapping files before the work starts.
2. Inspect the applicable agents.md instructions and the intended MCP connection through the recorded route; the description does not supply exact installation syntax.
3. Review the combined diff and rerun the affected checks after integration.
4. Check current trial terms separately. The recorded 100 credits without a card and 40% discount with 4U62GW are historical offers, not current access guarantees.

The takeaway

Visible changes are useful when you read them, test the affected behaviour and understand how to recover the previous state.