Tags are colored labels that you assign to agents for visual organization. They appear in the agents list and when viewing an individual agent, letting you scan your workspace at a glance and understand each agent’s status or category without opening it.
Each agent can have one tag at a time. Tags are managed at the project level, so all members of a project share the same set of tags.
When a new project is created, three tags are automatically added:
| Tag | Suggested use |
|---|
| Draft | Agents under initial development |
| Editing | Agents being revised or refined |
| In production | Agents actively running in live workflows |
- Go to Settings in the left-side pane of the dashboard.
- Select Tags under your project settings.
- Click Create tag.
- Enter a name and choose a color.
- Click Save.
The new tag is immediately available to assign to any agent in the project.
Editing a tag
- Go to Settings > Tags.
- Click the edit icon next to the tag you want to change.
- Update the name, color, or both.
- Click Save.
Changes apply immediately — agents already using that tag will display the updated name and color.
Deleting a tag
- Go to Settings > Tags.
- Click the delete icon next to the tag.
- Confirm the deletion.
Deleting a tag removes it from all agents it was assigned to. Those agents will no longer have a tag until you assign a new one.
Assigning or changing a tag
- Open the agent you want to tag from your agents list.
- Click the tag selector in the agent header or use the context menu in the agents list.
- Select a tag from the dropdown.
The tag is applied immediately and visible in the agents list.
Removing a tag from an agent
- Open the agent or access its context menu in the agents list.
- Click the tag selector and choose No tag (or the clear option).
Best practices
Use tags to reflect lifecycle stage. The default “Draft”, “Editing”, “In production” tags work well for most teams — agents move through stages as they’re built, tested, and deployed.
Combine tags with folders. Folders group agents by function or team; tags indicate status within those groups. For example, a “Sales” folder might contain agents tagged “Draft”, “In production”, or “Editing” at any given time.
Keep tag sets small. A short list of clearly defined tags is easier to apply consistently than a long list with overlapping meanings. Aim for five or fewer tags per project.
Establish team conventions. Agree with your team on what each tag means before creating agents, so tags stay meaningful as the project grows.
To see all agents with a specific tag, filter the agents list by tag name.
