Host · Agents
Agents — Small Task Units, Handled Autonomously
If a plugin is an entire domain, an Agent is a single task. It's a small autonomous unit built to do one thing well — like 'create a weekly retro' or 'summarize today's action items.' The host calls these Agents through shortcuts, Hub messages, or automation triggers.
How is this different from a plugin?
Plugin
Agent
How does an Agent get started?
- 01
Shortcut / command palette
Search directly for the Agent's name in the host's command palette. The most common way to call one.
- 02
Delegate via an Agent Hub message
From the work board, choose "hand this task to this Agent" → the Agent produces the result in the background and returns it as a message.
- 03
Automation trigger
Also started by automation rules such as "automatically run the meeting-notes Agent when a meeting ends."
Where is it stored?
An installed Agent is kept as a single text file in the LVIS area on the user's PC. It contains its own behavior, its calling keywords, and the user group that can call it. It is never sent to an external server.