---
title: "Comment by Vic Moreno on \"When Two AI Agents Drift Apart\" | Hashnode"
description: "For the Claude side there is a shortcut before any script: its memory file can import another file with an @ path, so a single line pointing at the AGENTS file"
url: "https://hashnode.com/posts/when-two-ai-agents-drift-apart/6b002b532cb3133aa9b0438a/comment/6b002ea7595f81e2cac588a4"
---

[Discussion](https://hashnode.com/posts/when-two-ai-agents-drift-apart/6b002b532cb3133aa9b0438a)

Comment [When Two AI Agents Drift Apart](https://hashnode.com/posts/when-two-ai-agents-drift-apart/6b002b532cb3133aa9b0438a)

[Vic Moreno](https://hashnode.com/@itsvicmoreno)

[1d ago](https://hashnode.com/posts/when-two-ai-agents-drift-apart/6b002b532cb3133aa9b0438a/comment/6b002ea7595f81e2cac588a4)

For the Claude side there is a shortcut before any script: its memory file can import another file with an @ path, so a single line pointing at the AGENTS file leaves one source to maintain. Copilot instructions still need their own copy, which is where a CI check earns its keep. Does yours fail the build on drift or only warn?

[mortylen](https://hashnode.com/@mortylen)

[1d ago](https://hashnode.com/posts/when-two-ai-agents-drift-apart/6b002b532cb3133aa9b0438a/comment/6b002ea7595f81e2cac588a4#reply-6b00335575c660b7bfe57a39)

Good point, thanks. For Claude, that's the simpler solution: one `@AGENTS.md` line in `CLAUDE.md` and you have a single source. The imported file is loaded together with `CLAUDE.md`, so it helps with maintenance but doesn't reduce the context size.

Copilot is different. Its instructions need their own copy, and that's where a CI check comes in handy, whether it's AIContext or a plain diff.

On drift, the build fails. Both `aicontext validate --strict` and `aicontext export --target all --check` exit with code `1`, so the CI job fails. The difference from an import is that AIContext generates `CLAUDE.md` as a full copy. If you only use Claude and `AGENTS.md`, the import is enough and you don't need any extra tools.
