OpenCode

About

Automatic summary of the docs and configuration of magnusoverli/opencode. Something wrong, or are you the maintainer and want your own text here? Get in touch

Supports

• Opens in the sidebar Its own page opens inside Home Assistant.

• Actively maintained Its author released or pushed a change in the last six months.

Setting it up

Add its app repository under Settings, Apps, then install and start it.

From the docs

Permissions

• Home Assistant APICan read and control Home Assistant.
• Supervisor APICan talk to the Supervisor, which manages apps and the system.

Configuration

• InterfaceChoose the terminal or pinned OpenChamber V2 web preview. Both use the same managed V2 backend and session history.
• Terminal themeColor scheme for the terminal. All ten themes are previewed in the Documentation tab. Applies to the terminal interface only.
• Font sizeFont size in pixels. Larger values are easier to read, smaller values fit more on screen. Applies to the terminal interface only.
• Cursor styleShape of the cursor: block, underline, or bar. Applies to the terminal interface only.
• Cursor blinkingBlink the cursor instead of showing it solid. Applies to the terminal interface only.
• Focus-friendly responses (beta)Ask OpenCode for action-first, concise, progress-aware replies that are quicker to scan and act on. Changes response wording only — it does not change permissions or safety confirmations.
• OpenCode Home Assistant toolsEnables the bundled configuration, validation, diagnostics and administration tools. Independent of Home Assistant native tools and external MCP servers; the Full profile includes the authenticated HAB CLI gateway.
• MCP tool profileControls which built-in Home Assistant MCP tools OpenCode receives. 'compact' is read-only diagnostics, 'configuration' adds documentation, validation and safe config writes, and 'full' keeps every existing tool including control and administration. A smaller profile reduces prompt size and tool-selection ambiguity, especially for local models.
• LSP integrationGive OpenCode live diagnostics, entity and service auto-completion, and validation while it edits Home Assistant YAML, through the Language Server Protocol (LSP).
• Screenshot toolRequires the Home Assistant access token below, and a model that accepts image input - many fast models cannot see pictures at all. Lets OpenCode photograph Home Assistant pages in a headless browser to check the result of dashboard changes; each capture takes about 5-10 seconds.
• Format YAML after editsOpt into whole-file Prettier formatting after native YAML edits. Off preserves unrelated formatting. An explicit formatter true or false in Custom OpenCode configuration takes precedence. Other formatters and YAML diagnostics are unaffected.
• Home Assistant access tokenLong-lived access token for talking to Home Assistant Core directly. Required by the screenshot tool above and by the ESPHome commands — leave empty if you use neither. Create one in Home Assistant under Profile → Long-lived access tokens.
• Home Assistant native toolsIndependent native MCP connection, on for new installs; upgrades preserve effective enabled/disabled state. Requires HA's MCP Server: Settings > System > AI > Model Context Protocol on HA 2026.10+, or the MCP Server integration on older versions. Supervisor supplies authentication; no URL or token needs to be pasted.
• Native tool selectionhome_assistant uses Your MCP API (/api/mcp), following HA's configured APIs; Expose all LLM APIs includes later additions. assist selects only Assist, and custom selects the API ID below. Upgrades migrate legacy Assist to home_assistant once, preserve custom choices and disabled states, and retain explicit selections afterward.
• Custom native API IDUsed only when Native tool selection is custom. Enter a registered API ID, not a URL; the bridge uses /api/mcp/<ID>. Existing custom selections retain their previous compatibility policy; newly selected specific APIs do not silently fall back to a broader endpoint.