OpenCode, Day-to-Day

OpenCode, Day-to-Day

Why this guide exists

You can use OpenCode every day and still miss what it added last month. You may never try the features that would help you most. OpenCode ships fast. This guide keeps you current, a few new techniques a day, so you do not get left behind and you use OpenCode the way it is meant to be used.

Who it is for

OpenCode, Day-to-Day is a 17-day guide to OpenCode, the open-source coding agent, for developers who have used a coding agent such as Claude Code.

How it works

You build one small project, Ticket Triage, across every day. Each day starts where the day before ended and takes 20 to 40 minutes. Start here is a real lesson that ends in a result you can check, such as a passing test. Going deeper holds the details and edge cases for when you have more time.

What you will learn

  • Write permission rules that refuse a git push from the agent (Day 4).
  • Keep rules in a three-line AGENTS.md that every new session receives (Day 5).
  • Hand a review to a read-only reviewer subagent (Day 10).
  • Add a skill that loads only when the request matches (Day 11).
  • Connect an MCP server and prove the agent called it (Day 13).
  • Write a guard plugin that refuses agent edits to package.json (Day 14).
  • Run an unattended fix in its own worktree (Day 16).

The 17 days fall into five stages: getting started (Days 1 to 4), what the model reads (Days 5 to 7), models and providers (Days 8 and 9), delegate and verify (Days 10 to 13), and extend and automate (Days 14 to 17).

OpenCode, Day-to-Day roadmap: Getting started, Day 1 The install that connects a model, Day 2 The ten-minute daily loop, Day 3 Plan is an agent, Day 4 Stop mashing yes. What the model reads, Day 5 What the model reads, Day 6 Your coding agent forgets on purpose, Day 7 The summary dropped the rule. Models and providers, Day 8 One agent, any model and Day 9 The right model for the job. Delegate and verify, Day 10 Subagents keep the parent session small, Day 11 Load it when the task matches, Day 12 The session is a poor judge, Day 13 MCP is the connector. Extend and automate, Day 14 There is no hooks.json, Day 15 Where the session actually runs, Day 16 Run it without you, Day 17 Casual, pro, elite.

How it was tested

The Start here steps ran live on OpenCode 2.3.0 in November 2026 with a Google Gemini key on google/gemini-4-hydrogen. Days 8, 9, and 12 also used google/gemini-3.5-flash-lite. A step that was not run on 2.3.0 says so in the text.

Get the code

Day 1 builds Ticket Triage by hand. The code is in the ticket-triage-day-by-day repository on the opencode branch, with one tag per day, opencode/day-00 to opencode/day-17. Use a tag to catch up on any day.

Start

Start at Day 1, one part a day.

Also in this series: Claude Code, Day-to-Day, Cursor, Day-to-Day, OpenAI Codex, Day-to-Day, Pi, Day to Day, and GitHub Copilot, Day-to-Day.

The parts

  1. Your OpenCode Install Worked. Your Model Still Can't See the Key.
  2. Stop Restarting Your Coding Agent: The Ten-Minute Loop in the OpenCode TUI
  3. You Asked for a Plan and Got a Diff
  4. Your Coding Agent Already Said Yes
  5. Your AGENTS.md Is a Line Item, Not a README
  6. Your Coding Agent Forgets on Purpose
  7. The Summary Dropped the Rule: What OpenCode Compaction Does to Instructions You Typed in Chat
  8. Your Coding Agent Is Down. Your Session Is Not.
  9. Your Coding Agent Bill Is a Reading Bill
  10. Subagents Keep the Parent Session Small: How OpenCode Child Sessions Protect Your Context Window
  11. You Asked for One Keyword and Got a Release
  12. The Agent Said All Tests Pass. It Had Rewritten the Test.
  13. The Green Line Lied: Your MCP Server Was Never Called
  14. The Agent Was Refused Twice and Bumped the Version Anyway
  15. The Link Failed, the Session Didn't: Where OpenCode Actually Runs
  16. The Overnight Agent Run Looked Like a Success. None of It Came From /goal.
  17. One Broken Link, One Ordinary Day: The OpenCode Workflow From Casual to Elite