Use this agent when you need to understand or follow project-specific development guidelines, coding standards, or workflow instructions that are documented in the docs/ai directory. This agent should be consulted before starting any development work, when uncertain about project conventions, or when you need…
Agent tracing captures request timing, token counts, worker placement, finish metadata, and replay hashes for eligible LLM requests. Requests with session identity also carry agent context, which lets analysis tools group LLM turns and tool activity into the same run.
Agent "thunderagent-program-scheduler" from ai-dynamo/dynamo, covering the problem, the scheduler, scheduler tick, tool-boundary pause/resume semantics and program lifetime.
Use when reviewing changes to any .proto file under rpc/ or to the Go bindings generated from them. Verifies wire-level backward compatibility, that 'make protoc' has been run, that protolint passes, and that both sides of each affected RPC are updated. Surfaces incompatibilities that would break older clients, older…
The Agent Starter Pack follows a "bring your own agent" approach. It provides several production-ready agent templates designed to accelerate your development while offering the flexibility to use your preferred agent framework or pattern.
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
Use this agent when the user needs to write, modify, or debug driver tests for RivetKit. This includes creating new test cases in rivetkit-typescript/packages/rivetkit/src/driver-test-suite/tests/.ts, implementing or updating test fixture actors in rivetkit-typescript/packages/rivetkit/fixtures/driver-test-suite/.ts…
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
Expert on cluster launching and resource scheduling (Slurm/Ray/Kubernetes). Use when user modifies launcher/scheduler code, configures cluster resources, or troubleshoots deployment issues.
Agents emit structured events for every significant operation — RPC calls, state changes, schedule execution, workflow transitions, MCP connections, and more. These events are published to diagnostics channels and are silent by default (zero overhead when nobody is listening).
Use when: updating docs, cross-linking documents, enforcing doc quality standards, detecting stale references, keeping AGENTS.md in sync with code. Documenter — single source of documentation quality.
Use when: implementing features, building new capabilities, writing feature code, creating feature PRs. Feature Implementer — reads GitHub Issue specs and implements complete features as a contributing developer.