All notable changes to this project will be documented in this file.
- feat: Context path configuration and documentation reorganization (#143)
- feat: add ExternalScout and optimize ContextScout with research-backed patterns (#128)
- Updated README.md and QUICK_START.md for v0.6.0 accuracy
- Updated version from 0.1.0-alpha.1 to 0.6.0
- Simplified agent architecture (OpenAgent + OpenCoder)
- Completed commands list with /analyze-patterns, /commit-openagents, /build-context-system
- Highlighted ExternalScout with 18+ supported libraries
- Updated installation profiles to mention new agents
-
ExternalScout Subagent: New subagent for fetching live, version-specific documentation for external libraries via Context7 API
- Supports 18+ libraries: Drizzle, Better Auth, Next.js, TanStack, Cloudflare Workers, AWS Lambda, and more
- Lazy-loads query patterns for specific libraries only
- Filters and formats results by relevance
- Fallback to official docs via webfetch
- Added to registry with
skill:context7dependency
-
Context7 Skill: Registered in system for external documentation fetching
- Path:
.opencode/skills/context7/SKILL.md - Library registry:
.opencode/skills/context7/library-registry.md - Navigation guide:
.opencode/skills/context7/navigation.md
- Path:
-
ContextScout v5.1.0: Optimized with research-backed prompt engineering patterns
- Critical rules moved to first 15% of prompt (position sensitivity)
- Added 3-tier execution priority system
- 20% token reduction via visual operators (→, |, @refs)
- Simplified XML structure (4% XML vs 40%) for multi-model compatibility (Claude, Gemini, GPT-4)
- Added external library detection and ExternalScout recommendation
- Added dependency:
subagent:externalscout - 100% behavior preservation
-
ExternalScout v2.0.0: Optimized with research-backed prompt engineering patterns
- 42% token reduction via visual operators and inline mappings
- Critical rules moved to first 15% of prompt
- Added 3-tier execution priority system
- Added references to prompt engineering docs and context system
- Enhanced workflow structure with checkpoints
- Added dependencies:
context:prompt-engineering,context:context-system - 100% behavior preservation
-
Registry Updates:
- Updated ContextScout description to mention multi-model optimization
- Updated ExternalScout description to mention token reduction
- Added version numbers to both subagents
- Added "optimized" tag to both subagents
- Added
.tmp/contextscout-optimization-analysis.md- Detailed optimization metrics - Added
.tmp/contextscout-simplification-analysis.md- Multi-model compatibility analysis - Added
.tmp/externalscout-optimization-analysis.md- Token reduction analysis
- Created
.opencode/agent/subagents/core/contextscout-v4-backup.md- Original v4.0.0 - Created
.opencode/agent/subagents/core/externalscout-v1-backup.md- Original v1.0.0
- fix(registry): add component-planning context and remove repo-specific contexts from user profiles (#125)
- docs: fix agent name casing in documentation (#117)
- fix: make admin bypass work properly for bot PRs (#113)
- docs(core): refine project intelligence system and deprecate legacy context (#93)
- refactor(evals): consolidate documentation and enhance test infrastructure (#56)
- Explicit Context File Validation: New
expectedContextFilesfield in test YAML files allows explicit specification of which context files the agent must read- Overrides auto-detection when specified
- Uses flexible pattern matching (
includes()orendsWith()) - Supports partial paths (e.g.,
standards/code.md) or full paths - See
evals/agents/shared/tests/EXPLICIT_CONTEXT_FILES.mdfor detailed guide - Example test:
evals/agents/shared/tests/golden/02-context-loading-explicit.yaml
- Context Loading Evaluator: Now accepts optional
BehaviorExpectationconfig to support explicit file validation- Shows detection mode in evidence: "Explicit (from YAML test)" or "Auto-detect (from user message)"
- Backward compatible - existing tests work unchanged
- Added
evals/agents/shared/tests/EXPLICIT_CONTEXT_FILES.md- Complete feature guide - Added
evals/PATTERN_MATCHING_GUIDE.md- Pattern matching reference - Updated
evals/CREATING_TESTS.md- AddedexpectedContextFilesdocumentation - Updated
evals/README.md- Added new feature section
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Category-Based Agent Organization: Agents now organized by domain in subdirectories
core/- Core system agents (openagent, opencoder)meta/- Meta-level agents (system-builder)development/- Development specialists (frontend-specialist, backend-specialist, devops-specialist, codebase-agent)content/- Content creation agents (copywriter, technical-writer)data/- Data and analysis agents (data-analyst)product/- Product management agents (directory created, ready for agents)learning/- Education and coaching agents (directory created, ready for agents)
- Category Metadata Files: Each category has
0-category.jsondocumenting common subagents, tools, and context - Subagent Organization: 13 subagents organized into 4 categories (code, core, system-builder, utils)
- Local Registry Fallback: Install script now supports local
registry.jsonfor development/testing - Enhanced Registry Validation: Added checks for duplicate IDs and category consistency
- Comprehensive Test Suite: 15 automated validation tests for category system
- Audit Tools: Scripts to verify migration completeness and system integrity
- Agent File Structure: Agents moved from flat structure to category-based organization
- Example:
.opencode/agent/openagent.md→.opencode/agent/core/openagent.md - Example:
.opencode/agent/opencoder.md→.opencode/agent/core/opencoder.md
- Example:
- Registry Schema: Updated to include category-based paths for all agents
- Eval Framework: Enhanced with path resolution supporting both agent IDs and category paths
--agent=openagentresolves tocore/openagent(backward compatible)--agent=core/openagentworks directly (new format)
- Documentation: Updated all docs to reference category-based structure
- Install Script: Enhanced with local registry fallback for offline/development use
- Frontend Specialist: Renamed
frontend-design-agent.mdtofrontend-specialist.mdfor consistency - Eval Directory Structure: Archived legacy flat eval structure to
_archive/for clarity - Registry Validation: Fixed validation script to handle category-based paths correctly
- Backward Compatibility: Agent IDs like
openagentstill work via path resolution - Local Testing: No need to push to GitHub to test registry changes
- Clear Organization: Agents grouped by domain make discovery easier
- Validation Tools: Automated tests ensure system integrity
- Agent Paths: Update references from flat to category-based paths
- Old:
.opencode/agent/openagent.md - New:
.opencode/agent/core/openagent.md
- Old:
- Eval Framework: Both formats work due to path resolution
--agent=openagent(backward compatible)--agent=core/openagent(new format)
- No Breaking Changes: Path resolution maintains backward compatibility
- Files Modified: 14+ files updated for category structure
- Agents Organized: 23 total agents (10 category agents, 13 subagents)
- Test Coverage: 15/15 validation tests passing (100%)
- Audit Status: 8/8 checks passing (100%)
- CI: Check only commit title for skip patterns (#46)
- New
ExecutionBalanceEvaluatorinevals/frameworkto assess read vs execution ordering and ratio - Contributor guide:
docs/contributing/ADDING_EVALUATOR.mddescribing evaluator design principles - Test cases under
evals/agents/openagent/tests/10-execution-balance/(positive & negative scenarios)
- Framework README updated with section documenting
ExecutionBalanceEvaluatorand violation codes
- Install Script Non-Interactive Bug: Fixed critical bug where
curl | bash -s <profile>would fail with "Installation cancelled by user" when existing files were present- Root cause: Collision handling prompted for user input even in non-interactive mode
- Solution: Auto-detect non-interactive mode and use "skip" strategy by default
- Installer CI Workflow: New
.github/workflows/installer-checks.ymlruns on install.sh changes- ShellCheck static analysis
- Bash syntax validation
- Non-interactive mode tests
- End-to-end installation tests
- Profile smoke tests on Ubuntu and macOS
- Non-Interactive Tests: New
scripts/tests/test-non-interactive.shvalidates piped execution - E2E Installation Tests: New
scripts/tests/test-e2e-install.shvalidates full installation workflow
- Updated
scripts/tests/README.mdwith new test documentation
- Explicit Context File Validation: New
expectedContextFilesfield in test YAML files- Overrides auto-detection when specified
- Uses flexible pattern matching (
includes()orendsWith()) - Supports partial paths (e.g.,
standards/code.md) or full paths
- Context Loading Evaluator: Now accepts optional
BehaviorExpectationconfig- Shows detection mode in evidence: "Explicit (from YAML test)" or "Auto-detect (from user message)"
- Backward compatible - existing tests work unchanged
- Added
evals/agents/shared/tests/EXPLICIT_CONTEXT_FILES.md- Complete feature guide - Added
evals/PATTERN_MATCHING_GUIDE.md- Pattern matching reference - Updated
evals/CREATING_TESTS.mdandevals/README.md
- Category-Based Agent Organization: Agents now organized by domain in subdirectories
core/- Core system agents (openagent, opencoder)meta/- Meta-level agents (system-builder)development/- Development specialists (frontend-specialist, backend-specialist, devops-specialist, codebase-agent)content/- Content creation agents (copywriter, technical-writer)data/- Data and analysis agents (data-analyst)product/- Product management agents (directory created, ready for agents)learning/- Education and coaching agents (directory created, ready for agents)
- Category Metadata Files: Each category has
0-category.jsondocumenting common subagents, tools, and context - Subagent Organization: 13 subagents organized into 4 categories (code, core, system-builder, utils)
- Local Registry Fallback: Install script now supports local
registry.jsonfor development/testing - Enhanced Registry Validation: Added checks for duplicate IDs and category consistency
- Comprehensive Test Suite: 15 automated validation tests for category system
- Audit Tools: Scripts to verify migration completeness and system integrity
- Agent File Structure: Agents moved from flat structure to category-based organization
- Example:
.opencode/agent/openagent.md→.opencode/agent/core/openagent.md - Example:
.opencode/agent/opencoder.md→.opencode/agent/core/opencoder.md
- Example:
- Registry Schema: Updated to include category-based paths for all agents
- Eval Framework: Enhanced with path resolution supporting both agent IDs and category paths
--agent=openagentresolves tocore/openagent(backward compatible)--agent=core/openagentworks directly (new format)
- Documentation: Updated all docs to reference category-based structure
- Install Script: Enhanced with local registry fallback for offline/development use
- Frontend Specialist: Renamed
frontend-design-agent.mdtofrontend-specialist.mdfor consistency - Eval Directory Structure: Archived legacy flat eval structure to
_archive/for clarity - Registry Validation: Fixed validation script to handle category-based paths correctly
- Backward Compatibility: Agent IDs like
openagentstill work via path resolution - Local Testing: No need to push to GitHub to test registry changes
- Clear Organization: Agents grouped by domain make discovery easier
- Validation Tools: Automated tests ensure system integrity
- Agent Paths: Update references from flat to category-based paths
- Old:
.opencode/agent/openagent.md - New:
.opencode/agent/core/openagent.md
- Old:
- Eval Framework: Both formats work due to path resolution
--agent=openagent(backward compatible)--agent=core/openagent(new format)
- No Breaking Changes: Path resolution maintains backward compatibility
- Files Modified: 14+ files updated for category structure
- Agents Organized: 23 total agents (10 category agents, 13 subagents)
- Test Coverage: 15/15 validation tests passing (100%)
- Audit Status: 8/8 checks passing (100%)
- CI: Check only commit title for skip patterns (#46)
- New
ExecutionBalanceEvaluatorinevals/frameworkto assess read vs execution ordering and ratio - Contributor guide:
docs/contributing/ADDING_EVALUATOR.mddescribing evaluator design principles - Test cases under
evals/agents/openagent/tests/10-execution-balance/(positive & negative scenarios)
- Framework README updated with section documenting
ExecutionBalanceEvaluatorand violation codes
v0.X.Y
│ │ │
│ │ └─ Patch version (bug fixes, minor changes)
│ └─── Minor version (new features, non-breaking changes)
└───── Major version (breaking changes, major milestones)
- 0.5.1 - Install script bug fix, CI improvements for installer
- 0.5.0 - Explicit context file validation in evals
- 0.4.0 - Category-based agent organization system
- 0.3.1 - CI improvements
- 0.0.2 - Execution balance evaluator