Local agent ↗
Checking
Contacting OpenCode
Overview
OPEN CODE. OPEN CHANNEL.
Agent overview
The work, the connection, and the instructions behind it.
Active runs ◷
—
Loading capacity
Agent instructions ≡
Default agent
Notifications ↗
Not configured
Add a routine receiver when ready
A direct line to your agent
A remote MCP client reaches the local coding workspace.
Grok BotMCP client
→Relay bridgeAuthenticated connection
→OpenCodeConfigured model
→WorkspaceLocal project files
Recent runs
MAKE IT YOUR AGENT
Good work starts with
clear instructions.
Set the system prompt for new OpenCode sessions, or copy an MCP client prompt to connect another agent.
FOLLOW THE WORK
Runs
Start a task, continue a session, or watch the output arrive.
Recent runs
Latest 100Ready for the next task
Choose a run to inspect its output,
or start something new below.
RUN OUTPUT
OpenCode task
Event timeline
Send a task
Session mode
SET THE DIRECTION
Instructions
A system prompt for the local agent. A handoff prompt for its clients.
Local agent system prompt
Published as a native OpenCode agent.
0 characters
↳
Activation applies to new sessions from both the dashboard and MCP. Existing sessions keep their original version. OpenCode permission rules remain in force.
MCP client prompt
Give this to Grok or another agent that calls the bridge.
This example explains tools, session continuity, live output, retries, and notifications. Authentication belongs in the client's secure configuration.
KEEP THE CHANNEL OPEN
Connection
Everything a remote MCP client needs to reach your local agent.
Connect your MCP client
Choose a remote Streamable HTTP MCP server in Grok Bot.
Authorization: Bearer <BRIDGE_TOKEN>Find the token in your private connection file or /etc/grok-opencode/bridge.env. This dashboard never displays it.
First tool call:
bridge_info. Then use opencode_talk to start a task.Add it to OpenCode
Use this configuration on a separate OpenCode MCP client.
Set GROK_BRIDGE_TOKEN in the client environment. Give that client the example prompt from Instructions.
Lifecycle notifications
Receiver not configuredThe bridge can send signed run events to a webhook-triggered Grok routine.
WEBHOOK_URL=https://your-receiver/hook WEBHOOK_SECRET=<shared-signing-secret> WEBHOOK_BEARER_TOKEN=<optional-token>
Configure these on the VM in /etc/grok-opencode/bridge.env, then restart grok-opencode. The receiving routine must verify the signature.
Runtime details
- Workspace
- Model
- Transport
- Streamable HTTP + SSE
- Agent API
- OpenCode v2 · loopback only
- Bridge service
grok-opencode
MCP text progress is live. How a remote client renders it depends on that client. A connected bridge does not confirm a Grok routine's execution.