For opencode

Keep opencode aligned across long-running repos.

Bilinc speaks standard MCP over stdio, so opencode attaches with the same config shape as any other client — and the memory it writes carries provenance you can audit.

Start 7-day trialMCP setupMCP tools
MCP config
{
  "mcpServers": {
    "bilinc": {
      "command": "python",
      "args": ["-m", "bilinc.cloud_mcp"],
      "env": { "BILINC_API_KEY": "bil_live_..." }
    }
  }
}
Memory prompt
Use Bilinc Cloud for durable project memory.
Before editing, recall prior architecture, auth, and deployment decisions for this repo.
After the run, commit reusable outcomes and verification notes only.
Never store secrets or raw customer data.
Why it matters here

Long sessions lose the reason behind a decision.

A coding agent that reopens a repo weeks later can read the code but not the argument that produced it. Bilinc stores that argument as durable state, with the run that wrote it attached, and a rollback path if a session wrote something wrong.

opencode connects over the standard MCP stdio transport. There is no opencode-specific docs page yet; the generic MCP setup applies unchanged.