anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

.opencode/agents/ folder agents are giving the <tool_call> response #8971

New Issue
Open
opened 2026-02-16 18:11:17 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @mahesh-muttinti on GitHub (Feb 10, 2026).

Originally assigned to: @thdxr on GitHub.

Question

I have been working on implementing/integrating the agents/sub agents in opencode tui. i followed the .opencode/agents and .opencode/prompts folder pattern which is also produced by opencode only when i asked like "Create agents/sub agents for multi tasking"

Image Image Image

This the one of the sub agent task output and giving same <tool_call> response every time i asked to do something with sub agents. Please correct me if i am doing this in wrong way

<tool_call>
{"name": "task", "arguments": {"description":"Generate comprehensive PR description","prompt":"Based on the git commit history and file changes I've analyzed, this branch implements a comprehensive feature flags and Sentry integration system along with OpenCode multi-agent workflow automation. 
Please create a detailed PR description that includes:
1. Summary: What this PR accomplishes overall
2. Key Changes: List of major components implemented
3. Feature Flags Integration: Complete OpenFeature + Sentry implementation
4. OpenCode Workflow: Multi-agent system setup
5. Code Standards: ESLint, Prettier, and commit standards
6. Documentation: New documentation and guides
7. Git Automation: Hooks and scripts
8. Testing: Testing strategy and examples
9. Deployment: Build and deployment considerations
10. Migration Guide: How to migrate from existing setup
Please make the description comprehensive, professional, and include all relevant technical details from the implementation. Reference the FEATURE-FLAGS-SENTRY-INTEGRATION-V2-REVIEWED.md document for specific technical details.","subagent_type":"pr-writer"}}
</tool_call>
Originally created by @mahesh-muttinti on GitHub (Feb 10, 2026). Originally assigned to: @thdxr on GitHub. ### Question I have been working on implementing/integrating the agents/sub agents in opencode tui. i followed the `.opencode/agents` and `.opencode/prompts` folder pattern which is also produced by opencode only when i asked like "Create agents/sub agents for multi tasking" <img width="1182" height="484" alt="Image" src="https://github.com/user-attachments/assets/abcf5ce2-b905-453a-bc6b-08300b1e64d2" /> <img width="1066" height="693" alt="Image" src="https://github.com/user-attachments/assets/2ba69d1f-8325-435f-bf15-c54b107f5d6c" /> <img width="1065" height="546" alt="Image" src="https://github.com/user-attachments/assets/6022364c-8b5c-49ec-9f4d-2554a3406a9c" /> This the one of the sub agent task output and giving same <tool_call> response every time i asked to do something with sub agents. Please correct me if i am doing this in wrong way ```js <tool_call> {"name": "task", "arguments": {"description":"Generate comprehensive PR description","prompt":"Based on the git commit history and file changes I've analyzed, this branch implements a comprehensive feature flags and Sentry integration system along with OpenCode multi-agent workflow automation. Please create a detailed PR description that includes: 1. Summary: What this PR accomplishes overall 2. Key Changes: List of major components implemented 3. Feature Flags Integration: Complete OpenFeature + Sentry implementation 4. OpenCode Workflow: Multi-agent system setup 5. Code Standards: ESLint, Prettier, and commit standards 6. Documentation: New documentation and guides 7. Git Automation: Hooks and scripts 8. Testing: Testing strategy and examples 9. Deployment: Build and deployment considerations 10. Migration Guide: How to migrate from existing setup Please make the description comprehensive, professional, and include all relevant technical details from the implementation. Reference the FEATURE-FLAGS-SENTRY-INTEGRATION-V2-REVIEWED.md document for specific technical details.","subagent_type":"pr-writer"}} </tool_call> ```
yindo commented 2026-02-16 18:11:17 -05:00
Author
Owner
Copy Link
Copy Source

@mahesh-muttinti commented on GitHub (Feb 10, 2026):

Few issues/scenarios/observations where the above case would come

  1. Rate limit exceeded for model we attached to agents md files
  2. Due to that, the <tool_call> response coming and opencode not able to predict that and stuck there
  3. So, I have changed the model to other and now the subagents are working fine
Image Image Image
@mahesh-muttinti commented on GitHub (Feb 10, 2026): Few issues/scenarios/observations where the above case would come 1. Rate limit exceeded for model we attached to agents md files 2. Due to that, the `<tool_call>` response coming and opencode not able to predict that and stuck there 3. So, I have changed the model to other and now the subagents are working fine <img width="1027" height="391" alt="Image" src="https://github.com/user-attachments/assets/7371690a-988d-48aa-9c0c-dcbd05a03ff7" /> <img width="1066" height="504" alt="Image" src="https://github.com/user-attachments/assets/e8a75104-17a8-4c67-b984-3c11c0474beb" /> <img width="1458" height="419" alt="Image" src="https://github.com/user-attachments/assets/4e790a5a-4890-47b7-91f2-3134bd49c6f7" />
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8971
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?