Custom Agents & Rules
Your project. Your way of working.
Give recurring tasks a clear role and your project a shared set of instructions. Custom Agents, Rules and LURUS.md bring different kinds of context to the same workflow.
Profiles and rules are reviewed instructions, not guarantees. Agent tools and models remain subject to the active permissions and availability.
An agent profile defines its role, tools and working instructions.
-
Define the role.
An agent profile describes a specialist’s purpose and instructions. It can specify tools, a model and a turn limit.
-
Inspect before calling.
List and inspect the available profiles. Trust decisions and model availability are checked when an agent is called.
-
Use it for a clear task.
Call the chosen agent explicitly with its key and a focused task. Its tool list cannot grant unlimited access.
Context for the whole project
Roles specialise. Rules align.
Keep architecture, commands and conventions in LURUS.md. Rules add shared instructions. /config and /rules help you inspect the setup; newly created rules need a new session to apply.
Create your own agent.
Create .lurus/agents/reviewer.md in your project and save this profile in it. Use ~/.lurus/agents/reviewer.md to make it available across projects. The filename reviewer is the key used to call it.
Start a new CLI session after creating or editing the profile. This example is read-only. Inspect the profile, approve it with trust and call it with a specific task.
---
name: Reviewer
description: Review correctness and tests
tools:
- Read
- Grep
- GitInspect
maxTurns: 12
---
Check correctness and tests. Report concrete findings with file references. Do not change files.Know which instructions are loaded.
Start with the existing profiles and project context. Use a real listed key when inspecting or running an agent.
- List agent profiles
/agents list - Show profile metadata and file path
/agents show reviewer - Approve the reviewed profile
/agents trust reviewer - Run the reviewer
/agents run reviewer Review the current changes and tests.
Your code stays yours.
Source code and request context are processed with Zero Data Retention. No use for model training. Providers and processing regions are disclosed transparently.
See privacy and processing detailsA few things to know before you start.
Are Custom Agents the same as orchestration?
Can an agent profile bypass permissions?
Do rules guarantee that conventions are followed?
Custom Agents & Rules
Give the next task the right specialist.
Start with the profiles and instructions already in your project. Review the role, then hand it a clear task.
Profiles and rules are reviewed instructions, not guarantees. Agent tools and models remain subject to the active permissions and availability.
Want to start with your team? Talk to us.