# OpenCode Features and Practical Usage 🔌 Want your agent to reach into the outside world? OpenCode's MCP server integration turns Sentry errors, library docs, and code search into tools the agent can call directly. 🏷️ Title: External Tool Connections (Local/Remote) 🔗 URL: 📘 Overview Configure MCP (Model Context Protocol) servers and external service tools become automatically available to the agent alongside OpenCode's built-in tools. Both local (process-launched) and remote (HTTP endpoint) servers are supported. ⚙️ How It Works Servers are declared in the `mcp` block of `opencode.json`, each under a unique identifier. ・Local: set `type: "local"`, give `command` as the startup command array, and optionally pass `environment` variables. `timeout` (default 5000ms) is configurable. ・Remote: set `type: "remote"` and provide `url`. Authenticate by passing a Bearer token in `headers`, or use OAuth (a 401 can trigger the flow automatically). Each server can be toggled individually with `enabled`. MCP tools appear with the server name as a prefix, and the `tools` field with wildcards (`*`, `?`) lets you enable or disable them globally or per agent. 🛠️ Practical Usage A remote Sentry integration is just an entry under `mcp` with `type: "remote"`, the `url` ` a Bearer token in `headers`, and `enabled: true`. For local servers, launch with something like `"command": ["npx", "-y", "@/modelcontextprotocol/server-everything"]`. You can just as easily add Context7 for docs search (` or Grep for GitHub code search (` as remotes. Use `opencode mcp auth ` and `opencode mcp list` to authenticate and check status. 💡 Use Cases Have the agent investigate a production error via Sentry, look up the correct usage of an up-to-date library via Context7, and find real-world implementations across repos via Grep — all in a single session, from investigation through implementation. For safety, keep servers at `enabled: false` and switch them on only for the tasks that need them. ⚠️ Caveats MCP servers consume context. Enabling a server that exposes many tools (like GitHub's) can rapidly inflate token usage and risk overflowing the context limit. Keep the set of enabled servers tight, and if you use API keys, set `oauth: false` to suppress automatic OAuth. Note that a remote server can fail to start if it exceeds its `timeout`. #OpenCode# #MCP#

OpenCode is NOT listening to me, i told it to go find aliens and it found a paper where the authors thought a star was emitting interesting light and proved that it was actually error from equipment they were using that is the OPPOSITE of finding aliens

OpenCode Go is by far the largest attempt at making agents accessible to everyone we are very close to getting all the economics figured out, the more users we have the more possible it is we do not make any money on this side of the business, we work to not lose money

# OpenCode Features and Practical Usage 📜 Tired of re-explaining your project's conventions every single session? `AGENTS.md` fixes that: write it once, and the agent always operates with your rules in mind. 🏷️ Title: AGENTS.md 🔗 URL: 📘 Overview `AGENTS.md` is the file you use to give OpenCode custom instructions. Document your project's conventions, architecture, and build steps there, and that content is always included in the LLM's context so the agent behaves the way your team expects. ⚙️ How It Works Rules live at two levels: ・Project-level: an `AGENTS.md` at the repo root, applied only within that directory tree. ・Global-level: `~/.config/opencode/AGENTS.md`, shared across all sessions and best for personal preferences. At startup OpenCode searches in order: local `AGENTS.md` or `CLAUDE.md` (walking up from the current directory) → global `~/.config/opencode/AGENTS.md` → the Claude Code compatibility file `~/.claude/CLAUDE.md`. The first match in each category wins. The design is close to Cursor-style rules and makes migration easy. 🛠️ Practical Usage To pull in external docs as instructions, list them in the `instructions` field of `opencode.json`, e.g. `"instructions": ["CONTRIBUTING.md", "docs/guidelines.md", ".cursor/rules/*.md"]`. Globs are supported. If writing from scratch feels like a chore, run `/init`: it scans important files, may ask targeted questions, and generates or improves `AGENTS.md` for you. Commit the result to Git so the whole team shares it. 💡 Use Cases Capture tacit knowledge like "commit messages in Japanese," "tests use pytest," or "never import this layer directly" in `AGENTS.md`, and both new teammates and the agent share the same assumptions, cutting down on review churn. In monorepos, `instructions` globs let you bundle per-package conventions. ⚠️ Caveats File references hand-written inside `AGENTS.md` are not expanded automatically. When you need multiple files reliably loaded, the `instructions` field of `opencode.json` is the dependable choice. An existing `CLAUDE.md` is recognized for compatibility, but consolidating new content into `AGENTS.md` keeps things tidy. Remote URL references carry a 5-second timeout. #OpenCode# #AGENTSmd#

opencode2 is really powerful I am trying to run a live profile (rather than simulating past events) it will create its own plugin, hot reloads and then you can get every bit of data you want. its kinda crazy but this is why primitives are so important

# OpenCode Features and Practical Usage 🧰 Wish you could decide in one line what your AI agent is allowed to do and what it must never touch? OpenCode's built-in tools plus permissions give you exactly that. 🏷️ Title: Built-in Tools + Permissions 🔗 URL: 📘 Overview OpenCode agents act on your codebase through "tools" such as file editing and shell execution. A rich set ships by default, and each tool can be governed by an allow / ask / deny policy. You get the safety-versus-convenience balance tuned entirely from config. ⚙️ How It Works The main built-in tools are: ・`bash`: run shell commands (git, npm, etc.) ・`edit`: modify existing files via exact string replacement ・`write`: create or overwrite files ・`read`: read files, with optional line ranges ・`grep`: regex search across files ・`glob`: find files by patterns like `**/*.js` ・`webfetch` / `websearch`: fetch and search the web ・helpers like `lsp`, `apply_patch`, `skill`, `todowrite`, `question` Permissions are set in the `permission` field with three states: `allow` (run freely), `ask` (confirm each time), `deny` (forbidden). Note that the `edit` permission governs `edit`, `write`, and `apply_patch` together. 🛠️ Practical Usage In `opencode.json`, you can forbid edits, confirm every bash call, and allow web fetches freely — set `"edit": "deny"`, `"bash": "ask"`, and `"webfetch": "allow"` under the `permission` block. Tools coming from MCP servers can be controlled with wildcards. Writing `"mymcp_*": "ask"` requires confirmation for every tool from that server. 💡 Use Cases On a production-adjacent repo, set `edit` to `deny` and `bash` to `ask` so the agent can plan and investigate but cannot rewrite code or run destructive commands on its own. On a throwaway experiment branch, allow everything to move fast. Switching between the two is just a config change. ⚠️ Caveats By default all tools are allowed, so nothing is restricted until you explicitly narrow it. The `lsp` tool needs `OPENCODE_EXPERIMENTAL_LSP_TOOL=true`, and `websearch` (powered by Exa) needs `OPENCODE_ENABLE_EXA=1`. It is easy to forget that the `edit` permission also covers write and apply_patch. #OpenCode# #AIAgents#