Lovable: Reads AGENTS.md and CLAUDE.md Files in Subfolders
LovableLovable now reads AGENTS.md and CLAUDE.md instruction files in a project's subfolders, not just the root. When it opens or edits a file, it follows the instruction files in that file's folder and in every parent folder above it. This lets teams scope rules to specific parts of a codebase.
Key Takeaways
- Lovable now reads AGENTS.md and CLAUDE.md files in subfolders, not just the project root.
- When working on a file, it follows instruction files in that file's folder and every parent folder.
- Rules can be scoped to one area of a codebase, such as frontend or backend.
- Teams with existing instruction files for other agents can reuse the same layout in Lovable.
- Root-level rules still apply everywhere, with nested files adding more specific guidance.
- Shorter, local instruction files avoid one oversized root file.
Instruction Files Beyond the Project Root
Lovable now follows AGENTS.md and CLAUDE.md files placed in a project's subfolders, instead of only reading the ones at the repository root. Teams that already keep instruction files for other coding agents can have Lovable respect the same structure.
How Lovable Picks Which Files to Read
When Lovable opens or edits a file, it reads the instruction files in that file's own folder and in every parent folder above it. A rule in a frontend/ folder therefore applies to work inside frontend/ without affecting the backend, while rules at the root still apply everywhere.
Why It Matters
Larger projects often have different conventions in different areas, such as separate styling rules for the UI and separate patterns for server code. Placing instructions next to the code they govern keeps each rule short and relevant, and avoids one large root file that tries to cover everything.