Agents

Hyprlayer installs specialized sub-agents that are spawned by the main AI tool to handle specific tasks in parallel. These agents are used internally by commands like /research_codebase and /create_plan.

Available Agents

Codebase Agents

Agent	Purpose
codebase-locator	Finds files, directories, and components relevant to a feature or task. A “super grep/glob” tool.
codebase-analyzer	Analyzes implementation details of specific components. Deep-dives into how code works.
codebase-pattern-finder	Finds similar implementations, usage examples, or existing patterns to model after. Returns concrete code examples.

Research Agents

Agent	Purpose
web-search-researcher	Searches the web for information not available in the codebase. Useful for API docs, library usage, and modern techniques.
thoughts-locator	Discovers relevant documents in the thoughts/ directory. Finds existing research, plans, and context.
thoughts-analyzer	Deep-dives on research topics found in the thoughts directory.

Integration Agents

Agent	Purpose
jira-ticket-reader	Reads full details of a JIRA ticket including description, comments, and linked issues.
jira-searcher	Searches JIRA for tickets using JQL or text queries. Finds similar issues and historical context.

How Agents Are Used

You don’t invoke agents directly. They are spawned by commands when needed:

• /research_codebase spawns codebase-locator, codebase-analyzer, and codebase-pattern-finder in parallel to explore different aspects of the codebase
• /create_plan uses codebase-analyzer and thoughts-locator to research before planning
• /founder_mode uses jira-ticket-reader to create tickets

Agent Files

Agent definitions are installed alongside commands during hyprlayer ai configure. They live in the agents/ subdirectory of your AI tool’s configuration directory.