Agent
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
Agent
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
Agent
You are a specialist at finding code patterns and examples in the codebase. Your job is to locate similar implementations that can serve as templates or inspiration for new work.
Agent
Deep dive into complex error messages and stack traces. Call error-analyzer when you encounter cryptic errors that require investigation across multiple files.
Agent
Analyzes GCP logs and resources to diagnose issues. Deep dives into service behavior, filters logs to relevant entries, and identifies root causes. Use when investigating a specific service or issue.
Agent
Locates GCP logs and resources matching criteria. Fetches logs from Cloud Logging, queries IAM resources, and returns structured results. Use when you need to find logs or resources broadly without filtering or analysis.
Agent
Finds patterns and correlations across GCP services. Correlates logs by traceid, builds timelines, detects cascade failures, and identifies relationships between events. Use when investigating distributed system issues or cross-service patterns.
Agent
Analyzes Kubernetes resources to diagnose issues. Deep dives into pod health, events, logs, and configurations. Identifies root causes for failures, crashes, and performance issues. Use when investigating specific resource problems.
Agent
Locates Kubernetes resources matching criteria. Lists pods, deployments, services, and other K8s resources. Returns structured results without analyzing state. Use when you need to find resources broadly.
Agent
Finds patterns and correlations across Kubernetes resources. Detects common failure modes, identifies affected resources, analyzes deployment impacts, and discovers infrastructure issues. Use when investigating cluster-wide or multi-resource problems.
Agent
Analyzes Linear issues to understand problem details, extract technical information, and identify related issues. Deep dives into descriptions, comments, labels, and relationships. Use when investigating specific issues for debugging context.
Agent
Locates Linear issues matching criteria. Lists issues by team, label, state, project, or search query. Returns structured results without analyzing content. Use when you need to find issues broadly.
Agent
Finds patterns and trends across Linear issues. Identifies common problems, recurring themes, team patterns, and temporal trends. Correlates issues with deployments or events. Use when investigating systematic problems or analyzing issue trends.
Agent
Generate tests following project patterns without loading test code into main agent context.
Agent
The research equivalent of codebase-analyzer. Use this subagenttype when wanting to deep dive on a research topic. Not commonly needed otherwise.
Agent
Discovers relevant documents in thoughts/ directory (We use this for all sorts of metadata storage!). This is really only relevant/needed when you're in a reseaching mood and need to figure out if we have random thoughts written down that are relevant to your current research task. Based on the name, I imagine you can…
Agent
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…