ai rules.md

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Agent Personalization

Glue Agent Personalization lets you personalize Glue AI's behavior, ensuring that its responses and suggestions align with your unique communication style and preferences.


📘 What can you personalize?

The Agent Personalization feature lets you set user-defined instructions that guide Glue AI's interactions within the platform. Similar to Custom Instructions in other AI tools, these rules are currently set on a per-user basis. There are different types of rules you can set.

Messaging Rules

Messaging Rules guide how Glue AI interprets and responds to your direct requests when you message Glue AI or @ mention Glue AI in a message. They allow you to specify preferences regarding tone, formatting, language, and more.

Potential Use Cases for Messaging Rules

Suggestion Rules

Suggestion Rules customize how Glue AI proposes content within the Glue application, with options to set rules for thread names, recipient suggestions, and group emojis.

Potential Use Cases for Suggestion Rules

MCP Server Rules

You can also customize how Glue AI should interact with each MCP Server by configuring rules on a server by server basis. You can find more information about configuring MCP Server rules here.

Potential Use Cases for MCP Server Rules

How to personalize Glue AI

1) Open Glue preferences
2) Go Agent Personalization
3) Add rules to the Messaging and Suggestion Rules sections

✅ Tips for Writing Effective Rules

Examples of Agent Personalization

Messaging Rules Examples
- Respond to all messages in a formal tone, using complete sentences.
- When discussing financial reports, assume the audience has a basic understanding of accounting principles.
- When summarizing meeting notes, use bullet points. E.g., '• Discussed Q3 targets • Reviewed marketing strategy.'
Suggestion Rules Examples

Thread naming

- If a thread context includes a link to a Linear issue or Figma file, prefix the thread name with "Project:" Don't add "Project:" if a user just types the the word "project" or "link".
- If the thread is describing a bug that a customer is experiencing or that the team has noticed via logs or reports, prefix the thread name with "🐛 Bug:"

Thread recipients

- If a thread is describing an API bug, suggest the API group.
- If the thread is describing a UI bug, suggest the Design group

Group emojis

- Use a different animal emoji for every department group, picking an animal emoji that fits with the team name.

🧠 Notes