What is a rule?
A rule has four parts:- Name: lowercase letters, numbers, and hyphens, such as
python-style. - Description: an optional summary shown when you mention the rule.
- Instructions: the guidance itself.
- Mode: whether the rule applies on every message or only when you call it.
Rule modes
- Always applied rules join every message’s context with no action from you. Use them for preferences you always want, such as “Use SI units for all measurements” or “Never delete files without confirmation.”
- Manual rules apply only to a message that mentions them. Use them for guidance you need sometimes, such as conventions for one kind of analysis.
Rule scope
Under Applies in, every rule is either Global or This workspace:- Global rules apply in every workspace.
- This workspace rules apply only in the current workspace.
Create a rule
- Open the gear menu in the titlebar, choose Customize agent, then choose Rules.
- Open the New rule menu and choose New rule.
- Choose where it applies, then enter a Name, an optional Description, and the Instructions.
- Choose a Mode: Always applied or Manual.
- Click Create.
Use a manual rule
To apply a manual rule, type@rule: followed by its name in your message:
“@rule:data-analysis Analyze this dataset and find anomalies”Qualia adds the rule’s instructions to that message’s context only.
Add a file path rule
A file path rule points the agent at a folder of code on disk. With it, the agent assumes imports in your notebooks resolve from that path. To add one, open the New rule menu and choose New file path. File path rules are always applied. Like other rules, they can be global or scoped to a workspace. Use a global file path for code you share across workspaces, and make sure the path exists on the machine running the workspace.CLAUDE.md and AGENTS.md
If your workspace root has aCLAUDE.md or AGENTS.md file, Qualia reads it on every message, like an always-applied rule. Keep workspace instructions in these files so that they live in version control beside your code.
Import rules
Import rules from other tools on local workspaces. These options read folders on the machine your workspace runs on, so they don’t appear in Qualia Cloud. Each option is in the New rule menu on the Rules page.- Import from Cursor copies the rules in
~/.cursor/rules/. A rule withalwaysApply: truebecomes an always-applied rule; every other rule becomes manual. - Import from Claude Code copies the
RULE.mdfiles in~/.claude/rules/and in the workspace’s.claude/rules/folder. - Import from file… asks for the full path to one file, such as a
CLAUDE.mdoutside your workspace. Its contents become a new always-applied rule.
Re-import rules
Importing makes a copy, so later edits in Cursor or Claude Code don’t reach Qualia on their own. If you import again after the source changed, Qualia lists the rules it would replace and asks first:- Keep mine leaves your copies as they are.
- Update from Cursor or Update from Claude Code replaces each listed copy with the source version. Edits you made to those rules in Qualia are lost.
Edit rule files on disk
On local workspaces, open the New rule menu and choose Open Rules folder to open the rules folder in your file manager. Each rule has its own folder with aRULE.md file. Qualia picks up edits you make on disk automatically.
Qualia Cloud has no rules folder to open, so edit rules on the Rules page instead.
How rules combine
Rules stack. Every always-applied rule, your workspace’sCLAUDE.md or AGENTS.md, and any manual rules you mention all apply to the same message. A common setup:
- One always-applied rule for your global preferences.
- Manual rules for different contexts, such as data analysis, model training, or visualization.
- A
CLAUDE.mdfor workspace-specific conventions.
Write effective rules
- Be specific. Don’t write vague rules such as “write good code,” because they give the agent nothing to act on. Write “Use tqdm in for loops” or “Add docstrings to all functions” instead.
- Keep each rule to one concern. Don’t mix Python style and chart styling in one rule, so that you can change each on its own.
- Test new rules. After creating a rule, try a few prompts to confirm Qualia follows it.
- Review rules as your work changes. Outdated rules keep steering the agent toward old habits.
Pipelines
A pipeline is a saved set of instructions that produces an artifact each time it runs, such as a report, dashboard, or presentation. Find pipelines under Customize agent > Pipelines. To start a run, select a pipeline and click Run now. Each run opens its own chat, which you’ll find under Pipelines in the Chats sidebar, and writes its own output. To create a pipeline, click New pipeline and fill in its Name, Target artifact, Artifact folder, and Instructions. You can also ask in chat, for example: “Make a pipeline that downloads Hacker News data and visualizes current trends.” The agent investigates the sources and asks you about missing decisions. Then it saves the instructions and continues in the same chat as run 1. The first run builds its artifact in its own output folder and leaves your existing files where they are. Later runs follow the saved instructions, write separate outputs, and can read earlier results to explain what changed. See Follow pipeline runs for how report outputs display. In a shared workspace, pipelines and their schedules belong to the person who created them. Collaborators can see the resulting files and run chats, and they manage their own pipelines. Two people’s pipelines with the same name keep separate run histories.Scheduled runs
On Qualia Cloud, a pipeline can run on a schedule. In local workspaces, you start runs manually.- Select the pipeline and click Edit pipeline (the pencil).
- Under Schedule, choose a Frequency: Every N minutes, Hourly, Daily, Weekly (pick the weekdays), Monthly (pick the day), or Custom cron.
- Choose a Timezone. Schedules follow that timezone’s clock, so 9 AM in New York stays 9 AM across daylight-saving changes.
- Choose when it Ends: Never, on a date, or after a number of runs. A schedule that reaches its end turns itself off.
- Check the summary and the next run times, then save.
- If the previous run is still going when the schedule fires, Qualia skips that occurrence instead of queuing it.
- After downtime, Qualia starts at most one run, rather than replaying every missed run.
- Scheduled runs pause when the account reaches its usage limit.
- If the pipeline’s creator loses Owner or Editor access, its scheduled runs stop.

