OpenAI's former Chief Operating Officer, Brad Lightcap just announced he is stepping down from the company Here is the full letter Lightcap sent to OpenAI employees: "Team, it is bittersweet to share that I’ll be moving on from OpenAI to start something new. I feel incredibly fortunate to have spent most of the last decade pursuing our mission and building this company. Sitting here today, mission success feels within sight. It has been the honor of my life to help bring us to this point, and to do it alongside all of you. I joined OpenAI in 2018, eight years ago this month, because I wanted to work on something hard. @sama introduced me to @gdb and @ilyasut, who showed me a pitch deck suggesting that because models improve predictably with scale, AGI was not only possible but likely. If you had told me then that we’d be where we are today, I wouldn't have believed you. In the years that followed, I had the privilege of building the first versions of most of our operations and business teams – from Finance to Legal, People, CorpSec, GTM/Gov, Partnerships, and more. Among the most rewarding parts of this journey for me has been watching each of these teams mature under brilliant leaders. I am excited for the next decade in the hands of this incredibly capable team. At the same time, we grew from a small research lab to one of the most consequential companies of our time. I was reminded of that fact constantly – from serving our first user to our billionth, to the growing scale and ambition of our partnerships and the occasional curveball (the Blip, etc.). Through it all, I’m proud of how we’ve maintained our focus on people. It always amazes me how quickly the world has adopted our tools and rallied behind our mission. I hope we will continue to earn their trust. Over the last few months, I’ve been focused on the next horizon and what would stand in the way of mission success. I believe there are a few important new things the world will need to get right as we enter this next period. I’ll have more to share soon, but I believe in OpenAI more than ever and am excited to help you all advance the mission from a different vantage point. I am deeply grateful to have had the opportunity to work with all of you, and to so many of you for the support through the years. The old OpenAI meme that “the real AGI is the friends you made along the way” really rings true for me. I will be around for the next few weeks. I am not going far and hope to continue to support you all however I can. I’ll always be a phone call away if you need me. Brad"

# 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#