OpenCode’s /init will guide AGENTS.md setup per repo

OpenCode has just rolled out plans to turn /init into a guided AGENTS.md setup that reads your repository and scaffolds agent rules from what it finds. It’s designed to capture the non-obvious conventions and workflow choices agents can’t reliably infer from code alone.

open-source cover

TL;DR

  • Next release change: /init becomes a guided AGENTS.md setup instead of simple file creation
  • Repo-aware flow: Reads the repository and infers agent-relevant project details for scaffolding instructions
  • Goal: Reduce gap between empty configuration and project-specific rules reflecting real conventions
  • Focus areas: Non-obvious workflows, conventions, and decisions that are easy to violate accidentally
  • Supported notes: AGENTS.md and commonly used sibling CLAUDE.md

OpenCode is teeing up a small but practical change for teams that already rely on repo-specific “agent notes”: in its next release, /init will become a guided AGENTS.md setup. The update is framed as an interactive flow that reads the repository and infers the kinds of details agents typically need, then uses that understanding to help scaffold the file.

From “create the file” to “shape the rules”

AGENTS.md (and its common sibling, CLAUDE.md) tends to be most useful when it captures the decisions that don’t show up cleanly in code or in a README—things that humans on the team learn through repetition and reviews. The upcoming OpenCode change positions /init less as a boilerplate generator and more as a guided setup that’s informed by the repo itself.

The goal is to reduce the gap between an empty agent configuration file and one that meaningfully reflects the project’s conventions.

Why the “non-obvious” parts matter

The most valuable agent guidance is rarely the obvious stuff like “run tests” or “use TypeScript.” It’s the project-specific texture: workflows, conventions, and decisions that are easy to violate accidentally, especially when a coding agent is moving quickly.

In practice, AGENTS.md or CLAUDE.md needs to include non-obvious choices or conventions of the codebase—the kind that won’t reliably be inferred from static analysis alone. That can include preferences that are consistent but not enforced, or rules that live in team culture more than in tooling.

OpenCode’s interactive /init is notable here because it’s described as reading the repo and figuring out the “stuff agents” act on, implying that the guided setup is designed to surface and capture those less explicit constraints rather than just emitting a template.

What’s changing in the next release

Based on the posted preview, the next OpenCode release will:

  • Turn /init into a guided AGENTS.md setup
  • Have the flow read the repo and infer relevant project details for agent instructions

No timing, pricing, or release-specific rollout details were included in the post.

Source: https://x.com/opencode/status/2039419606540992688

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community