Context & Rules
Set up your routing once in the dashboard so the right instructions, knowledge, and automations fire on every email — no command syntax required
Context: reusable instructions & knowledge
A Context is a Markdown document you author or upload in the dashboard — standing instructions (how the AI should behave) or knowledge (reference material the AI can draw on). If you're new to Markdown, don't worry — it's basically a text file with a few formatting rules that are easy to learn. Because it comes through your authenticated dashboard, Airbox treats it as trusted authority, the same trust level as your command line (subject, first body line, or (* … *) block). Untrusted email content can never add or change a Context.
| Kind | Use it for |
|---|---|
| instruction | Behavioral standing instructions — tone, format, what to always do |
| knowledge | Reference material — rubrics, product facts, style guides |
Manage Contexts under Context in the dashboard. Each Context has a slug (a stable handle derived from its title) used by the +slug email syntax below.
Three ways to attach a Context
| How | When it applies |
|---|---|
| Inbox default | Attach to an address so it is used on every email to that address |
| +slug in the email | Attach for one email, from the trusted instruction surface |
| A rule action | Auto-attach when an email matches conditions you define |
The +slug verb command names a saved Context by its slug. Put it on the trusted surface (subject, first body line, or a (* … *) block), alongside any target or command:
(* @claude #reply +legal-style *)
Unknown or unowned slugs are ignored (never an error). Only the trusted surface is parsed, so a stray + inside forwarded content does nothing.
Rules: if-this-then-that automation
A Rule runs logic filters and conditions over an email and applies pre-authored actions to the routing plan when its conditions are met. Conditions are plain boolean (true-false) and/or matching tests run on your email(s) information. The sender allowlist runs before rules, so only mail you trust is ever evaluated.
| Condition field | Operators |
|---|---|
| from | contains, equals, matches |
| subject | contains, equals, matches |
| body | contains, equals, matches |
| has_attachment | is true / is false |
| Action | Effect |
|---|---|
| Route to connection | Send the email to a specific LLM provider |
| Attach context | Add a saved Context to the prompt |
| Attach tool | Expose an MCP/tool connection for this email |
| Set instruction / command | Override the instruction or set a built-in #verb |
| Set reply | Force an email reply on or off |
| Tag | Label the message for your activity log |
| Stop | Drop the email (log it, do not route) |
All matching rules apply top-to-bottom; turn on Stop evaluating later rules on a rule to halt there. Build and reorder rules under Rules, and use the Test against a sample email panel to see exactly why a rule fires before you rely on it.
Recipes: one-click setups
Not sure where to start? Recipes are pre-built bundles of Context and Rules for common workflows, grouped by use case — general productivity, sales, customer support, finance & operations, and more. Open Recipes, pick one, and Apply — Airbox creates the Context docs and Rules on your account, already wired together. Everything a recipe adds is a normal Context or Rule you can edit afterward.
Plan limits
Context and Rules counts are capped per plan. Applying a recipe that would push you over a cap prompts an upgrade instead.
| Free | Pro | Team | |
|---|---|---|---|
| Saved contexts | 3 | 50 | 200 |
| Rules | 1 | 50 | 200 |