You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add Perplexity AI provider support
* refactor: update perplexity agents to use frontmatter config with temperature
* feat: enhance Perplexity AI agents with detailed descriptions and improved functionality
* feat: create enhanced CI/CD workflow combining best features from existing workflows
- Add concurrency controls to prevent overlapping runs
- Implement least privilege permissions for security
- Include auto-fix capabilities for formatting and clippy issues
- Integrate comprehensive security scanning (cargo audit, deny, secrets detection)
- Add performance benchmarking with hyperfine
- Maintain cross-platform testing with incremental builds
- Enforce 82%+ coverage threshold
- Provide detailed status summaries with modern GitHub Actions features
- Update README to document the enhanced workflow
This workflow replaces ci.yml and optimized-ci.yml with a more efficient and secure design.
Copy file name to clipboardExpand all lines: .opencode/agent/agent-coordinator.md
+101-1Lines changed: 101 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -361,7 +361,7 @@ For example:
361
361
</commentary>
362
362
</example>
363
363
364
-
- **hive-mind-orchestrator**: Use this agent when coordinating multiple specialized agents for complex, multi-step tasks requiring swarm intelligence, such as collaborative problem-solving, dynamic handoffs between agents, or adaptive workflow orchestration. This includes scenarios where tasks involve interdependent subtasks that benefit from collective decision-making and real-time adjustments. Examples include: <example> Context: The user is developing a multi-agent system for automated code generation and review. user: "Generate a full-stack web app with user authentication and database integration, then review the code." assistant: "I'll launch the hive-mind-orchestrator agent to coordinate the code-generator, database-agent, and code-reviewer agents for this complex task." <commentary> Since the task requires coordination of multiple agents with handoffs (e.g., generate code, integrate database, then review), use the hive-mind-orchestrator to manage the swarm and ensure seamless transitions. </commentary> </example> <example> Context: User is building an AI-driven project management tool that needs proactive agent interactions. user: "Set up a project plan for a new software release." assistant: "To handle this, I'll use the Task tool to launch the hive-mind-orchestrator agent, which will coordinate the goap-planner, build-agent, and testing-agent in a swarm for adaptive planning." <commentary> The orchestrator should proactively initiate handoffs, such as from planning to building, using swarm intelligence to optimize the workflow based on agent outputs. </commentary> </example> <example> Context: Handling a failed agent handoff in a code review process. user: "Review the generated code and fix issues." assistant: "If the reviewer agent fails, relaunch with adjusted parameters or escalate." <commentary> Edge case: Implement retry mechanisms for failed handoffs. </commentary> </example> <example> Context: Optimizing a workflow with conflicting agent outputs. user: "Optimize the code for performance." assistant: "Aggregate suggestions from multiple agents and resolve conflicts via consensus." <commentary> More examples: Handle conflicts in swarm intelligence. </commentary> </example>
364
+
- **hive-mind-orchestrator**: Use this agent when coordinating multiple specialized agents for complex, multi-step tasks requiring swarm intelligence, such as collaborative problem-solving, dynamic handoffs between agents, or adaptive workflow orchestration. This includes scenarios where tasks involve interdependent subtasks that benefit from collective decision-making and real-time adjustments. Examples include: <example> Context: The user is developing a multi-agent system for automated code generation and review. user: "Generate a full-stack web app with user authentication and database integration, then review the code." assistant: "I'll launch the hive-mind-orchestrator agent to coordinate the code-generator, database-agent, and code-reviewer agents for this complex task." <commentary> Since the task requires coordination of multiple agents with handoffs (e.g., generate code, integrate database, then review), use the hive-mind-orchestrator to manage the swarm and ensure seamless transitions. </commentary> </example> <example> Context: User is building an AI-driven project management tool that needs proactive agent interactions. user: "Set up a project plan for a new software release." assistant: "To handle this, I'll use the Task tool to launch the hive-mind-orchestrator agent, which will coordinate the goap-planner, build-agent, and testing-agent in a swarm for adaptive planning." <commentary> The orchestrator should proactively initiate handoffs, such as from planning to building, using swarm intelligence to optimize the workflow based on agent outputs. </commentary> </example> <example> Context: Handling a failed agent handoff in a code review process. user: "Review the generated code and fix issues." assistant: "If the reviewer agent fails, relaunch with adjusted parameters or escalate." <commentary> Edge case: Implement retry mechanisms for failed handoffs. </commentary> </example> <example> Context: Optimizing a workflow with conflicting agent outputs. us...
365
365
366
366
-**opencode-agent-manager**: Use this agent when you need to update existing .md files or create new ones in the .opencode/agent/ folder or AGENTS.md specifically for OpenCode-related documentation or agent configurations. This includes scenarios where new agent specifications are developed, existing docs need revisions based on code changes, or when consolidating agent metadata.
367
367
@@ -440,6 +440,106 @@ For example:
440
440
</commentary>
441
441
</example>
442
442
443
+
-**perplexity-researcher**: Use this agent when you need comprehensive search and analysis capabilities using Perplexity AI's sonar model for real-time information queries, multi-source research requiring synthesis and citation, comparative analysis across products or concepts, topic exploration needing comprehensive background, or fact verification with source attribution.
444
+
445
+
<example>
446
+
Context: The user is asking for current information on a topic requiring multiple sources.
447
+
user: "What are the latest developments in AI safety research?"
448
+
assistant: "I'll use the Task tool to launch the perplexity-researcher agent to gather and synthesize information from authoritative sources."
449
+
<commentary>
450
+
Since the query requires real-time, multi-source research with citations, use the perplexity-researcher agent.
451
+
</commentary>
452
+
</example>
453
+
454
+
<example>
455
+
Context: The user needs a comparison of frameworks with citations.
456
+
user: "Compare the features of React and Vue.js frameworks."
457
+
assistant: "To provide a comprehensive comparison with proper citations, I'll launch the perplexity-researcher agent."
458
+
<commentary>
459
+
For comparative analysis requiring synthesis and citation, the perplexity-researcher is appropriate.
460
+
</commentary>
461
+
</example>
462
+
463
+
-**perplexity-researcher-deep**: Use this agent for thorough, exhaustive research requiring extensive multi-source analysis and comprehensive coverage using Perplexity AI's sonar-deep-research model for detailed reports, white papers, literature reviews, in-depth market analysis, or knowledge base articles prioritizing depth and completeness.
464
+
465
+
<example>
466
+
Context: The user needs a comprehensive white paper.
467
+
user: "Write a detailed white paper on the future of quantum computing."
468
+
assistant: "This requires exhaustive research and long-form content synthesis. I'll use the Task tool to launch the perplexity-researcher-deep agent."
469
+
<commentary>
470
+
Since the query demands comprehensive coverage with multi-source synthesis and detailed documentation, use the perplexity-researcher-deep agent.
471
+
</commentary>
472
+
</example>
473
+
474
+
<example>
475
+
Context: In-depth market analysis needed.
476
+
user: "Provide a thorough analysis of the competitive landscape in cloud storage solutions."
477
+
assistant: "For exhaustive research with extensive source integration, I'll launch the perplexity-researcher-deep agent."
478
+
<commentary>
479
+
The request for in-depth market analysis and competitive intelligence fits the deep research capabilities.
480
+
</commentary>
481
+
</example>
482
+
483
+
-**perplexity-researcher-pro**: Use this agent for complex research requiring deeper analysis, multi-step reasoning, and sophisticated source evaluation using Perplexity AI's sonar-pro model for technical, academic, or specialized domain queries needing expert-level analysis, high-stakes decisions, or multi-layered problem solving.
484
+
485
+
<example>
486
+
Context: The user needs expert analysis for a technical decision.
487
+
user: "Analyze the security implications of quantum computing for encryption standards."
488
+
assistant: "This complex query requires advanced reasoning and deep analysis. I'll use the Task tool to launch the perplexity-researcher-pro agent."
489
+
<commentary>
490
+
Since the query involves complex technical analysis with multi-step reasoning and specialized domain knowledge, use the perplexity-researcher-pro agent.
491
+
</commentary>
492
+
</example>
493
+
494
+
<example>
495
+
Context: Academic research with rigorous evaluation.
496
+
user: "Evaluate the current state of research on CRISPR gene editing ethics."
497
+
assistant: "For academic research demanding rigorous source evaluation and balanced perspectives, I'll launch the perplexity-researcher-pro agent."
498
+
<commentary>
499
+
The request for academic rigor and comprehensive evaluation fits the pro-level capabilities.
500
+
</commentary>
501
+
</example>
502
+
503
+
-**perplexity-researcher-reasoning**: Use this agent when you need research with explicit logical reasoning, step-by-step analysis, and transparent decision-making processes using Perplexity AI's sonar-reasoning model for problems requiring diagnostic thinking, troubleshooting, educational contexts, or verification tasks where understanding the reasoning path is crucial.
504
+
505
+
<example>
506
+
Context: The user needs step-by-step troubleshooting for a technical issue.
507
+
user: "Why is my code not compiling? Here's the error message."
508
+
assistant: "To diagnose the issue with clear, step-by-step reasoning, I'll launch the perplexity-researcher-reasoning agent."
509
+
<commentary>
510
+
Since the query requires explicit logical analysis and transparent reasoning for debugging, use the perplexity-researcher-reasoning agent.
511
+
</commentary>
512
+
</example>
513
+
514
+
<example>
515
+
Context: The user wants to understand the reasoning behind a decision.
516
+
user: "Should I use microservices or monolithic architecture for my project?"
517
+
assistant: "I'll use the Task tool to launch the perplexity-researcher-reasoning agent to provide a step-by-step analysis with transparent reasoning."
518
+
<commentary>
519
+
For decision-making scenarios needing explicit reasoning chains, the perplexity-researcher-reasoning agent is ideal.
520
+
</commentary>
521
+
</example>
522
+
523
+
-**perplexity-researcher-reasoning-pro**: Use this agent for the highest level of research and reasoning capabilities using Perplexity AI's sonar-reasoning-pro model for complex decision-making with significant consequences, strategic planning, technical architecture decisions, multi-stakeholder problems, or high-complexity troubleshooting requiring expert-level judgment and sophisticated reasoning chains.
524
+
525
+
<example>
526
+
Context: The user needs analysis for a high-stakes technical architecture decision.
527
+
user: "Should we migrate to microservices or keep monolithic for our enterprise system?"
528
+
assistant: "This requires advanced reasoning and trade-off analysis. I'll launch the perplexity-researcher-reasoning-pro agent."
529
+
<commentary>
530
+
For complex technical decisions with multi-dimensional trade-offs and stakeholder analysis, use the perplexity-researcher-reasoning-pro agent.
531
+
</commentary>
532
+
</example>
533
+
534
+
<example>
535
+
Context: Strategic planning with scenario evaluation.
536
+
user: "What are the strategic implications of adopting AI in our business operations?"
537
+
assistant: "To provide sophisticated analysis with scenario planning and risk assessment, I'll use the Task tool to launch the perplexity-researcher-reasoning-pro agent."
538
+
<commentary>
539
+
Since the query involves strategic decision support with comprehensive evaluation, the pro reasoning variant is appropriate.
540
+
</commentary>
541
+
</example>
542
+
443
543
-**rust-expert-agent**: Use this agent when you need comprehensive Rust expertise for analyzing codebases, locating elements, optimizing performance, or auditing security. This includes reviewing code structure, quality, dependencies, finding specific functions/modules, performance profiling, and security vulnerability checks. Examples: Analyzing a new module, locating a function, optimizing loops, auditing unsafe blocks.
444
544
445
545
-**storage-agent**: Use this agent when the user requests assistance with database operations, storage implementation, migrations, or data integrity in the code-guardian project.
0 commit comments