* feat(agents): implement category-based agent organization system - Organize agents into domain categories (core, development, content, data, product, learning) - Move 10 agents to category subdirectories with proper git rename tracking - Update 13 subagents with category and type metadata in frontmatter - Add category metadata files (0-category.json) documenting common patterns - Implement local registry fallback in install script for offline development - Add comprehensive validation suite with 15 automated tests (100% pass rate) - Enhance registry validation with duplicate ID and consistency checks - Update eval framework with intelligent path resolution (backward compatible) - Archive legacy eval structure to _archive/ for reference - Update all documentation to reflect category-based structure - Bump version to 0.5.0 with accurate CHANGELOG Technical Details: - 23 agents organized (10 category agents, 13 subagents) - 6 category directories created - Path resolution supports both agent IDs and category paths - Registry schema updated to v2.0.0 - 159 files changed, 872 insertions(+), 10738 deletions(-) BREAKING CHANGE: Agent file paths now use category structure. Update references from .opencode/agent/openagent.md to .opencode/agent/core/openagent.md. Eval framework maintains backward compatibility via path resolution. * refactor(evals): consolidate documentation and enhance test infrastructure - Remove temporary project tracking files (PHASE_5_COMPLETE, PROJECT_COMPLETE, etc.) - Consolidate evaluation framework docs into main README - Enhance test execution with improved logging and multi-prompt support - Move system-builder from core to meta category - Add comprehensive test suites for openagent with organized structure - Create evaluation test structure for all subagents - Clean up archived workflows and redundant documentation - Update registry to reflect new agent organization - Add shared test templates and golden test patterns * feat(ci): add manual trigger support for bot-created PRs in validate-registry workflow - Add pr_number input to workflow_dispatch for manually triggering validation - Fetch PR details dynamically when triggered manually - Support both automatic (PR event) and manual (workflow_dispatch) triggers - Enable validation of bot-created PRs like automated version bumps - Update branch detection and push logic to handle both trigger types - Add documentation explaining how to manually trigger for bot PRs * feat(evals): add explicit context file validation to test framework - Add expectedContextFiles field to test YAML schema for explicit context file specification - Enhance context-loading-evaluator to support both auto-detect and explicit validation modes - Update documentation with comprehensive guide and examples - Clean up archived legacy test structure (90+ old test files) - Add new example tests demonstrating explicit context validation - Backward compatible with existing tests * feat(evals): add multi-agent logging system and performance optimizations Implement comprehensive multi-agent logging and performance improvements for the eval framework. Task 01: Multi-Agent Logging System - Add complete hierarchical logging module (evals/framework/src/logging/) - SessionTracker: tracks parent-child delegation hierarchies - MultiAgentLogger: pretty-prints logs with visual indentation - Formatters: box characters and emoji formatting - 37 passing unit tests (session-tracker, logger, integration) - Integrate with SDK event stream handler - Hook into session.created, message.updated, message.part.updated events - Real-time child session detection via timestamp heuristics - Message deduplication for cleaner output - Enable in debug mode only (<1% performance overhead) - Add demo script and comprehensive documentation Task 02: Performance Optimizations - Reduce grace period from 5s to 2s (67% reduction, 10-20% faster tests) - Add PerformanceMetricsEvaluator for bottleneck identification - Collects tool latencies, inference time, idle time - Provides full performance visibility - Update smoke test to validate delegation (core feature) - Replace simple read test with multi-agent delegation test - Tests both parent and child agent functionality - Validates multi-agent logging system Results: - 37 unit tests passing - Smoke test passing (95/100 score) - Clean hierarchical logging output - 10-20% faster test execution - Full multi-agent visibility Files changed: 16 files, +2678 lines Time saved: ~6-8 days (completed in 6 hours vs 3-5 day estimate) * feat(evals): show child agent execution in non-debug mode - Enable MultiAgentLogger in both debug and non-debug modes - Add verbose parameter to control output level - Non-verbose mode shows concise child session lifecycle: - Child agent started message - Child agent completed with duration - Verbose mode (--debug) shows full delegation hierarchy - Update documentation to reflect new behavior This provides visibility into delegation without overwhelming output, giving confidence that child agents are actually running. * feat(evals): improve delegation testing and behavior validation Major improvements to eval framework: Test Suite: - Add 00-smoke-test.yaml (basic read operation) - Rename 01-smoke-test.yaml → 02-delegation-test.yaml (delegation test) - Add simple-responder test agent for delegation testing - Add debug test: simple-subagent-call.yaml Evaluators: - Add agent-model-evaluator.ts for agent/model validation - Enhance behavior-evaluator.ts with detailed task tool output - Improve delegation-evaluator.ts with better evidence tracking Schema & Execution: - Add expectedAgent and expectedModel to test schema - Improve test executor with better logging and error handling Documentation: - Update evals/README.md with new features and performance improvements - Remove outdated MULTI_AGENT_LOGGING_COMPLETE.md Registry: - Add simple-responder test agent to registry Fixes: - Fix dashboard.sh path resolution These changes provide better visibility into delegation, improved test coverage, and clearer validation of agent behavior. * chore: add GitHub Actions workflow and plugin documentation - Add .github/workflows/evals/run-evaluations.yml for automated eval testing - Add dev/ai-tools/opencode/plugins/Plugin-inspiration.md for plugin development reference
8.1 KiB
8.1 KiB
Agent Evaluation Framework
Test and validate agent behavior with automated evaluations.
Quick Start
cd evals/framework
# Run golden tests (baseline - 8 tests, ~2-3 min)
npm run eval:sdk -- --agent=openagent --pattern="**/golden/*.yaml"
# Run a specific test
npm run eval:sdk -- --agent=openagent --pattern="**/smoke-test.yaml"
# Run with debug output (includes multi-agent logging)
npm run eval:sdk -- --agent=openagent --pattern="**/golden/*.yaml" --debug
✨ New Features
Multi-Agent Logging (Dec 2025)
Beautiful hierarchical logging shows parent-child delegation chains:
┌────────────────────────────────────────────────────────────┐
│ 🎯 PARENT: OpenAgent (ses_xxx...) │
└────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────┐
│ 🎯 CHILD: simple-responder (ses_yyy...) │
│ Parent: ses_xxx... │
│ Depth: 1 │
└────────────────────────────────────────────────────────────┘
✅ CHILD COMPLETE (2.9s)
✅ PARENT COMPLETE (20.9s)
Enable with --debug flag. See MULTI_AGENT_LOGGING_COMPLETE.md for details.
Performance Improvements (Dec 2025)
- 10-20% faster tests - Grace period reduced from 5s to 2s
- Performance metrics - Automatic collection of tool latencies, inference time
- 37 unit tests - Complete test coverage for logging system
Golden Tests
8 curated tests that validate core agent behaviors:
| Test | What It Validates |
|---|---|
| 01-smoke-test | Agent & subagent delegation (multi-agent) |
| 02-context-loading | Agent reads context before answering |
| 03-read-before-write | Agent inspects before modifying |
| 04-write-with-approval | Agent asks before writing |
| 05-multi-turn-context | Agent remembers conversation |
| 06-task-breakdown | Agent reads standards before implementing |
| 07-tool-selection | Agent uses dedicated tools (not bash) |
| 08-error-handling | Agent handles errors gracefully |
# Run all golden tests
npm run eval:sdk -- --agent=openagent --pattern="**/golden/*.yaml"
Creating Custom Tests
See CREATING_TESTS.md for:
- Test templates (copy and modify)
- Behavior options (mustUseTools, requiresApproval, etc.)
- NEW:
expectedContextFiles- Explicitly specify which context files to validate - Expected violations
- Examples
New Feature: Explicit Context File Validation
You can now explicitly specify which context files the agent must read:
behavior:
requiresContext: true
expectedContextFiles:
- .opencode/context/core/standards/code.md
- standards/code.md
See agents/shared/tests/EXPLICIT_CONTEXT_FILES.md for detailed guide.
Quick example:
id: my-test
name: "My Test"
description: What this tests.
category: developer
prompts:
- text: Read evals/test_tmp/README.md and summarize it.
approvalStrategy:
type: auto-approve
behavior:
mustUseTools: [read]
expectedViolations:
- rule: approval-gate
shouldViolate: false
severity: error
timeout: 60000
Evaluators
| Evaluator | What It Checks |
|---|---|
| approval-gate | Approval requested before risky operations |
| context-loading | Context files loaded before acting (supports explicit file specification) |
| execution-balance | Read operations before write operations |
| tool-usage | Dedicated tools used instead of bash |
| behavior | Expected tools used, forbidden tools avoided |
| delegation | Complex tasks delegated to subagents |
| stop-on-failure | Agent stops on errors instead of auto-fixing |
Directory Structure
evals/
├── README.md # This file
├── CREATING_TESTS.md # How to create custom tests
├── framework/ # Test runner and evaluators
│ ├── src/
│ │ ├── sdk/ # Test execution
│ │ └── evaluators/ # Rule validators
│ └── README.md # Technical details
├── agents/
│ ├── shared/tests/
│ │ ├── golden/ # 8 baseline tests
│ │ └── templates/ # Test templates
│ └── core/openagent/tests/ # Agent-specific tests
├── results/ # Test results
│ ├── latest.json
│ └── index.html # Dashboard
└── test_tmp/ # Temp files (auto-cleaned)
CLI Options
npm run eval:sdk -- [options]
Options:
--agent=NAME Agent to test (openagent, opencoder, core/openagent)
--subagent=NAME Test a subagent (coder-agent, tester, reviewer, etc.)
Default: Standalone mode (forces mode: primary)
--delegate Test subagent via parent delegation (requires --subagent)
--pattern=GLOB Test file pattern (default: **/*.yaml)
--debug Enable debug output, keep sessions for inspection
--verbose Show full conversation (prompts + responses) after each test
(automatically enables --debug)
--model=PROVIDER/MODEL Override model (default: opencode/grok-code-fast)
--timeout=MS Test timeout (default: 60000)
--prompt-variant=NAME Use specific prompt variant (gpt, gemini, grok, llama)
Auto-detects recommended model from prompt metadata
--no-evaluators Skip running evaluators (faster iteration)
--core Run core test suite only (7 tests, ~5-8 min)
Examples
# Run golden tests with verbose output (see full conversations)
npm run eval:sdk -- --agent=openagent --pattern="**/golden/*.yaml" --verbose
# Test subagent standalone (forces mode: primary)
npm run eval:sdk -- --subagent=coder-agent
# Test subagent via delegation (uses parent agent)
npm run eval:sdk -- --subagent=coder-agent --delegate
# Test with a specific model
npm run eval:sdk -- --agent=openagent --model=anthropic/claude-3-5-sonnet-20241022
# Test with a prompt variant (auto-detects model)
npm run eval:sdk -- --agent=openagent --prompt-variant=llama
# Quick iteration without evaluators
npm run eval:sdk -- --agent=openagent --pattern="**/01-smoke-test.yaml" --no-evaluators
Quick Commands (Makefile)
From the project root, you can use these shortcuts:
# Full pipeline: build, validate, run golden tests
make test-evals
# Just run golden tests (8 tests, ~3-5 min)
make test-golden
# Quick smoke test (1 test, ~30s)
make test-smoke
# Run with verbose output (see full conversations)
make test-verbose
# Test specific agent
make test-agent AGENT=opencoder
# Test subagent (standalone mode)
make test-subagent SUBAGENT=coder-agent
# Test subagent (delegation mode)
make test-subagent-delegate SUBAGENT=coder-agent
# Test with specific model
make test-model MODEL=anthropic/claude-3-5-sonnet-20241022
# Test with prompt variant
make test-variant VARIANT=llama
# View results
make view-results # Open dashboard in browser
make show-results # Show summary in terminal
For detailed subagent testing guide, see SUBAGENT_TESTING.md
Results
Results are saved to evals/results/:
latest.json- Most recent runhistory/- Historical results (by month)index.html- Dashboard (open in browser)
# View dashboard
make view-results
# Or manually:
cd evals/results && python -m http.server 8080
# Open http://localhost:8080