opencode-config

Configure OpenCode agents, tools, permissions, and models via JSON/JSONC.

Updated Feb 10, 2026

Search Tags:#permissions #configuration #opencode #tool management #agent setup #llm configuration

Ready to run

npx skills add https://github.com/tardyp/esp_tock --skill opencode-config-tardyp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opencode-config
Source: https://github.com/tardyp/esp_tock/tree/main/.opencode/skills/opencode-config
Command: npx skills add https://github.com/tardyp/esp_tock --skill opencode-config-tardyp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to configuring OpenCode, demystifying its complex settings for agents, tools, permissions, and models.

Core Features & Use Cases

Configuration Reference: Detailed explanations of all configuration options, including JSON and Markdown formats.
Agent & Tool Management: Guidance on setting up custom agents, managing tool access, and defining permissions.
Use Case: You're setting up a new project with OpenCode and need to define specific permissions for your build agent to execute certain bash commands while denying others. This Skill will show you exactly how to structure your opencode.json or agent markdown files.

Quick Start

Use the opencode-config skill to understand how to configure agent permissions.

Frequently Asked Questions about opencode-config

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

FAQPage Schema

How do I configure OpenCode agent permissions in a JSON file?▼

You configure OpenCode agent permissions by defining tool access rules within an `opencode.json` or JSONC configuration file. This allows you to specify exactly which bash commands or tools an agent is permitted to execute or denied.

What is the difference between JSON and Markdown formats for OpenCode agent setup?▼

OpenCode agent setup supports both JSON/JSONC and Markdown formats. JSON provides a structured schema for defining permissions and models, while Markdown files offer a text-based approach for configuring custom agents and their tool access.

Can I restrict specific bash commands for a build agent in OpenCode?▼

Yes, you can restrict specific bash commands for a build agent in OpenCode. By structuring your `opencode.json` configuration, you can define granular permissions that permit certain commands while explicitly denying others.

What do I need to know to manage tools and models in OpenCode?▼

Managing tools and models in OpenCode requires an understanding of JSON/JSONC configuration syntax and the platform's specific schema. You need this knowledge to correctly define agent environments and apply advanced settings.

How does OpenCode handle custom agent configuration for AI environments?▼

OpenCode handles custom agent configuration by providing a comprehensive schema for defining AI environments. You use configuration files to manage tool access, set up agents, and adjust advanced model settings for administrative workflows.

When should I use JSONC instead of JSON for OpenCode configuration?▼

You should use JSONC instead of JSON when your OpenCode configuration requires comments or trailing commas for better readability. Both formats are supported for managing agent and tool settings within the environment.