Connect Parallel Task to OpenCode
Give OpenCode governed access to Parallel Task’s 4 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Parallel Task to OpenCode in four steps
Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.
- 1
Approve Parallel Task in Runlayer
Add Parallel Task from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect OpenCode to Runlayer
Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Parallel Task’s 4 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
OpenCode setup guide - 3
Sign in to Parallel Task
Sign in the way Parallel Task requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Parallel Task from OpenCode
Parallel Task’s approved tools appear in OpenCode. Every call is checked against policy and recorded.
Tools
4 Parallel Task tools in OpenCode
Runlayer policy decides which of these OpenCode users can call.
Create deep research
Creates a Deep Research task for comprehensive, single-topic research with citations.
Create Task group
Batch data enrichment tool.
Get result markdown
Get final task results as markdown.
Get status
Lightweight status check (~50 tokens).
Control
What Runlayer can see and stop in OpenCode
Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.
Gateway policy (available)
Every Parallel Task call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.
Frequently asked questions
Connect more