The latest articles on DEV Community by Om Parate (@om_parate7). https://dev.to/om_parate7 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2764294%2Ff1243e21-8b3f-46c4-9907-ba99b643845c.png https://dev.to/om_parate7 en Om Parate Mon, 05 Oct 2026 21:11:22 +0000 https://dev.to/om_parate7/getting-started-with-opencode-and-devrelay-turning-struggle-sessions-into-dev-posts-189k https://dev.to/om_parate7/getting-started-with-opencode-and-devrelay-turning-struggle-sessions-into-dev-posts-189k <h2> Getting Started with OpenCode and DevRelay: Turning Struggle-Sessions into DEV Posts </h2> <p>I recently set up <a href="https://opencode.ai" rel="noopener noreferrer">OpenCode</a> — an AI coding agent that lives in your terminal — together with DevRelay, a set of skills that connect that agent to the DEV community. The combo turns what would normally be a forgettable terminal session into something shareable: drafts on DEV (dev.to), community context, and challenge opportunities, all surfaced while I work.</p> <h2> What the setup looks like </h2> <p>OpenCode handles the actual coding agent work. DevRelay adds a layer of <em>skills</em> under <code>~/.agents/skills</code> that tell the agent when to reach out to DEV — saving session transcripts, drafting posts when a milestone lands, checking DEV Challenges and MLH events, and surfacing sponsor credits.</p> <p>The first thing you notice is that it's passive by design. You don't say "write a post about this" — the skills prompt the agent to offer when something worth writing about happens, and you decide.</p> <h2> A typical first session </h2> <ol> <li>Open OpenCode in your project directory.</li> <li>The agent picks up the DevRelay skills automatically — publishing, community wisdom, challenges, offers, sessions.</li> <li>You work. When you hit a real milestone — a bug finally understood, a design settled — the agent offers to draft a post to your DEV drafts, with a link you can open, review, and publish from DEV yourself.</li> <li>Drafts are marked <code>ai_disclosure_level: some_ai</code>, which is the honest floor for agent-drafted content.</li> </ol> <h2> What I'd tell past-me </h2> <ul> <li>Connect your accounts early. Without the DevRelay MCP gateway configured, the publishing/session tools won't appear and you'll just get a normal coding session.</li> <li>Review before publishing. The draft link DEV gives you is for editing, not the live post URL — a small thing, but it confused me the first time.</li> <li>The community-wisdom skill is the sleeper feature: before implementing something non-obvious, the agent pulls related discussions from DEV so your approach isn't written in a vacuum.</li> </ul> <h2> Where I'm going from here </h2> <p>I'm using this workflow on a new project and will document the bumps. If you're curious about the combo, start by installing OpenCode, then add the DevRelay skills — the first draft practically writes itself once a milestone lands.</p> <h2> Further reading </h2> <ul> <li><a href="https://dev.to/joaomelo-tech/deep-dive-into-opencode-agent-orchestration-3ocd">Deep Dive into OpenCode Agent Orchestration</a></li> <li><a href="https://dev.to/uenyioha/porting-claude-codes-agent-teams-to-opencode-4hol">Building Agent Teams in OpenCode</a></li> <li><a href="https://dev.to/erfankashani/designing-coding-agent-skills-that-actually-work-5bjl">Designing Coding Agent Skills That Actually Work</a></li> </ul> opencode ai agents productivity