Rules

Rules add persistent instructions to agent context. Use Marketplace → Manage → Rules to edit user and project sources.

User rules

User rules are stored in app settings and apply to all chats when enabled and non-empty. A rule has a name and body. Agent V allows up to 16 user rules; names are capped at 64 characters and bodies at 4,000 characters.

User rules cannot override the system constraints, tool policy, or selected mode.

Workspace rules

The app reads workspace instructions in this order:

1. AGENTS.md
2. CLAUDE.md
3. .cursorrules
4. Markdown or MDC files under .cursor/rules/
5. Markdown files under .vyotiq/rules/

Workspace instructions are assembled after user-global rules and therefore win when the two conflict. A single file is capped at 64 KiB, discovery is bounded to 24 files and three nested directory levels, and symlink-style surprises are avoided by the workspace file boundary.

Frontmatter

Directory rule files can use:

---
description: TypeScript changes in the renderer
globs: ["src/renderer/**/*.ts", "src/renderer/**/*.tsx"]
alwaysApply: true
---

Keep Node APIs out of the renderer.

alwaysApply: true injects the body automatically, and an omitted value does too when the rule has no globs. Explicit alwaysApply: false rules are requestable only. Globs change this: when the run has a focused file, a rule auto-injects if that file matches the globs — even with alwaysApply: false — and stays requestable-only when no file is focused.

Create and verify

Use /create-rule to create a workspace rule under .vyotiq/rules/, or use the Rules editor. Changes clear the rule cache and should affect subsequent agent steps without an app restart.

Keep each rule narrow and testable. Do not put API keys, tokens, or private chat content in rule files; workspace rules are ordinary project files and can be committed.