Custom Detection Rules
Got an AI tool we haven't heard of yet? Teach Chau7. It learns fast.
Questions this answers
- How do I add a custom AI tool to my terminal detection?
- Can I detect private or internal AI CLI tools in Chau7?
- Custom process detection rules for terminal AI monitoring
- Add new AI agent to Chau7 detection list
How it works
Chau7 exposes a settings interface where you can define custom detection rules using process name patterns. Each rule maps a pattern to a display name and optional color, so your internal or niche AI tools get the same first-class treatment as built-in agents.
Patterns are matched against the process name and arguments in the tab's process tree. You can use substring matching to catch tools launched through various wrapper scripts or package managers. Custom rules are evaluated alongside built-in rules with no priority conflicts.
Why it matters
The AI tooling landscape moves faster than any vendor can ship updates. Your team's custom fine-tuned model CLI, that internal wrapper around Ollama, the niche open-source agent your coworker swears by: Chau7 can't ship built-in support for all of them, but it can learn. Custom detection rules let you extend detection to anything with a process name.
Frequently asked questions
Do custom rules override built-in detection?
No. Custom rules run alongside built-in rules. If a process matches both, the built-in rule takes precedence to ensure consistent branding for well-known agents.
Can I share custom detection rules with my team?
Custom rules are stored in Chau7's settings and can be exported or version-controlled. Sharing a configuration file is the simplest way to distribute rules across a team.