docs: add clearer bedrock instructions #40
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
thanks a ton! |
carabistouflette
pushed a commit
to carabistouflette/opencode
that referenced
this pull request
Jun 16, 2025
m-pa
pushed a commit
to m-pa/opencode
that referenced
this pull request
Dec 4, 2025
randomm
added a commit
to randomm/opencode
that referenced
this pull request
Jan 9, 2026
* fix(anomalyco#41): correct Perplexity tool names across configs and prompts Replace incorrect tool references with actual MCP server tool names: - mcp_perplexity_research → perplexity-ask_deep_research - mcp_perplexity_ask → perplexity-ask_search, perplexity-ask_reason, perplexity-ask_deep_research Files updated: - opencode.work.json: 28 tool references across 14 agents - opencode.personal.json: 28 tool references across 14 agents - 18 prompt files with corrected Perplexity tool names This fixes tool invocation errors when agents attempt to use Perplexity research capabilities. * feat(anomalyco#40): add research-backed boundary definitions to agent prompts Implement minimal, evidence-based prompt improvements to prevent agents from attempting GitHub operations outside their scope: PM prompt (4 lines): - Explicit coordination-only boundary - GitHub ops delegation to git-agent - Issue verification requirement Specialist prompts (6 lines each × 13): - Standardized scope boundary section - Do-not checklist (keyword format) - Cross-domain escalation protocol - Pre-work validation checklist Research basis: Perplexity research on prompting best practices found checklist/keyword format achieves 2-3x better compliance than narrative prose with fewer tokens. Files: 14 prompts updated, 97 lines total
randomm
added a commit
to randomm/opencode
that referenced
this pull request
Jan 9, 2026
* fix(anomalyco#41): correct Perplexity tool names across configs and prompts Replace incorrect tool references with actual MCP server tool names: - mcp_perplexity_research → perplexity-ask_deep_research - mcp_perplexity_ask → perplexity-ask_search, perplexity-ask_reason, perplexity-ask_deep_research Files updated: - opencode.work.json: 28 tool references across 14 agents - opencode.personal.json: 28 tool references across 14 agents - 18 prompt files with corrected Perplexity tool names This fixes tool invocation errors when agents attempt to use Perplexity research capabilities. * feat(anomalyco#40): add research-backed boundary definitions to agent prompts Implement minimal, evidence-based prompt improvements to prevent agents from attempting GitHub operations outside their scope: PM prompt (4 lines): - Explicit coordination-only boundary - GitHub ops delegation to git-agent - Issue verification requirement Specialist prompts (6 lines each × 13): - Standardized scope boundary section - Do-not checklist (keyword format) - Cross-domain escalation protocol - Pre-work validation checklist Research basis: Perplexity research on prompting best practices found checklist/keyword format achieves 2-3x better compliance than narrative prose with fewer tokens. Files: 14 prompts updated, 97 lines total * feat(anomalyco#44): expand PM tools and standardize on ripgrep over grep Research-backed expansion of PM tool permissions to enable effective context gathering for informed routing decisions. PM tool additions (read-only): - cat * (all files, not just .project-id) - rg* (ripgrep for fast, gitignore-aware search) - jq* (JSON parsing for GitHub API responses) - wc* (counting and statistics) New instruction file: instructions/tool-preferences.md - System-wide mandate: Use rg over grep - Rationale: faster, respects .gitignore, better defaults - Usage examples and common patterns Research basis: Industry best practice shows orchestrators need read access for informed routing decisions (Perplexity research on multi-agent systems 2024-2025). Files: 2 configs, 1 new instruction, 1 prompt (4 total)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
I was missing clearer instructions on how to get up and running with Bedrock and took the time to write them down in the readme.
I haven't used it but I think we should be able to make this more generic or add information on how to do the same with the supported Azure and GCP models.