# OpenCode Published articles for OpenCode. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI SDK harness layer now supports native subscription authentication DevFeed: [AI SDK harness layer now supports native subscription authentication]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-09-14T21:28:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [Authentication](), [OAuth](), [codex](), [Claude Code]() Tags: [ai](), [authentication](), [claude-code](), [codex](), [coding-agents](), [copilot](), [cursor](), [gateway](), [oauth](), [opencode](), [sdk]() ### AI overview The AI SDK harness layer now supports authenticating supported coding-agent harnesses through their native subscriptions. It uses explicit provider credentials when available, otherwise falls back to a host-native subscription without requiring code or configuration changes. ### Source excerpt The AI SDK harness layer now supports authenticating harnesses through their native subscriptions, where the underlying harness supports them. The harness layer runs different coding agents through the same HarnessAgent interface, so you can switch agents without changing your application code. No code changes or new settings are required. The direct authentication mode uses explicit provider environment credentials when they are present, and otherwise a native subscription found on the host. The default auto mode does the same when no AI Gateway credentials are set. The ai-gateway mode never reads native subscriptions. Native subscription credentials stay on the host. Just like with API keys, credentials are resolved at the host boundary. OAuth access tokens are refreshed there as needed. Where the sandbox supports it, the harness receives placeholder credentials and the real token is injected into outbound requests on the host. Native subscriptions work across harness adapters wherever the harness itself supports subscription login. These include Claude Code, Cline, Codex, Cursor, fx, GitHub Copilot, Grok Build, OpenCode, and Pi. Read the harness documentation to learn more. Read more ## Intelligence is yours. Let's keep it that way. DevFeed: [Intelligence is yours. Let's keep it that way.]() Original publisher: [Read original article]() Author: Paddy Srinivasan Published: 2026-09-14T21:11:13Z Content type: opinion Language: en Sources: [DigitalOcean]() Topics: [Open Source](), [Software](), [PostgreSQL](), [React](), [GitHub]() Tags: [agents](), [competition](), [github](), [infrastructure](), [intellectual-property](), [kubernetes](), [models](), [mysql](), [news](), [open-source](), [opencode](), [postgresql](), [react]() ### AI overview The article argues that founders should retain ownership and control of their companies' intelligence rather than depend on a single intelligence provider. It advocates an Open Intelligence movement built from open-source models, agents, harnesses, data technologies, and infrastructure, drawing comparisons with the adoption of Linux, PostgreSQL, MySQL, Kubernetes, and other open technologies. ### Source excerpt Intelligence was yours. A founder's intellectual property, business logic, differentiation, their intelligence, was once theirs alone. You built it, you owned it, and no tools/platform vendor stood between you and your customers. This is no longer clear. It is starting to look like it is "theirs." Intelligence can now be manufactured: the models, the agents and the harnesses that drive them, and the compute they run on. Providers who own all these can produce the application, and the differentiation, in every industry. That power runs the risk of becoming increasingly concentrated in a handful of companies. The race for the application layer is not about interfaces or go-to-market; it is a fight over who owns the intelligence layer itself. We have seen this before but we must act before its too late. Linux started behind Unix and Windows and now runs most of the world's servers. PostgreSQL and MySQL started behind Oracle and now underpin most new software. Kubernetes arrived after proprietary orchestrators and made them irrelevant. Each began less capable and won anyway: builders could see inside it, run it anywhere, and never had to ask permission. The same is happening now. Open weight models have repeatedly reached the frontier this past year. Open harnesses like OpenCode have grown to tens of trillions of tokens a day. Hermes reached more than 200,000 GitHub stars in five months, a milestone that took React a decade to achieve. Along with the near total adoption of open source data technologies, this collection of open technologies power an Open Intelligence movement. Open Intelligence restores the order. It returns to founders ownership of what makes their companies theirs. Founders should be free to build without tying their future to a single intelligence provider: their choice of agents, harnesses, data technologies, models, and infrastructure, with open source transparency, control, and competition keeping every layer honest. The stakes go beyond business. ## Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute DevFeed: [Void Linux Maintainer Orphans 100+ Packages Over AI Policy Dispute]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T15:11:26Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [Artificial Intelligence](), [Large Language Model](), [pull-requests]() Tags: [ai](), [desktop-linux](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [llm](), [open-source-graphics](), [opencode](), [packages](), [phoronix](), [phoronix-test-suite](), [policy](), [pull-request](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview A Void Linux maintainer orphaned 113 packages after a dispute over the project's policy on using generative AI. The dispute followed the use of GLM-5.3-Flash with OpenCode to generate comparison text for a Go package update without disclosing the AI usage. ### Source excerpt A Void Linux maintainer has orphaned more than 100 packages he maintained over a dispute of the project's AI policy for LLM-generated text... ## fx is now available in the AI SDK harness layer DevFeed: [fx is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-31T06:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [Vercel](), [AI-assisted coding](), [API](), [Protocol (disambiguation)]() Tags: [agent](), [agents](), [ai](), [api](), [building](), [claude](), [claude-code](), [codex](), [coding-agents](), [cursor](), [integration](), [open-source](), [opencode](), [sdk](), [vercel]() ### AI overview Vercel's AI SDK harness layer now supports fx, a lightweight open-source coding agent. Developers can run fx in their applications through the HarnessAgent interface using the official @ai-sdk/harness-fx adapter, which connects through the Agent Client Protocol via @ai-sdk/harness-acp. ### Source excerpt The AI SDK harness layer now supports fx, Vercel's lightweight, open-source coding agent. The harness layer provides one API for running coding agents in your application, so you can add fx without building a separate integration. Configure HarnessAgent with the official @ai-sdk/harness-fx adapter: The @ai-sdk/harness-fx adapter connects to fx over the Agent Client Protocol (ACP) using @ai-sdk/harness-acp. fx joins Claude Code, Cline, Codex, Cursor, Deep Agents, Grok Build, OpenCode, and Pi in the list of supported harnesses. Read the fx harness documentation to get started. Read more ## Qwen 3.8 Flash now available on AI Gateway DevFeed: [Qwen 3.8 Flash now available on AI Gateway]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [qwen](), [Artificial Intelligence](), [SDKs](), [AI-assisted coding](), [long-context](), [Claude Code](), [codex](), [cursor]() Tags: [ai](), [ai-gateway](), [api-keys](), [claude-code](), [codex](), [coding-agents](), [context-window](), [cost](), [cursor](), [opencode](), [pricing](), [qwen](), [routing](), [sdk](), [tokens](), [vercel]() ### AI overview Qwen 3.8 Flash from Alibaba is now available through Vercel AI Gateway. The model accepts text and images, supports a 1-million-token context window, and can generate responses of up to 65,000 tokens. It is recommended for coding, tool use, and multi-step agent workflows, and can be used through the AI SDK, coding agents, and the model playground. AI Gateway offers unified model access, usage and cost tracking, reliability features, reporting, retention controls, API key budgets, routing, and provider pricing without markup or inference platform fees. ### Source excerpt Qwen 3.8 Flash from Alibaba is now available on AI Gateway. It takes text and images as input, serves a context window of 1 million tokens, and can return up to 65k tokens in a response. Alibaba recommends it for coding, tool use, and multi-step agent workflows. To use Qwen3.8-Flash, set model to alibaba/qwen3.8-flash in the AI SDK: To use it in a coding agent, see the coding agents guide, then run vercel ai-gateway coding-agents setup to connect agents like Claude Code, Codex, OpenCode, Cursor, Pi, and more and select alibaba/qwen3.8-flash inside the agent. Try Qwen3.8-Flash in the model playground. AI Gateway provides a unified API for calling models, tracking usage and cost, and configuring retries, failover, and performance optimizations for higher-than-provider uptime. It includes built-in custom reporting, Zero Data Retention support, budgets for API keys, routing rules, and more. AI Gateway reflects provider pricing with no markup and does not charge a platform fee on inference, including on Bring Your Own Key (BYOK) requests. Read more ## The Real Python Podcast - Episode #308: Navigating Silent Failures in AI: Strategies for Effective Oversight DevFeed: [The Real Python Podcast - Episode #308: Navigating Silent Failures in AI: Strategies for Effective Oversight]() Original publisher: [Read original article]() Author: Real Python Published: 2026-08-21T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Artificial Intelligence](), [Large Language Model](), [AI-assisted coding](), [LLMs](), [Command-line interface](), [audit trail](), [Embeddings](), [Markdown](), [Script](), [Python]() Tags: [agentic-ai](), [agents](), [ai](), [api](), [audit-trail](), [cli](), [coding-agents](), [embeddings](), [gemini](), [markdown](), [opencode](), [tokens]() ### AI overview This podcast episode examines why AI systems can fail silently and how to improve oversight through context, checklists, validation, hooks, skills, scripts, and audit trails. It discusses document parsing problems such as unsupported formats, dropped attachments, and silent truncation, along with coding agents, CLI tools, embeddings, model selection, and token usage. The episode also highlights a course on AI-assisted Python coding with OpenCode and Gemini. ### Source excerpt Why do AI systems silently fail? How can you set up a system that produces results while also reviewing and validating the work? This week on the show, Calvin Hendryx-Parker returns to discuss his recent talk "Orchestrate Agentic AI: Context, Checklists, and No-Miss Reviews." ## Cline is now available in the AI SDK harness layer DevFeed: [Cline is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-18T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [Code](), [Shell](), [Command-line interface]() Tags: [agent](), [agents](), [ai](), [claude-code](), [codex](), [filesystem](), [opencode](), [remote](), [sandbox](), [sdk]() ### AI overview Vercel's AI SDK harness layer now supports Cline through the official @ai-sdk/harness-cline adapter. Cline uses the shared HarnessAgent interface, runs in the host process, and accesses the sandbox as a remote filesystem and shell. ### Source excerpt The AI SDK harness layer lets you run established coding-agent runtimes through one unified interface, so you can switch runtimes without changing your application code. Today we are adding Cline, which runs through the same HarnessAgent interface as other supported harness. @ai-sdk/harness-cline is the official harness adapter for Cline, implemented in collaboration with the Cline team. Cline runs fully in the host process and uses the sandbox as a remote filesystem and shell, so only its tools operate in the sandbox. No bridge process is installed inside the sandbox, similar to the existing Pi harness. Read the Cline harness documentation to get started. The full supported list of harnesses is now: Claude Code, Cline, Codex, Deep Agents, Grok Build, OpenCode, and Pi, with more coming soon. Read more ## How to use OpenCode DevFeed: [How to use OpenCode]() Original publisher: [Read original article]() Author: Jeff Morhous Published: 2026-08-13T10:34:23Z Content type: tutorial Language: en Sources: [The AI-Augmented Engineer]() Topics: [coding](), [Software]() Tags: [build](), [coding](), [how-to](), [opencode](), [software]() ### AI overview A tutorial on using OpenCode to build software without coupling the coding harness to a model provider. ### Source excerpt Wouldn't it be great if your coding harness wasn't coupled to your model provider? I'll show you how to use OpenCode to build software. ## Gemini 3.7 Flash now available on AI Gateway for 50% off DevFeed: [Gemini 3.7 Flash now available on AI Gateway for 50% off]() Original publisher: [Read original article]() Author: Jerilyn Zheng Published: 2026-08-13T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Artificial Intelligence](), [AI Models](), [Google](), [vercel ai sdk](), [AI-assisted coding](), [Vercel](), [API](), [web applications]() Tags: [2026](), [agentic](), [ai](), [api](), [api-keys](), [claude](), [claude-code](), [code](), [codex](), [coding](), [gemini](), [google](), [inference](), [models](), [opencode](), [performance](), [playground](), [pricing](), [routing](), [sdk]() ### AI overview Vercel announces that Google's Gemini 3.7 Flash is available through AI Gateway at 50% off until December 31, 2026. The release highlights improved reliability for software engineering and agentic work, stronger adherence when generating application code from design mocks, coding-agent integrations, a model playground, and gateway features for usage, cost, routing, retries, failover, and uptime. ### Source excerpt Gemini 3.7 Flash from Google is now available on AI Gateway for 50% off till December 31st, 2026. Gemini 3.7 Flash improves on prior Flash models at software engineering and agentic work. It resolves issues more reliably and spends less time stuck in failed agent loops, which matters on long tool-calling sequences where one derailment costs the rest of the run. It also generates desktop and web application code directly from design mocks, with closer adherence to the source design. To use Gemini 3.7 Flash, set model to google/gemini-3.7-flash in the AI SDK: To use it in a coding agent, run vercel ai-gateway coding-agents setup to connect Claude Code, Codex, OpenCode, or Pi, then select google/gemini-3.7-flash inside the agent. To try Gemini 3.7 Flash with no code, try the model in the model playground. AI Gateway provides a unified API for calling models, tracking usage and cost, and configuring retries, failover, and performance optimizations for higher-than-provider uptime. It includes built-in custom reporting, Zero Data Retention support, budgets for API keys, routing rules, and more. AI Gateway reflects provider pricing with no markup and does not charge a platform fee on inference, including on Bring Your Own Key (BYOK) requests. Read more ## Use ACP-compatible harnesses with the AI SDK harness layer DevFeed: [Use ACP-compatible harnesses with the AI SDK harness layer]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-08-13T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [Protocol (disambiguation)](), [SDKs](), [coding](), [Claude Code](), [codex]() Tags: [agent](), [ai](), [claude-code](), [codex](), [integration](), [opencode](), [sdk]() ### AI overview The AI SDK harness layer now supports Agent Client Protocol-compatible harnesses through the new @ai-sdk/harness-acp package. It acts as a meta adapter for harnesses that provide ACP-compatible packages, while direct adapters remain preferable for Claude Code and Codex when tighter integration is needed. ### Source excerpt The AI SDK harness layer now supports any Agent Client Protocol (ACP)-compatible harness with HarnessAgent through the new @ai-sdk/harness-acp package. Previously, every harness adapter wrapped one specific runtime (Claude Code, Codex, Pi, Deep Agents, OpenCode). @ai-sdk/harness-acp wraps the protocol instead. It is a meta adapter: rather than adapting a single harness, it lets you build an adapter for any harness that ships an ACP-compatible package. Implement a harness by passing that package to createACP and configure basic harness mapping. Then pass it to HarnessAgent like any other harness: ACP is an abstraction over coding harnesses, but the AI SDK harness layer stays deliberately decoupled from it. Not every harness supports ACP, and for some, ACP limits or changes how well they expose their internal behaviors, so a direct adapter can produce a tighter integration. For Claude Code and Codex, prefer the direct @ai-sdk/harness-claude-code and @ai-sdk/harness-codex adapters over an ACP-based implementation; reach for @ai-sdk/harness-acp when a harness has no direct adapter but ships an ACP-compatible package. Read the ACP harness documentation to get started. Read more ## Grok Build is now available in the AI SDK harness layer DevFeed: [Grok Build is now available in the AI SDK harness layer]() Original publisher: [Read original article]() Author: Maya Lekhi Published: 2026-08-13T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [coding](), [Claude Code](), [codex]() Tags: [agent](), [agents](), [ai](), [claude-code](), [codex](), [documentation](), [opencode](), [sdk]() ### AI overview Vercel has added Grok Build to the AI SDK harness layer, allowing it to run through the same HarnessAgent interface as other supported coding-agent runtimes. The official Grok Build adapter is built on the ACP harness adapter. ### Source excerpt The AI SDK harness layer lets you run established coding-agent runtimes through one unified interface, so you can switch runtimes without changing your application code. Today we are adding Grok Build, which runs through the same HarnessAgent interface as every other supported harness. @ai-sdk/harness-grok-build is the official harness adapter for Grok Build, built on top of the ACP harness adapter (@ai-sdk/harness-acp). Read the Grok Build harness documentation to get started. The full supported list of harnesses is now: Claude Code, Codex, Deep Agents, Grok Build, OpenCode, Pi, with more coming soon. Read more ## Building an OpenCode Companion with ESP-BLE-UART and ESP-VoCat DevFeed: [Building an OpenCode Companion with ESP-BLE-UART and ESP-VoCat]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-14T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Tutorial](), [AI Agent](), [ESP32](), [ESP32-S3](), [Embedded Software Dev](), [Internet of things](), [Hardware]() Tags: [ai-agent](), [blog](), [bluetooth](), [bluetooth-le](), [console](), [esp-idf](), [esp-iot-solution](), [esp-vocat](), [esp32](), [esp32-s3](), [firmware](), [opencode](), [tutorial]() ### AI overview This tutorial explains how to build a physical OpenCode companion with ESP-VoCat. It uses ESP-BLE-UART to send session status and permission prompts to an ESP32-S3 device, whose screen and button support status display and approval or rejection decisions. ### Source excerpt This article shows how to build a physical OpenCode companion with ESP-VoCat. The device displays session status and permission prompts, then sends one-button approval or rejection decisions over BLE UART. ## Deep Agents and OpenCode are now available in the AI SDK Harness DevFeed: [Deep Agents and OpenCode are now available in the AI SDK Harness]() Original publisher: [Read original article]() Author: Felix Arntz Published: 2026-06-25T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [vercel ai sdk](), [SDKs](), [LangChain](), [Vercel](), [coding]() Tags: [agent](), [ai](), [claude](), [codex](), [langchain](), [model](), [opencode](), [reasoning](), [sandbox](), [sdk](), [skills](), [tools](), [vercel]() ### AI overview Vercel's AI SDK Harness now supports Deep Agents and OpenCode through new adapters running in a Vercel Sandbox. The unified interface allows applications to switch between coding-agent runtimes without changing application code, while supporting tools, sessions, approvals, model selection, and streamed events. ### Source excerpt The AI SDK Harness lets you run established coding-agent runtimes through one unified interface, so you can switch runtimes without changing your application code. Today we're adding two new adapters, Deep Agents and OpenCode, both running inside a Vercel Sandbox. Deep Agents @ai-sdk/harness-deepagents adapts LangChain's deepagents runtime, with built-in file and shell tools, skills, host tools, multi-turn sessions, attach and resume, and built-in tool approvals. Read the Deep Agents harness documentation to get started. OpenCode @ai-sdk/harness-opencode boots a real OpenCode server inside the sandbox via @opencode-ai/sdk and streams its session events through the harness. It exposes OpenCode's built-in tools, supports both built-in and host tool approvals, and lets you pick the model, provider, and reasoning variant. Read the OpenCode harness documentation to get started. The full supported list of harnesses is now: Claude Code, Codex, Deep Agents, OpenCode, Pi, with more coming soon. Read more ## OpenCode power user tips DevFeed: [OpenCode power user tips]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-06-03T16:00:00Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Agent Harness](), [Tooling](), [Open Source](), [Code]() Tags: [agent-harness](), [claude-code](), [codex](), [commands](), [fork](), [how-to](), [model](), [open-source](), [opencode](), [switching](), [tips]() ### AI overview A practical guide to advanced OpenCode features, including the leader key, session management, session forking, conversation rewind, and model switching. ### Source excerpt In this post, I'd like to talk about some power user tips for OpenCode - an open source, model agnostic harness that more people should be using. Hopefully some of the advanced use cases convince you to give OpenCode (and OpenChamber) a shot. intermediate to advanced tips only I am specifically choosing to talk about some advanced tips in this post. If you've never used an agent harness or are looking to learn how to use OpenCode, this post can be useful but reader beware. Unleash the leader key ## While ⌃p (Ctrl + P) will list out all the possible commands (and is helpful), OpenCode has the concept of a "leader" key (which defaults to ⌃x). The leader key allows you to execute targeted useful commands more quickly and there's a slew of useful ones pre-defined1. ctrl-p shows all commands. notice leader key bound to some Manage multiple sessions - leader l ## People reach for whole terminals and extra tooling to juggle between agent sessions. I too had an overly customized tmux setup that looked like this: Before: agent session listing via tmux OpenCode simplifies this. Just hit leader + l and you view current sessions and can instantly switch to that session by just selecting it from the list. After: leader-l allows quick session switching The ability to quickly rename a session from this view is a godsend for me and what lets me be organized. session directory filtering you can pass a --dir . flag to opencode when launching it, which filters the session list to just this workspace/directory by default. You can alternatively not pass that flag, and the session list will show all sessions. Fork (or Branch) sessions /fork ## Forking takes the session you're in and spawns a new one. You branch off into a separate conversation while the main agent keeps grinding on whatever you left it doing. I love this feature and even cobbled my own version with tmux long before most harnesses shipped it. Claude Code, Codex and other harnesses have caught up and support this feature. ## AI model choices 2026-06 DevFeed: [AI model choices 2026-06]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-06-01T17:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [Artificial Intelligence](), [Text-based user interface](), [Tool]() Tags: [ai](), [audio](), [code](), [code-review](), [deep](), [gemini](), [gpt](), [model](), [models](), [opencode]() ### AI overview A developer shares their current AI tool stack, preferring Kimi 2.6 as a general-purpose workhorse, GPT 5.5 for coding and planning, Opus 4.8 for deep thinking and writing, and Gemini for image, video, and audio tasks. They also describe using OpenCode with OpenChamber as their preferred harness. ### Source excerpt My 2026 Jan AI tool stack. Six months since my last post and the whole list has turned over. Models ### Kimi 2.6 has become my overall workhorse model. By default I start most AI sessions with Kimi 2.6 now. GPT 5.5 remains my coding model of choice. My detailed planning, creating of exec-plans1, code review, simplification, and one-shot feature changes, reliably happen with GPT 5.5 (high). Opus 4.8 for deep thinking, writing and overall hard tasks. It's been four days since the release, so my opinion is still forming but I've been fascinated how quickly Opus 4.8 is giving me the right solutions, especially for the slightly more complex problems. - I still only reach out to, when other models are struggling, cause 💸🔥 Gemini for anything image, video, or audio. Nothing else is close. It has collapsed work that used to eat hours2 of mine. Harness ### I constantly try multiple harnesses but I think I've firmly settled on OpenCode paired with OpenChamber as my harness of choice. I've since written up my power tips for OpenCode, but I put a lot of these harnesses through the ringer and am really happy with this combo atm. I still drop often into TUI land with OpenCode and while like others I had my dalliance with cmux, I've found it's not great on performance and runs into memory issues. So I'm back to naked Ghostty. OpenCode on the other hand is really good at managing sessions, so often I don't even find myself needing to use tmux. Also, I use Hermes but having discovered OpenChamber, I don't find myself needing to reach as often. Again, this deserves a longer post, if you're curious. What surprised me ### I've just been blow away by Kimi 2.6. I've found it often keeps pace with GPT 5.5 with Medium reasoning. There have even been time it's results matched Opus 4.8 (though Opus typically gets the results one-shot). I'm not sure if I've engineered my harness in some way to work better with Kimi, but dang I love the results I'm getting. If you want to give it a shot, I rec ## How to Enable Gemma 4 Thinking Mode in LM Studio and OpenCode DevFeed: [How to Enable Gemma 4 Thinking Mode in LM Studio and OpenCode]() Original publisher: [Read original article]() Published: 2026-04-08T15:10:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [gemma4](), [Chat Bot]() Tags: [ai](), [gemma-4](), [lm-studio](), [local-llms](), [opencode](), [reasoning]() ### AI overview A tutorial on configuring Gemma 4 26B's thinking mode for local use with LM Studio and OpenCode. It explains that successful setup depends on reasoning parsing, the prompt template, model support, and message formatting across the involved tools. ### Source excerpt Everything Android, Kotlin and other random topics ## Using coding agents as modular components in developer tools DevFeed: [Using coding agents as modular components in developer tools]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2026-03-18T17:51:32Z Content type: opinion Language: en Sources: [le0nidas]() Topics: [coding](), [Tooling](), [Terminal](), [Git](), [Bash]() Tags: [agent](), [ai](), [bash](), [beads](), [coding](), [git](), [good-practices](), [open-code](), [opencode](), [productivity](), [thoughts](), [workflow]() ### AI overview The article argues that coding agents should be embedded as focused components within developer tools rather than treated as monolithic tools. It illustrates the approach by decomposing an OpenCode-based commit workflow into Bash scripts and a custom agent, following single-responsibility and composability principles. ### Source excerpt Or to be more exact, use a coding agent in a tool. This is my new starting point every time I begin to think of a tool I want to implement. Being part of the pipeline A couple of weeks ago I thought of creating an OpenCode agent that will check my uncommitted changes, construct ... Continue reading Use AI _in_ a tool not _as_ a tool -> ## Here's my list of reasons for using Opencode DevFeed: [Here's my list of reasons for using Opencode]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-03-17T20:00:00Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [User experience (UX)](), [client](), [servers](), [context]() Tags: [agentic](), [architecture](), [bugs](), [external](), [features](), [mcps](), [models](), [opencode](), [plugins](), [switching](), [tailscale](), [ux]() ### AI overview The author gives five personal reasons for using OpenCode: switching between models, its client-server architecture, subagent and mode features, opinionated user experience, and plugin customization. The article also notes that OpenCode has bugs and missing features, which the author says have not stopped them from using it exclusively for two months. ### Source excerpt Here's my list of reasons for using Opencode. 1. Switch between models on the fly ## I'm often experimenting with the bleeding edge models as they come out. I actively switch between models for tasks and I use them all enough where I can tell the difference. Opencode lets me switch between models mid-task or mid-conversation. Fluidly. 2. client-server architecture (a.k.a built-in remote control) ## I wrote about this and agentic fluidity in more detail but tldr: Opencode has the client/server architecture baked in. So I can just start an opencode server on one machine, expose it through tailscale serve and start using it on my phone or other machines. 3. Subagent + mode features ## I talked about this on my podcast in some detail but Opencode has the best implementation of subagents and modes. You can switch to a subagent definition as your primary mode, then operate other subagents from there. It makes orchestrator-type tasks super easy. 4. Opinionated UX ## I love that OpenCode is opinionated about their UX. They don't try to be Claude Code or Codex. In the process they have some really nice UX patterns like a sidebar with ongoing file changes, context/cost, MCPs connected etc. It's the first time I've not needed to worry about a custom statusline.sh or building one. 5. "Highly" customizable via plugins ## The plugin ecosystem is highly customizable. To the point where you can add new features, integrate with external services or even modify OpenCode's default behavior. The wonderful Jesse Vincent mentioned this to me when I was stupidly contemplating a fork. What's missing # It's not all rainbows and sunshine. Anomaly -- the team behind OpenCode -- is small. Which sometimes shows, because there's definitely bugs and some features missing. But I will say... none that's deterred me from using it for the last two months, exclusively. Go give it a shot. Many of the serious AI coders I know are really liking it and switching. ## OpenCode offers server-client access for on-the-go agentic coding DevFeed: [OpenCode offers server-client access for on-the-go agentic coding]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2026-02-20T21:04:46Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [agentic-coding](), [Command-line interface](), [servers](), [client](), [browser](), [tailscale](), [Artificial Intelligence](), [Open Source]() Tags: [agentic](), [agentic-coding](), [browser](), [cli](), [local](), [open-source](), [opencode](), [project](), [server](), [tailscale](), [terminal]() ### AI overview The article argues that OpenCode is a useful open-source option for accessing agentic coding sessions from multiple devices. It highlights OpenCode's server-client architecture, CLI and web modes, browser access, and use with Tailscale to connect to a development machine remotely. ### Source excerpt One of the reasons OpenClaw got so popular was how fluidly you can chat with and operate your agents. Pull up your phone, send a quick message on WhatsApp, and you're in business. As we focus more on agent orchestration1 in 2026, I think an important aspect will be access fluidity. How do you hop into your agent's context from any device, terminal, or IDE and just start coding? Claude Code supports this in a limited way, while others like Cursor and Codex take a cloud-based approach. The best option I've found for this "on-the-go" agentic coding is an open-source one -- OpenCode. OpenCode - your best "on-the-go" option for agentic coding. Server-client architecture ## OpenCode uses a native server-client architecture. You can simply spin it up in a regular terminal tab, just like claude or codex. But the power move is running it as a server and connecting multiple clients. A client can be your terminal tab, a mobile device, or a desktop computer. Each terminal tab becomes a new, isolated CLI session that connects to the server. Couple this with Tailscale, and you can securely connect to a dev machine running an OpenCode server from anywhere. Getting started ## I'd start by using opencode like a regular CLI tool. Once it feels familiar, switch to server/web mode. # advertises server as opencode.local opencode web --mdns # attach to a session # equivalent to starting a new claude code session opencode attach http://opencode.local:4096 --dir /path/to/project The beauty is you can open that opencode.local URL in any browser, and it's fully synced. Credit to my co-host Iury for tooting the OpenCode horn early, and my Instacart colleague Spencer for questioning my luddite tmux ways.2 I'll write a future post singing OpenCode's other praises. For now, if you're exploring the bleeding edge of agent access fluidity, don't sleep on it. See my post on AI paradigms. ↩︎ I noticed some memory leaks when using tmux sessions with OpenCode, and Spencer asked me: why not lean on the s ## skill.md: An open standard for agent skills DevFeed: [skill.md: An open standard for agent skills]() Original publisher: [Read original article]() Author: Michael Ryaboy Published: 2026-01-21T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Agent Skills](), [Documentation](), [AI-assisted coding]() Tags: [agent](), [agent-skills](), [announcements](), [article](), [claude](), [claude-code](), [coding-agents](), [cursor](), [opencode](), [skills]() ### AI overview Mintlify describes skill.md as an open standard for documenting how coding agents should use a product. Mintlify documentation sites include a skill.md file at their base URL, and users can customize it in the root of their documentation repository. ### Source excerpt All Mintlify documentation sites now contain a skill.md file. Learn about this open standard for agent skills and how to use it. ## A human-in-the-loop workflow for OpenCode agents, subagents, and Beads DevFeed: [A human-in-the-loop workflow for OpenCode agents, subagents, and Beads]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2026-01-06T14:51:35Z Content type: tutorial Language: en Sources: [le0nidas]() Topics: [configuration](), [context window]() Tags: [agent](), [agentic-coding](), [agents](), [ai](), [beads](), [configuration](), [context-window](), [execution](), [know-your-tools](), [opencode](), [productivity](), [review](), [tasks]() ### AI overview The article describes a personal development workflow using one primary OpenCode agent, one subagent, and Beads to manage planned tasks. The primary agent selects tasks, delegates implementation, requests human review, and commits approved changes, with an inner loop for requested revisions. ### Source excerpt OpenCode's agents configuration and Beads. A match made in heaven. My flow until now Working on a task starts with the Plan agent. I provide an initial prompt of what I want to achieve and the agent responds with a plan. If the plan needs adjustments I ask the agent to update it. When I'm ... Continue reading Pinky and the Brain: my agent/subagent duo -> ## OpenCode Made LLMs Useful for This Developer DevFeed: [OpenCode Made LLMs Useful for This Developer]() Original publisher: [Read original article]() Author: Harsh Shandilya Published: 2026-01-02T16:53:00Z Content type: opinion Language: en Sources: [Posts on Harsh Shandilya]() Topics: [Large Language Model]() Tags: [ai](), [llm](), [llms](), [opencode]() ### AI overview A developer describes finding earlier LLM tools underwhelming but says OpenCode, used with oh-my-opencode, made LLM-assisted programming useful for their work on Claw. ### Source excerpt Having unsuccessfully tried to use Windsurf and GitHub Copilot over the years, OpenCode finally made LLMs useful to me ## I wrote a replacement for GitHub's code review bot DevFeed: [I wrote a replacement for GitHub's code review bot]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2025-11-18T00:00:00Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [GitHub](), [Code review](), [GitHub Copilot code review](), [Pull Request]() Tags: [agent](), [code-review](), [firecracker](), [github](), [github-copilot](), [large-language-models-llms](), [linux](), [llm](), [opencode](), [review](), [self-hosted](), [self-hosting](), [slicer](), [source]() ### AI overview The author describes building a replacement for GitHub's code review bot. They explain code review bots and compare GitHub Copilot's feedback with the opencode CLI, reporting that Copilot's feedback was superficial while opencode produced more useful review feedback for an OpenFaaS product change. ### Source excerpt If GitHub themselves have a native code review bot, why not just use it? ## Zed introduces Agent Server Extensions for one-click ACP agent installation DevFeed: [Zed introduces Agent Server Extensions for one-click ACP agent installation]() Original publisher: [Read original article]() Author: Richard Feldman Published: 2025-11-06T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Extension](), [Development](), [Documentation]() Tags: [agent](), [agents](), [authentication](), [distribution](), [extensions](), [installation](), [opencode](), [svg]() ### AI overview Zed introduces Agent Server Extensions, which let users install ACP-compatible agents with one click, start them in new threads, and complete the agents' authentication process. The article also explains how developers can create and publish these extensions. ### Source excerpt Zed launches Agent Server Extensions, enabling one-click installation of ACP-compatible agents like Augment Code and OpenCode. [Next page]()