Fix
Continue.dev rules and AGENTS.md
Answer
Continue project rules are .md files in .continue/rules with YAML frontmatter (name, globs, alwaysApply, description). config.yaml replaces config.json, which is deprecated. The loader also accepts one workspace-root agent file, checking AGENTS.md, then AGENT.md, then CLAUDE.md, and sets alwaysApply: true. When AGENTS.md exists, that file is the agent rule, so a root CLAUDE.md is not loaded beside it. Rules kept only in config.json, .cursor/rules, or .continue/rule/ are missed.
- Scope Tool-agnostic. Written against Cursor project rules (.mdc), Claude Code CLAUDE.md, AGENTS.md, and GitHub Copilot repository instructions as documented on 2026-10-15.
Last verified 2026-10-15
The Vibe Coder Starter pack ships AGENTS.md at the project root and a matching CLAUDE.md. Continue's rules page says to add .continue/rules at the top of the workspace. Its pinned scope is: Tool-agnostic. Written against Cursor project rules (.mdc), Claude Code CLAUDE.md, AGENTS.md, and GitHub Copilot repository instructions as documented on 2026-10-15. See /fixes/codex-cli-agents-md, /fixes/claude-code-claude-md-vs-agents-md, /fixes/cursor-rule-sources-and-precedence, and /fixes/aider-conventions-md.
In .continue/rules, name is the display title, and it is required for YAML rules. globs is one pattern or a list. description is what the agent reads when alwaysApply is false. alwaysApply: true is included on every Agent, Chat, and Edit request. alwaysApply: false waits for a glob match, or for the agent to pull the rule in from the description. If alwaysApply is omitted, the rule is included when there are no globs, or when the globs match. Files load in lexicographical order, so 01-general.md comes before 02-frontend.md. Rules join with newlines in toolbar order and are skipped for autocomplete and apply. A file in .continue/rule/ does not show in the toolbar.
An entry in the config.yaml rules list can be a string, a hub slug such as uses: sanity/sanity-opinionated, or a file:// path. If ~/.continue/config.yaml is present, or %USERPROFILE%\.continue\config.yaml on Windows, that file is loaded instead of config.json, and the old systemMessage string becomes a rules list. An accepted agent file is stored as source agentFile with alwaysApply: true, which overrides frontmatter. .continue/rules Markdown is added after that agent file. One does not replace the other. The break sits after the exists check, not inside it. On the VS Code extension, fileExists returns false for a missing file, so a missing AGENTS.md ends the search before AGENT.md and CLAUDE.md. See https://github.com/continuedev/continue/blob/main/core/config/markdown/loadMarkdownRules.ts and https://github.com/continuedev/continue/blob/main/extensions/vscode/src/VsCodeIde.ts.
Every Loadout free zip includes AGENTS.md and CLAUDE.md at the project root, plus .cursor/rules/<slug>.mdc and .github/copilot-instructions.md. The packs are /packs/vibe-coder-starter, /packs/nextjs-supabase, /packs/unity-6, and /packs/godot-4. None of them ships .continue/rules, config.yaml, or config.json. With both root files present, the agent-file slot is AGENTS.md.
Last verified 2026-10-15. doc-verified.
Pro
Unity 6, Godot 4, and Next.js Pro rules, $1+
$1+ · pay what you want
Advanced rules for the same stacks as the free packs: Unity 6 Pro (Netcode, URP, Addressables, tests), Godot 4 Pro (multiplayer, GDExtension and C#, saves, export), and Next.js 16 + Supabase Pro (RLS, getClaims, Stripe webhooks, caching). Each pack is AGENTS.md, CLAUDE.md, Cursor .mdc, and Copilot instructions. The Phaser 4, three.js, and FastAPI packs stay on the Gumroad download as a bonus. 12 months of free updates.
Each pack ships as AGENTS.md, CLAUDE.md, Cursor .mdc, and Copilot instructions, with 12 months of free updates.
From the Unity 6 Pro rules
Mark an RPC with `[Rpc(SendTo.Server)]` and end the method name in `Rpc`. A missing `Rpc` suffix is an error. Do not write new `[ServerRpc]` or `[ClientRpc]` methods.
A client asks the server with `SendTo.Server`. The server talks to observers with `SendTo.NotServer`, or `SendTo.ClientsAndHost` when a host must run the method too. There is no direct client-to-client connection. The server forwards it.
Keep shared state on a `NetworkVariable<T>` and use `.Value`. It is sent to clients already connected and to a client that joins later. An RPC is not. Write `.Value` from the server when write permission is `NetworkVariableWritePermission.Server`.
Put a `NetworkObject` on the networked prefab and spawn it on the server. Do not use the removed UNet types `NetworkIdentity`, `[Command]`, or `UnityEngine.Networking`.Unity 6, Godot 4, and Next.js Pro rules, $1+Vibe Coder Starter pack — Safe defaults for any AI coding agent, in any stack.
doc-verified
Sources in the pack
Docs
Questions
- Where does Continue load project rules versus AGENTS.md?
- Continue project rules are .md files in .continue/rules with YAML frontmatter (name, globs, alwaysApply, description). config.yaml replaces config.json, which is deprecated. The loader also accepts one workspace-root agent file, checking AGENTS.md, then AGENT.md, then CLAUDE.md, and sets alwaysApply: true. When AGENTS.md exists, that file is the agent rule, so a root CLAUDE.md is not loaded beside it. Rules kept only in config.json, .cursor/rules, or .continue/rule/ are missed.
- Does Continue read CLAUDE.md when AGENTS.md is also at the root?
- No. The loader checks AGENTS.md, then AGENT.md, then CLAUDE.md, and it accepts one workspace-root agent file. When AGENTS.md exists, that file is stored as source agentFile with alwaysApply: true. CLAUDE.md in the same root is not added as a second agent-file rule. Continue-specific rules still belong in .continue/rules.
- Do Loadout free packs ship .continue/rules or config.yaml?
- No. They do not include .continue/rules, config.yaml, or config.json. Every free zip includes AGENTS.md and CLAUDE.md at the project root. The packs are /packs/vibe-coder-starter, /packs/nextjs-supabase, /packs/unity-6, and /packs/godot-4. Continue's agent-file slot is AGENTS.md. Add .continue/rules yourself for a Continue-only rule.
- When was this Continue.dev rules and AGENTS.md rule last checked?
- Last verified 2026-10-15. doc-verified.