openAgent

1# Security
2 
3## IMPORTANT
4 
5We do not accept AI generated security reports. We receive a large number of
6these and we absolutely do not have the resources to review them all. If you
7submit one that will be an automatic ban from the project.
8 
9## Threat Model
10 
11### Overview
12 
13OpenCode is an AI-powered coding assistant that runs locally on your machine. It provides an agent system with access to powerful tools including shell execution, file operations, and web access.
14 
15### No Sandbox
16 
17OpenCode does **not** sandbox the agent. The permission system exists as a UX feature to help users stay aware of what actions the agent is taking - it prompts for confirmation before executing commands, writing files, etc. However, it is not designed to provide security isolation.
18 
19If you need true isolation, run OpenCode inside a Docker container or VM.
20 
21### Server Mode
22 
23Server mode is opt-in only. When enabled, set `OPENCODE_SERVER_PASSWORD` to require HTTP Basic Auth. Without this, the server runs unauthenticated (with a warning). It is the end user's responsibility to secure the server - any functionality it provides is not a vulnerability.
24 
25### Out of Scope
26 
27| Category                        | Rationale                                                               |
28| ------------------------------- | ----------------------------------------------------------------------- |
29| **Server access when opted-in** | If you enable server mode, API access is expected behavior              |
30| **Sandbox escapes**             | The permission system is not a sandbox (see above)                      |
31| **LLM provider data handling**  | Data sent to your configured LLM provider is governed by their policies |
32| **MCP server behavior**         | External MCP servers you configure are outside our trust boundary       |
33| **Malicious config files**      | Users control their own config; modifying it is not an attack vector    |
34 
35---
36 
37# Reporting Security Issues
38 
39We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
40 
41To report a security issue, please use the GitHub Security Advisory ["Report a Vulnerability"](https://github.com/anomalyco/opencode/security/advisories/new) tab.
42 
43The team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
44 
45## Escalation
46 
47If you do not receive an acknowledgement of your report within 6 business days, you may send an email to security@anoma.ly
48