Create a custom agent type
Add an agent type with its own description, instructions and tool mode, so Chetty knows when to pick it and what it may do.
Create one
The Agents page lists every built-in and custom type. An administrator creates, edits and deletes custom types there.
- Open Agents and choose Add agent.
- Enter a Name in lowercase kebab-case, such as
code-reviewer. - Write a one-line Description. Chetty reads it to decide when to delegate to this type.
- Write the Prompt: the agent's role, its limits and how it reports the result.
- Choose the tool mode (see below), then Save agent.
Note: Built-in types cannot be edited and carry the built-in badge; custom ones carry custom. Delete a custom type with Delete agent, which removes it permanently.
Limits: a name of 1 to 64 lowercase letters, digits and single interior dashes; a description of up to 4,096 characters; instructions of up to 65,536 characters. Editing a type requests a daemon restart before new conversations use the updated catalog.
Tip: Everyone can view the page, but a custom type's instructions are returned only to administrators. Other accounts see its name, description and tools.
Choose the tool mode
Tools decides what the agent may use.
- Read-only (+ non-destructive shell) provides non-editing tools and a shell limited to non-destructive commands.
- All (full toolset) gives the agent everything the caller has.
- Inherit the caller's tools passes on the delegating conversation's tools unchanged.
- Custom list… takes exact tool names in the Tool list, for example
Read, Search, Bash.
Whatever you choose, a delegation can still narrow the tools further, and no type can widen the caller's access.
Choose the model
Each built-in type has a Model group you can open, and a custom type has Agent settings; both use the same rows and the same model picker.
- A built-in type's choice applies only to your own account and needs no administrator.
- A custom type's model applies to everyone who delegates that type.
- The empty choice reads Inherits the caller's model, or None for a built-in type, and then the child runs on the delegating conversation's model.
- A stored model that the catalog no longer offers shows as unavailable.
Each group can be folded and remembers its state separately, and saving keeps your other pins. If another tab changed the settings, reload them or merge, which keeps the remote changes to pins you did not edit.