# Rules # Rules Rules let Chronoid classify activity automatically. They are used across project assignment, distraction handling, ignore behavior, and web blocking. ![Rules editor configuration](/docs/rules/rule-config.png) ## Condition Types Chronoid currently supports these condition types: | Type | What It Matches | Example | | --- | --- | --- | | **App Name** | Application display name | `Safari` | | **Application** | Bundle identifier | `com.apple.Safari` | | **Window Title** | Active window title text | `Sprint Planning` | | **Website URL** | Domain name | `github.com` | | **URL Path** | URL path only | `/docs/api` | | **File Path** | File or folder path | `/Users/me/Projects` | | **Keyword Match** | Title, path, domain, and URL text | `meeting` | | **Title or Path** | Window title and file path together | `README` | | **Full URL** | Complete URL including domain and path | `instagram.com/reel/` | ## Operators Chronoid supports these operators: | Operator | Meaning | | --- | --- | | **Equals** | Exact match | | **Contains** | Text appears anywhere | | **Starts With** | Value begins with the text | | **Ends With** | Value ends with the text | | **Matches Regex** | Regular expression match | | **In** | Matches a predefined group | | **Not In** | Excludes a predefined group | Regex and group-based operators are useful when broad text matching is either too loose or too repetitive. ## Where Rules Are Used - [Project Auto-Assignment](/docs/projects/project-auto-assignment) - [Distraction Management](/docs/distraction/manage-distraction) - [Ignore Tracking](/docs/trackings/ignore-tracking) - [Web Blocker](/docs/web-blocker/web-blocker) ## Compound Rules Chronoid supports nested rule groups, so you can combine conditions with logic such as: - **AND** - **OR** - **NOR** That makes it possible to build rules like: - a specific domain **and** a matching title - a project assignment for one app **but not** a predefined distraction group - a full URL pattern using regex ## When To Use Newer Types - Use **Full URL** when the domain alone is not specific enough. - Use **Title or Path** when file-based work can appear either in a window title or in a filesystem path. - Use **Matches Regex** when you need one rule to cover many similar patterns. ## Tips - Start with the narrowest rule that solves the problem. - Use **Website URL** for broad domain matching and **Full URL** for route-specific matching. - Test regex rules carefully before relying on them for billing or auto-assignment. - Review older rules after major workflow changes so they do not overmatch. For help, email [support@chronoid.app](mailto:support@chronoid.app) --- Source: https://www.chronoid.app/docs/rules/rules