- File format
- JSON
- Discovery path
.kiro/agents- Syllago install method
- JSON merge
- Symlink support
- No
- Config file
.kiro/agents/- Handler types
command
Hook events
| Canonical Event | Native Name | Category |
|---|
after_task | Post Task Execution | Lifecycle |
after_tool_execute | postToolUse | Tool |
agent_stop | stop | Lifecycle |
before_prompt | userPromptSubmit | Lifecycle |
before_task | Pre Task Execution | Lifecycle |
before_tool_execute | preToolUse | Tool |
file_changed | File Save | Workspace |
file_created | File Create | Workspace |
file_deleted | File Delete | Workspace |
session_start | agentSpawn | Lifecycle |
Features
How each feature converts to syllago's canonical format. See format conversion for what these statuses mean.
Other features
Behaviors, conventions, and capabilities that aren't tied to a single named field — things like path-based activation, discovery rules, and lifecycle behavior.
| Feature | Conversion | Summary |
|---|
| Agent turn completion trigger | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Hook trigger that fires after each agent turn completes, enabling automated follow-up actions. |
| File operation triggers (save, create, delete) | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Hook triggers that fire on file save, file create, and file delete events within the IDE, enabling automated responses to file lifecycle changes. |
| Hooks configured via IDE UI only | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Kiro hooks are created either by describing desired functionality in natural language (Kiro generates the configuration) or by manually completing a form with title, description, event type, action type, and execution instructions. No documented file-based configuration format — configuration is not portable. |
| Manual on-demand hook trigger | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Hook trigger type that fires only on explicit user request, enabling on-demand automation without automatic event-based execution. |
| Predefined agent prompt as hook action | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Hook action type that runs a predefined agent prompt through the Kiro agent instead of a shell command. Configured via the IDE panel. |
| Spec task lifecycle triggers (before/after spec task execution) | Not portableConversion type: Not portableUnique to this provider — can’t be carried across providers.Learn more → | Triggers firing before and after spec task execution, tied to Kiro's spec/planning workflow. |