<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opencode on Unbound Force</title><link>https://unboundforce.dev/tags/opencode/</link><description>Recent content in Opencode on Unbound Force</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright (c) 2025-2026 Unbound Force</copyright><lastBuildDate>Sun, 23 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://unboundforce.dev/tags/opencode/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Platform Support — uf init Now Scaffolds for Cursor</title><link>https://unboundforce.dev/blog/multi-platform-support/</link><pubDate>Sun, 23 Aug 2026 00:00:00 +0000</pubDate><guid>https://unboundforce.dev/blog/multi-platform-support/</guid><description>&lt;h2 id="the-single-platform-ceiling"&gt;The Single-Platform Ceiling&lt;/h2&gt;
&lt;p&gt;Until now, Unbound Force was an OpenCode integration. Convention packs, MCP server configuration, agent prompts, and skill definitions all targeted one platform&amp;rsquo;s file layout. If your team used Cursor, you were out of luck — or stuck maintaining a parallel set of hand-written configuration files that drifted from the canonical source within days.&lt;/p&gt;</description></item></channel></rss>