rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{escape(entry['title'])}
copia local · blog real
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(entry['title'])}
{escape(entry['title'])}
copia local · blog real
{escape(entry['title'])}
{escape(entry['title'])}
copia local · blog real
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
rss-offline rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{''.join(cards)}rss-offline rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{''.join(cards)}{escape(entry['title'])}
copia local · blog real
rss-offline rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{''.join(cards)}rss-offline rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{''.join(cards)}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
rss-offline rss-offline
PDF diario con artÃculos nuevos.
37 artÃculos · últimos 14 dÃas
Archivo de PDFs
rss-offline-2026-05-30.pdf
{escape(item['name'])}
{escape(item['name'])}
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}{escape(item['name'])}
{escape(item['name'])}
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
{escape(item['name'])}
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
''')\n","newText":" for item in pdf_archive:\n pdf_cards.append(f'''{escape(item['name'])} descargar
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}{escape(item['name'])}
{escape(item['name'])} descargar
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
{escape(item['name'])} descargar
rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline sin conexión Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
Still a developer. Just outside. Our latest GitHub Shop collection is here. - The GitHub Blog \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[Showing lines 1-117 of 1003 (50.0KB limit). Use offset=118 to continue.]"}],"details":{"truncation":{"content":"\n\n\nStill a developer. Just outside. Our latest GitHub Shop collection is here. - The GitHub Blog \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n","truncated":true,"truncatedBy":"bytes","totalLines":220,"totalBytes":70047,"outputLines":117,"outputBytes":49368,"lastLinePartial":false,"firstLineExceedsLimit":false,"maxLines":2000,"maxBytes":51200}},"isError":false,"timestamp":1780219531843}}
{"type":"message","id":"048c4bbe","parentId":"4abf6e13","timestamp":"2026-05-31T09:25:31.844Z","message":{"role":"toolResult","toolCallId":"call_5Vx1dcNiLFATM3JbQmcGJMrD|fc_0f029265420fe376016a1bfe8bab288191b0882eab7a7a122e","toolName":"read","content":[{"type":"text","text":"\n\n\n\nStill a developer. Just outside. Our latest GitHub Shop collection is here. - The GitHub Blog \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[Showing lines 1-118 of 979 (50.0KB limit). Use offset=119 to continue.]"}],"details":{"truncation":{"content":"\n\n\n\nStill a developer. Just outside. Our latest GitHub Shop collection is here. - The GitHub Blog \n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n","truncated":true,"truncatedBy":"bytes","totalLines":220,"totalBytes":63722,"outputLines":118,"outputBytes":42787,"lastLinePartial":false,"firstLineExceedsLimit":false,"maxLines":2000,"maxBytes":51200}},"isError":false,"timestamp":1780219531844}}
{"type":"message","id":"317eaf1c","parentId":"048c4bbe","timestamp":"2026-05-31T09:25:31.845Z","message":{"role":"toolResult","toolCallId":"call_stXwYgiqOumhut6MNi1OylI1|fc_0f029265420fe376016a1bfe8bab30819182d85ef66f12cf72","toolName":"read","content":[{"type":"text","text":"\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing | DigitalOcean OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
![\"author\"](\"https://www.gravatar.com/avatar/6c29b11c4ac98017df02463d0c637bce9d9d157ae7b1c5a02c9d5f2f93a5d563?default=retro\")
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
\n\n[Showing lines 1-7 of 47 (50.0KB limit). Use offset=8 to continue.]"}],"details":{"truncation":{"content":"\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing | DigitalOcean OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
","truncated":true,"truncatedBy":"bytes","totalLines":47,"totalBytes":158521,"outputLines":7,"outputBytes":50712,"lastLinePartial":false,"firstLineExceedsLimit":false,"maxLines":2000,"maxBytes":51200}},"isError":false,"timestamp":1780219531845}}
{"type":"message","id":"b39aec93","parentId":"317eaf1c","timestamp":"2026-05-31T09:25:31.846Z","message":{"role":"toolResult","toolCallId":"call_iOIFuUQLnIPODEsVx1l8Wf5d|fc_0f029265420fe376016a1bfe8bab348191a15e2bb7cc7063f5","toolName":"read","content":[{"type":"text","text":"\n\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing | DigitalOcean OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
\nAn Inference Router is the auto-mode pattern engineers are used to, but with deliberate control over the tradeoffs that matter: latency, cost, and output quality. Rather than statically pointing your coding agent to a single model, an Inference Router can analyze each request and route it to the model best suited for that specific task. Not the most powerful model available, but the right model. That distinction is what drives real savings without compromising on your desired quality of output.
\nTo use DigitalOcean’s Inference Router: Create an Inference Router from the router catalog—pick a preset or build a custom router via the API or UI. No GPU management, no infrastructure to run. Use it by setting “model”: “router:your-router-name” in any OpenAI-compatible API call.
\nWhat Changed for OpenCode
\nOpenCode has become one of the most popular AI coding harnesses on GitHub, earning over 160,000 stars by embracing a simple idea: developers should not be locked into a single model provider. Its rise has shown a demand for provider agnostic AI use cases. At Deploy 2026, Tyler Gillam - a core engineer on Inference Router - demoed our integration live on stage, showing exactly how OpenCode and Inference Router work together to make intelligent model selection decisions in real time. If you want to see it before diving in, the full recording is linked at the bottom of this post.
\nPreviously, integrating DigitalOcean models into OpenCode meant manually editing your opencode.json, adding each model by hand, a list that would be outdated within weeks given the pace of new model launches. So, we built a native OpenCode integration that supports Inference Routers and DigitalOcean Serverless Inference models right out of the box.
\nNow you can run the following steps:
\n\n- Launch OpenCode (desktop, web or TUI) and run
/connect \n- Select Login with DigitalOcean
\n- Your Inference Routers are shown in the Model Selection tab
\n
\nThat’s it. You’re plugging directly into a routing layer that’s already helping to make the cost & quality tradeoff decisions for you based on your stated needs — with our purpose-build Software Engineering preset.
\nBeyond Coding Agents
\nThis integration is part of a broader effort to bring DigitalOcean’s Inference Engine into the tools developers already use, while continuing to invest in open source and upstream contributions. OpenCode is one example of that direction.
\nThe goal is to make intelligent, cost-aware model routing the default for coding agents, not something you have to manually configure and hope for the best. As the OSS model landscape keeps improving, routing intelligence will become more valuable, not less. The gap between “frontier” and “good enough” is closing fast, and developers who take advantage of routing will consistently come ahead on both desired quality and cost.
\nIf you’re using OpenCode, try /connect today. If you want to dig deeper on what Inference Router is and how it works, the full documentation is available below.
\nInference Router Resources:
\n\n- How We Built DigitalOcean Inference Router
\n\n[Showing lines 1-27 of 35 (50.0KB limit). Use offset=28 to continue.]"}],"details":{"truncation":{"content":"\n\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing | DigitalOcean OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
{escape(entry['title'])}
copia local · blog real
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
rss-offline
Artículos por fecha con copia local y link real precargado.
{len(archived)} artículos · últimos {DAYS} días
Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
rss-offline
PDF diario con artÃculos nuevos.
37 artÃculos · últimos 14 dÃas
Archivo de PDFs
rss-offline-2026-05-30.pdf
{escape(item['name'])}
{escape(item['name'])}
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}{escape(item['name'])}
{escape(item['name'])}
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
{escape(item['name'])}
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
''')\n","newText":" for item in pdf_archive:\n pdf_cards.append(f'''{escape(item['name'])} descargar
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}{escape(item['name'])}
{escape(item['name'])} descargar
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
{escape(item['name'])}
{escape(item['name'])} descargar
rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}rss-offline
PDF diario con artículos nuevos.
{len(archived)} artículos · últimos {DAYS} días
Archivo de PDFs
{''.join(pdf_cards) or 'Todavía no hay PDFs.
'}Sin conexión
La lista y copias locales visitadas deberían seguir disponibles.
OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
\n\n[Showing lines 1-7 of 47 (50.0KB limit). Use offset=8 to continue.]"}],"details":{"truncation":{"content":"\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
","truncated":true,"truncatedBy":"bytes","totalLines":47,"totalBytes":158521,"outputLines":7,"outputBytes":50712,"lastLinePartial":false,"firstLineExceedsLimit":false,"maxLines":2000,"maxBytes":51200}},"isError":false,"timestamp":1780219531845}} {"type":"message","id":"b39aec93","parentId":"317eaf1c","timestamp":"2026-05-31T09:25:31.846Z","message":{"role":"toolResult","toolCallId":"call_iOIFuUQLnIPODEsVx1l8Wf5d|fc_0f029265420fe376016a1bfe8bab348191a15e2bb7cc7063f5","toolName":"read","content":[{"type":"text","text":"\n\n\n\nOpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer
- Updated:
- 3 min read
Coding agents today have a massive spending problem. Every request, whether you’re designing system architecture or writing a single-line docstring, often gets routed to the same expensive frontier model. The result: unnecessary token usage, higher inference costs, and little awareness of task complexity or budget constraints.
\nThis high cost stems from a “one-size-fits-all” approach to model usage, where premium frontier models are utilized for trivial tasks that don’t require such intensive reasoning effort. In multi-agent workflows, where orchestrators delegate work to specialized subagents, this lack of discrimination frequently leads to runaway costs and opaque failure modes. Without intelligent routing, developers can essentially be forced into closed-provider lock-in and high API usage fees, which quickly escalate during exploratory building phases.
\nDigitalOcean Inference Router, now in Public Preview, was built to solve this problem by dynamically routing requests to the right model for the job. As part of DigitalOcean’s AI-Native Cloud, it gives developers a unified way to control, optimize, and evaluate AI inference across models. And as of today, you can access it through OpenCode, the open-source AI coding agent, in as little as a few seconds.
\nWhat is an Inference Router?
\nAn Inference Router is the auto-mode pattern engineers are used to, but with deliberate control over the tradeoffs that matter: latency, cost, and output quality. Rather than statically pointing your coding agent to a single model, an Inference Router can analyze each request and route it to the model best suited for that specific task. Not the most powerful model available, but the right model. That distinction is what drives real savings without compromising on your desired quality of output.
\nTo use DigitalOcean’s Inference Router: Create an Inference Router from the router catalog—pick a preset or build a custom router via the API or UI. No GPU management, no infrastructure to run. Use it by setting “model”: “router:your-router-name” in any OpenAI-compatible API call.
\nWhat Changed for OpenCode
\nOpenCode has become one of the most popular AI coding harnesses on GitHub, earning over 160,000 stars by embracing a simple idea: developers should not be locked into a single model provider. Its rise has shown a demand for provider agnostic AI use cases. At Deploy 2026, Tyler Gillam - a core engineer on Inference Router - demoed our integration live on stage, showing exactly how OpenCode and Inference Router work together to make intelligent model selection decisions in real time. If you want to see it before diving in, the full recording is linked at the bottom of this post.
\nPreviously, integrating DigitalOcean models into OpenCode meant manually editing your opencode.json, adding each model by hand, a list that would be outdated within weeks given the pace of new model launches. So, we built a native OpenCode integration that supports Inference Routers and DigitalOcean Serverless Inference models right out of the box.
Now you can run the following steps:
\n- \n
- Launch OpenCode (desktop, web or TUI) and run
/connect\n - Select Login with DigitalOcean \n
- Your Inference Routers are shown in the Model Selection tab \n
That’s it. You’re plugging directly into a routing layer that’s already helping to make the cost & quality tradeoff decisions for you based on your stated needs — with our purpose-build Software Engineering preset.
\nBeyond Coding Agents
\nThis integration is part of a broader effort to bring DigitalOcean’s Inference Engine into the tools developers already use, while continuing to invest in open source and upstream contributions. OpenCode is one example of that direction.
\nThe goal is to make intelligent, cost-aware model routing the default for coding agents, not something you have to manually configure and hope for the best. As the OSS model landscape keeps improving, routing intelligence will become more valuable, not less. The gap between “frontier” and “good enough” is closing fast, and developers who take advantage of routing will consistently come ahead on both desired quality and cost.
\nIf you’re using OpenCode, try /connect today. If you want to dig deeper on what Inference Router is and how it works, the full documentation is available below.
Inference Router Resources:
\n- \n
- How We Built DigitalOcean Inference Router \n\n[Showing lines 1-27 of 35 (50.0KB limit). Use offset=28 to continue.]"}],"details":{"truncation":{"content":"\n\n\n\n
- Updated:
- 3 min read
OpenCode Now Supports DigitalOcean Inference Router for Intelligent Model Routing
By Musa Malik
AI/ML Engineer