Site-Specific Instructions

Overview

Your account-level custom instructions and default model apply everywhere. Site-Specific Instructions (Site Rules) let you override that for a single website — so Evelant can behave one way on your documentation site and a different way on your inbox, without you having to remember to change your settings back and forth.

Why this is different from a per-message request

You could always just tell Evelant your preference in a single conversation, but that only lasts for that one chat. A site rule is set once and applies automatically every time you're on that domain, without you having to think about it — closer to a standing preference than a one-off instruction.

Setting up a rule

1. Go to Settings → Site Rules.
2. Enter a domain — either a specific site (example.com) or a wildcard for all of a site's subdomains (*.example.com). Pasting a full URL is fine too; it's automatically reduced to just the domain.
3. Click Add rule.
4. Configure what you want different on that site:
   • Evelant on this site — Default, Always show, or Never show.
   • Page reading — Default, Never, Balanced, or Full (how much of the page Evelant reads automatically).
   • Model — Default, or pin a specific model for this site.
   • Extra instruction on this site — a short free-text note, applied on top of your account's own custom instructions whenever you're on this site.
5. Changes to the note save automatically when you click away from the field; the dropdowns apply as soon as you change them.

What each setting actually does

• Never show turns Evelant off entirely on that site — no orb, no page reading, no keyboard shortcuts. Useful for sites where you never want it active, like your bank or an internal admin tool.
• A pinned model always answers on that site with the model you chose, overriding whatever your account default or the composer's model picker would otherwise use.
• A note is added as extra context whenever you chat on that site — for example, "This is a legal reference site, always cite the specific section" — without needing to repeat it in every conversation.

How rules resolve

• A rule for an exact domain takes priority over a wildcard rule that would also match it. If you have a rule for *.example.com and another for docs.example.com, the more specific one wins on docs.example.com.
• Anything left on Default in a rule simply falls through to your normal account settings — you don't need to fill in every field, only the ones you want to override.

Tips

• Use wildcards for whole platforms, not just one page — *.example.com covers every subdomain of a site, which is usually what you want for something like a company's own suite of tools.
• Pin a model where it matters, not everywhere. If a particular site benefits from a specific model's strengths (like long-document reading), pin it there rather than changing your account default globally.
• "Never show" is reversible. You can always come back and change it, or delete the rule entirely — nothing about disabling Evelant on a site is permanent.

Worked examples

Turning Evelant off on sensitive sites. Add a rule for your bank's domain (or your company's internal admin tools) and set "Evelant on this site" to Never show. From then on, visiting that domain doesn't show the orb at all, on any tab, until you remove or change the rule.

Pinning a model for a documentation site. If you find a particular model gives better answers when reading long technical documentation, add a rule for that documentation site's domain and set Model to your preferred one. Every question you ask while on that site uses it automatically, without changing your account default.

A standing note for a reference site. Add a rule for a legal or policy reference site with the note "Always quote the specific section number you're citing." Every conversation on that site now carries that instruction automatically.

Managing existing rules

Your rules are listed under Settings → Site Rules in the order you added them. Edit any field directly, or remove a rule entirely if you no longer need it — removing a rule returns that site to your normal account defaults immediately.

Troubleshooting

My rule doesn't seem to be applying. Double check the domain you entered matches exactly (including whether it needs the *. wildcard prefix for subdomains) — a rule for example.com alone won't automatically apply to app.example.com unless you used the wildcard form.

I set "Never show" but still see the orb. Refresh the tab — site rules are read when a page loads, so a tab that was already open before you added the rule won't pick it up until it reloads.

Two rules seem to conflict. Only the most specific matching rule applies, not both — check whether you have both a wildcard and an exact-domain rule for the same site, since the exact one always wins.

Frequently asked questions

Is there a limit to how many rules I can add? Yes — up to 100 rules per account, which comfortably covers most people's regular set of sites.

Do site rules sync between devices? They're tied to your account, so signing in on another device gives you the same rules.

Can I set a rule for a specific page instead of a whole site? Site Rules apply at the domain level, not to individual URLs — for page-level control within a single site, see Full-Page Deep Scan's page-visibility options instead.

If I don't set a rule for a site, what happens? Nothing changes — your account defaults apply exactly as they would anywhere else. Site Rules are opt-in overrides, not something you need to configure for every site you visit.

Can a site rule change my response style, not just the model? The note field can carry any instruction, including style preferences — "keep answers brief on this site" works the same way a longer instruction would.

Related features

• Multi-Model AI — for how model selection normally works outside of a site rule's override.
• Custom Appearance — for account-wide preferences that apply everywhere, rather than one site at a time.