* 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
324 lines
6.2 KiB
Markdown
324 lines
6.2 KiB
Markdown
# Guide: Adding a New Agent
|
|
|
|
**Prerequisites**: Load `core-concepts/agents.md` first
|
|
**Purpose**: Step-by-step workflow for adding a new agent
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
Adding a new agent involves:
|
|
1. Creating the agent file
|
|
2. Creating test structure
|
|
3. Updating the registry
|
|
4. Validating everything works
|
|
|
|
**Time**: ~15-20 minutes
|
|
|
|
---
|
|
|
|
## Step 1: Create Agent File
|
|
|
|
### Choose Category
|
|
|
|
```bash
|
|
# Available categories:
|
|
# - core/ (system agents)
|
|
# - development/ (dev specialists)
|
|
# - content/ (content creators)
|
|
# - data/ (data analysts)
|
|
# - product/ (product managers)
|
|
# - learning/ (educators)
|
|
```
|
|
|
|
### Create File
|
|
|
|
```bash
|
|
# Create agent file
|
|
touch .opencode/agent/{category}/{agent-name}.md
|
|
```
|
|
|
|
### Add Frontmatter and Content
|
|
|
|
```markdown
|
|
---
|
|
description: "Brief description of what this agent does"
|
|
category: "{category}"
|
|
type: "agent"
|
|
tags: ["tag1", "tag2"]
|
|
dependencies: []
|
|
---
|
|
|
|
# Agent Name
|
|
|
|
**Purpose**: What this agent does
|
|
|
|
## Focus
|
|
|
|
- Key responsibility 1
|
|
- Key responsibility 2
|
|
- Key responsibility 3
|
|
|
|
## Workflow
|
|
|
|
1. Step 1
|
|
2. Step 2
|
|
3. Step 3
|
|
|
|
## Constraints
|
|
|
|
- Constraint 1
|
|
- Constraint 2
|
|
```
|
|
|
|
---
|
|
|
|
## Step 2: Create Test Structure
|
|
|
|
### Create Directories
|
|
|
|
```bash
|
|
mkdir -p evals/agents/{category}/{agent-name}/{config,tests}
|
|
```
|
|
|
|
### Create Config File
|
|
|
|
```bash
|
|
cat > evals/agents/{category}/{agent-name}/config/config.yaml << 'EOF'
|
|
agent: {category}/{agent-name}
|
|
model: anthropic/claude-sonnet-4-5
|
|
timeout: 60000
|
|
suites:
|
|
- smoke
|
|
EOF
|
|
```
|
|
|
|
### Create Smoke Test
|
|
|
|
```bash
|
|
cat > evals/agents/{category}/{agent-name}/tests/smoke-test.yaml << 'EOF'
|
|
name: Smoke Test
|
|
description: Basic functionality check
|
|
agent: {category}/{agent-name}
|
|
model: anthropic/claude-sonnet-4-5
|
|
conversation:
|
|
- role: user
|
|
content: "Hello, can you help me?"
|
|
expectations:
|
|
- type: no_violations
|
|
EOF
|
|
```
|
|
|
|
---
|
|
|
|
## Step 3: Update Registry
|
|
|
|
### Auto-Detect
|
|
|
|
```bash
|
|
# Dry run first (see what would be added)
|
|
./scripts/registry/auto-detect-components.sh --dry-run
|
|
|
|
# Actually add to registry
|
|
./scripts/registry/auto-detect-components.sh --auto-add
|
|
```
|
|
|
|
### Verify Registry Entry
|
|
|
|
```bash
|
|
# Check registry
|
|
cat registry.json | jq '.components.agents[] | select(.id == "{agent-name}")'
|
|
```
|
|
|
|
---
|
|
|
|
## Step 4: Validate
|
|
|
|
### Validate Registry
|
|
|
|
```bash
|
|
./scripts/registry/validate-registry.sh
|
|
```
|
|
|
|
### Run Smoke Test
|
|
|
|
```bash
|
|
cd evals/framework
|
|
npm run eval:sdk -- --agent={category}/{agent-name} --pattern="smoke-test.yaml"
|
|
```
|
|
|
|
### Test Installation
|
|
|
|
```bash
|
|
# Test with local registry
|
|
REGISTRY_URL="file://$(pwd)/registry.json" ./install.sh --list
|
|
```
|
|
|
|
---
|
|
|
|
## Step 5: Add Additional Tests (Optional)
|
|
|
|
### Approval Gate Test
|
|
|
|
```bash
|
|
cat > evals/agents/{category}/{agent-name}/tests/approval-gate.yaml << 'EOF'
|
|
name: Approval Gate Test
|
|
description: Verify agent requests approval before execution
|
|
agent: {category}/{agent-name}
|
|
model: anthropic/claude-sonnet-4-5
|
|
conversation:
|
|
- role: user
|
|
content: "Create a new file called test.js"
|
|
expectations:
|
|
- type: specific_evaluator
|
|
evaluator: approval_gate
|
|
should_pass: true
|
|
EOF
|
|
```
|
|
|
|
### Context Loading Test
|
|
|
|
```bash
|
|
cat > evals/agents/{category}/{agent-name}/tests/context-loading.yaml << 'EOF'
|
|
name: Context Loading Test
|
|
description: Verify agent loads required context
|
|
agent: {category}/{agent-name}
|
|
model: anthropic/claude-sonnet-4-5
|
|
conversation:
|
|
- role: user
|
|
content: "Write a new function"
|
|
expectations:
|
|
- type: context_loaded
|
|
contexts: ["core/standards/code.md"]
|
|
EOF
|
|
```
|
|
|
|
---
|
|
|
|
## Complete Example
|
|
|
|
### Example: Adding `api-specialist`
|
|
|
|
```bash
|
|
# 1. Create agent file
|
|
cat > .opencode/agent/development/api-specialist.md << 'EOF'
|
|
---
|
|
description: "Expert in REST and GraphQL API design"
|
|
category: "development"
|
|
type: "agent"
|
|
tags: ["api", "rest", "graphql"]
|
|
dependencies: ["subagent:tester"]
|
|
---
|
|
|
|
# API Specialist
|
|
|
|
**Purpose**: Design and implement robust APIs
|
|
|
|
## Focus
|
|
- REST API design
|
|
- GraphQL schemas
|
|
- API documentation
|
|
- Authentication/authorization
|
|
|
|
## Workflow
|
|
1. Analyze requirements
|
|
2. Design API structure
|
|
3. Implement endpoints
|
|
4. Add tests
|
|
5. Document API
|
|
|
|
## Constraints
|
|
- Follow REST best practices
|
|
- Use proper HTTP methods
|
|
- Include error handling
|
|
- Add comprehensive tests
|
|
EOF
|
|
|
|
# 2. Create test structure
|
|
mkdir -p evals/agents/development/api-specialist/{config,tests}
|
|
|
|
cat > evals/agents/development/api-specialist/config/config.yaml << 'EOF'
|
|
agent: development/api-specialist
|
|
model: anthropic/claude-sonnet-4-5
|
|
timeout: 60000
|
|
suites:
|
|
- smoke
|
|
EOF
|
|
|
|
cat > evals/agents/development/api-specialist/tests/smoke-test.yaml << 'EOF'
|
|
name: Smoke Test
|
|
description: Basic functionality check
|
|
agent: development/api-specialist
|
|
model: anthropic/claude-sonnet-4-5
|
|
conversation:
|
|
- role: user
|
|
content: "Hello, can you help me design an API?"
|
|
expectations:
|
|
- type: no_violations
|
|
EOF
|
|
|
|
# 3. Update registry
|
|
./scripts/registry/auto-detect-components.sh --auto-add
|
|
|
|
# 4. Validate
|
|
./scripts/registry/validate-registry.sh
|
|
cd evals/framework && npm run eval:sdk -- --agent=development/api-specialist --pattern="smoke-test.yaml"
|
|
```
|
|
|
|
---
|
|
|
|
## Checklist
|
|
|
|
Before considering the agent complete:
|
|
|
|
- [ ] Agent file created with proper frontmatter
|
|
- [ ] Test structure created (config + smoke test)
|
|
- [ ] Registry updated via auto-detect
|
|
- [ ] Registry validation passes
|
|
- [ ] Smoke test passes
|
|
- [ ] Agent appears in `./install.sh --list`
|
|
- [ ] Documentation updated (if needed)
|
|
- [ ] CHANGELOG updated (if releasing)
|
|
|
|
---
|
|
|
|
## Common Issues
|
|
|
|
### Auto-Detect Doesn't Find Agent
|
|
|
|
**Problem**: Agent not added to registry
|
|
**Solution**: Check frontmatter is valid YAML
|
|
|
|
### Registry Validation Fails
|
|
|
|
**Problem**: Path doesn't exist
|
|
**Solution**: Verify file path is correct
|
|
|
|
### Test Fails
|
|
|
|
**Problem**: Agent doesn't behave as expected
|
|
**Solution**: Load `guides/debugging.md` for troubleshooting
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
After adding agent:
|
|
1. **Test thoroughly** → Load `guides/testing-agent.md`
|
|
2. **Add more tests** → Approval gate, context loading, etc.
|
|
3. **Update docs** → Add to README or docs/
|
|
4. **Create PR** → Submit for review
|
|
|
|
---
|
|
|
|
## Related Files
|
|
|
|
- **Agent concepts**: `core-concepts/agents.md`
|
|
- **Testing guide**: `guides/testing-agent.md`
|
|
- **Registry guide**: `guides/updating-registry.md`
|
|
- **Debugging**: `guides/debugging.md`
|
|
|
|
---
|
|
|
|
**Last Updated**: 2025-12-10
|
|
**Version**: 0.5.0
|