opencode

Drive OpenCode REST API sessions and prompts for headless automation.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/nq-rdl/agent-extensions --skill opencode-nq-rdl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opencode
Source: https://github.com/nq-rdl/agent-extensions/tree/main/skills/opencode
Command: npx skills add https://github.com/nq-rdl/agent-extensions --skill opencode-nq-rdl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interacting with the OpenCode REST API to drive server lifecycle, session management, prompts, and permissions is automated and easy to integrate into agent workflows.

Core Features & Use Cases

  • Manage server startup, health checks, and session creation.
  • Send prompts synchronously or asynchronously and monitor via Server-Sent Events.
  • Control permissions, agent routing, and cleanup for headless automation.

Quick Start

Start the OpenCode server and issue your first session using the REST endpoints.

Frequently Asked Questions about opencode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate OpenCode session management and prompt handling via REST API?

Automate OpenCode session management and prompt handling by driving the HTTP REST API from agents and automated workflows to control session lifecycles, send prompts, and monitor responses across multiple sessions.

What is headless orchestration for OpenCode agents?

Headless orchestration for OpenCode agents uses the REST API to manage server startup, health checks, and session creation without a user interface, enabling fully automated server lifecycle and prompt handling.

Can I monitor asynchronous REST API prompts using Server-Sent Events?

Yes, you can monitor asynchronous REST API prompts using Server-Sent Events to track real-time message updates and agent routing responses after sending prompts to the OpenCode server.

How do I control permissions and agent routing for headless automation workflows?

Control permissions and agent routing for headless automation workflows by applying the OpenCode REST API endpoints to manage access levels and direct prompt handling across multiple sessions.

Do I need to manually start the OpenCode server before creating REST API sessions?

Yes, you need to start the OpenCode server and run health checks before issuing your first session using the REST endpoints to ensure the environment is ready for headless automation.