ModsCode / Claude Code Mods / Ranking / vome-esphome
vome-esphome
A side pane for ESPHome in Claude Code: a map of the device from its YAML (board, network, buses, entities, pins, triggers) with what a save changed lit up, and the build Claude is running as it happens (phase, progress, the latest output,…
What it does
- Draws a pane
- Adds /esphome
- Watches tool calls and can refuse them
- Hooks plugin.register, session.start
- Keeps its own state between turns
Good points
- No network calls
- Starts no processes
- Written in TypeScript
- Has a desktop-specific branch
Code to start from
A starter ModsCode writes from the drawing it read, and the mod's own lines that draw, where there are any.
Starter (register.tsx)
import type { Register } from 'claude-code'
// Drawn like vome-esphome by Vortitron (pane), as ModsCode read it from the mod's code:
// https://modscode.com/claude-mods/mods/vortitron-vome-esphome/
// Written by ModsCode from that reading, not copied from the mod: use it as you like.
// Each value below stands for one the mod works out at run time; put in your own.
export const register: Register = on => {
// the pane: open it with $.ui.open({ id: 'my-pane', title: "ESPHome" })
on('ui.render', { component: 'Pane', requestId: 'my-pane' }, async ($, e) => {
const { Box, Text, Markdown, Code, Button } = $.ui.resolve(e)
const verb = '…'
const configuration = '…'
const status = '…'
const uploadPercent = '…'
const error = '…'
const line = '…'
const line2 = '…'
const line3 = '…'
const name = '…'
const configuration2 = '…'
const deployed = '…'
const current = '…'
const name2 = '…'
const configuration3 = '…'
const name3 = '…'
const configuration4 = '…'
const allowLines = '…'
return (
<Box flexDirection="column">
<Text bold wrap="truncate-end">
{verb}
{" "}
{configuration}
</Text>
<Text color="success" wrap="truncate-end">
{status}
</Text>
<Text color="suggestion">
████████░░░░░░░░
{" "}
{uploadPercent}
%
</Text>
<Text dimColor wrap="truncate-end">
{" "}
</Text>
<Text color="error" wrap="wrap">
{error}
</Text>
<Box flexDirection="column">
<Text wrap="truncate-end">
{line}
</Text>
<Text wrap="truncate-end">
{line2}
</Text>
<Text wrap="truncate-end">
{line3}
</Text>
</Box>
<Box flexDirection="column" marginTop={1}>
<Text bold>
Devices
</Text>
<Text wrap="truncate-end">
<Text color="warning">
{"↑ "}
</Text>
{name}
<Text dimColor>
{" "}
{configuration2}
{` ${deployed}`}
{` → ${current} available`}
</Text>
</Text>
<Text wrap="truncate-end">
<Text color="warning">
{"↑ "}
</Text>
{name2}
<Text dimColor>
{" "}
{configuration3}
{` ${deployed}`}
{` → ${current} available`}
</Text>
</Text>
<Text wrap="truncate-end">
<Text color="warning">
{"↑ "}
</Text>
{name3}
<Text dimColor>
{" "}
{configuration4}
{` ${deployed}`}
{` → ${current} available`}
</Text>
</Text>
</Box>
<Box flexDirection="column" borderStyle="round" borderColor="warning" paddingX={1} marginTop={1}>
<Text color="warning" wrap="wrap">
{"Auto mode refused the pane's read of the build's progress or the device's YAML. Add these to permissions.allow in "}
~/.claude/settings.json
, then the next build shows live:
</Text>
<Markdown text="[~/.claude/settings.json](file://~/.claude/settings.json)" />
<Code source={`${allowLines}`} />
<Box flexDirection="row" gap={2}>
<Button hotkey="c">
Copy the lines
</Button>
<Button hotkey="r">
Retry
</Button>
</Box>
</Box>
<Box flexDirection="row" gap={2} marginTop={1}>
<Text dimColor wrap="wrap">
{"Working on automations too? The automation pane shows them, and their runs: "}
<Text color="suggestion">
/plugin install vome-automation --marketplace Vortitron/home-assistant-mcp
</Text>
</Text>
<Button dimColor>
Hide
</Button>
</Box>
<Box marginTop={1} gap={2}>
<Button hotkey="l" dimColor>
Map and latest lines
</Button>
<Button hotkey="b" dimColor>
Animation off
</Button>
</Box>
</Box>
)
})
}
The mod's own code
Shown under the mod's licence (MIT); its text is below. Keep the notice if you copy these lines.
claude-plugin/vome-esphome/hooks/register.tsx lines 185–344 · Pane
on('ui.render', { component: 'Pane', requestId: PANE }, async ($, e) => {
const { Box, Text, Button, Code, Markdown } = $.ui.resolve(e)
const current = (await $.state.get(build)).value ?? null
const known = (await $.state.get(devices)).value ?? null
const refusal = (await $.state.get(blocked)).value ?? null
const isFxEnabled = (await $.state.get(fxOn)).value ?? true
const view = (await $.state.get(config)).value ?? null
const isFullLog = (await $.state.get(showLog)).value ?? false
const siblingHint =
!hasSibling && ((await $.state.get(sibling)).value ?? false) ? (
<Box flexDirection="row" gap={2} marginTop={1}>
<Text dimColor wrap="wrap">
Working on automations too? The automation pane shows them, and their runs: <Text color="suggestion">{AUTOMATION_INSTALL}</Text>
</Text>
<Button
key="hide-sibling"
dimColor
onPress={async () => {
await $.store.set('siblingHintOff', true).catch(() => undefined)
await $.state.set(sibling, false)
}}
>
Hide
</Button>
</Box>
) : null
const width = Math.max(20, e.props.bodyColumns)
const rows = Math.max(6, (e.viewport?.rows ?? 30) - 14)
const deviceRows = known && known.length > 0 ? (
<Box flexDirection="column" marginTop={1}>
<Text bold>Devices</Text>
{known.map(d => {
const isBehind = d.deployed !== null && d.current !== null && d.deployed !== d.current
return (
<Text wrap="truncate-end">
<Text color={isBehind ? 'warning' : undefined}>{isBehind ? '↑ ' : ' '}</Text>
{d.name}
<Text dimColor>
{' '}
{d.configuration}
{d.deployed ? ` ${d.deployed}` : ''}
{isBehind ? ` → ${d.current} available` : ''}
</Text>
</Text>
)
})}
</Box>
) : null
// Auto mode refuses a background read nobody asked for unless it is allowed by name.
const help = refusal ? (
<Box flexDirection="column" borderStyle="round" borderColor="warning" paddingX={1} marginTop={1}>
<Text color="warning" wrap="wrap">
Auto mode refused the pane's read of the build's progress or the device's YAML. Add these to permissions.allow
in {settingsFile}, then the next build shows live:
</Text>
<Markdown text={`[${settingsFile}](file://${settingsFile})`} />
<Code source={allowLines(refusal.server)} />
<Box flexDirection="row" gap={2}>
<Button key="copy-rule" hotkey="c" onPress={press => $.ui.copy({ text: allowLines(refusal.server), surface: press.surface })}>
Copy the lines
</Button>
<Button
key="retry"
hotkey="r"
onPress={async () => {
// Allowed since? Try the reads again now rather than at the next build.
await $.state.set(blocked, null)
isUnsupported = false
configAsked = null
const running = (await $.state.get(build)).value ?? null
if (running && running.command !== 'logs') void loadConfig($, refusal.server, running.configuration)
void poll($)
}}
>
Retry
</Button>
</Box>
</Box>
) : null
const map = view ? deviceMap($.ui.resolve(e), view) : null
const isStage = e.surface === 'terminal' && isFxEnabled
const things = view ? thingsOf(view) : []
const stage = (state: Omit<ChipState, 'things' | 'hasWifi'>) => {
if (e.surface !== 'terminal') return null
const { Raster } = $.ui.resolve(e)
const columns = Math.min(512, width)
strip = { columns, state: { ...state, things, hasWifi: !!view?.rows.some(row => row.section === 'Network' && row.label === 'wifi') } }
return <Raster key="chip" columns={columns} rows={STRIP_ROWS} cells={chipFrame(Date.now(), strip.state, columns)} />
}
if (!current) {
if (!isStage) strip = null
return (
<Box flexDirection="column">
{isStage
? stage({
outcome: 'idle',
scene: 'idle',
percent: null,
words: view ? `${view.name} · ${things.length || 'no'} thing${things.length === 1 ? '' : 's'} attached` : 'dreaming of devices…',
endedAt: null,
})
: null}
{map ?? (
<Text dimColor wrap="wrap">
Nothing building. When Claude reads, edits or builds an ESPHome device, its map shows here, and a build's
progress as it runs.
</Text>
)}
{deviceRows}
{help}
{siblingHint}
</Box>
)
}
const parsed = progressOf(current.lines, current.command)
const progress = { ...parsed, uploadPercent: uploadShown(parsed, current) }
const took = elapsed((current.finishedAt ?? Date.now()) - current.startedAt)
const verb = { validate: 'Checking', compile: 'Compiling', upload: 'Flashing', logs: 'Logs from' }[current.command] ?? current.command
const done = { validate: 'Valid', compile: 'Compiled', upload: 'Flashed', logs: 'Read the logs' }[current.command] ?? 'Done'
const status =
current.outcome === 'running'
? `${phaseWords(progress, current.command)} · ${took}`
: current.outcome === 'ok'
? `✓ ${done} in ${took}`
: `✗ Failed after ${took}`
const isUploading = current.outcome === 'running' && progress.uploadPercent !== null
const isCompiling = current.outcome === 'running' && !isUploading && progress.compilePercent !== null
const kept = current.lines.filter(line => current.command === 'logs' || kindOf(line) !== 'debug')
// The latest couple of lines unless asked for all; a failure keeps a few more, where it explains itself.
const tail = isFullLog || current.command === 'logs' ? kept.slice(-rows) : kept.slice(current.outcome === 'failed' ? -6 : -LOG_LINES)
// The chip on the bench: a Raster, which only the terminal draws. Not for a logs read.
let chip = null
if (isStage) {
// The scene follows the build, not the command: a flash compiles first, then uploads.
const isUploadPhase = current.command === 'upload' && (progress.uploadPercent !== null || progress.phase === 'uploading')
const scene: Scene =
current.command === 'logs' ? 'logs' : current.command === 'validate' ? 'validate' : isUploadPhase ? 'upload' : 'compile'
const words =
current.outcome === 'running'
? `${scene === 'upload' ? 'flashing' : scene === 'validate' ? 'checking' : scene === 'logs' ? 'listening to' : 'compiling'} ${current.configuration}${(scene === 'upload' ? progress.uploadPercent : progress.compilePercent) !== null && scene !== 'logs' ? ` · ${scene === 'upload' ? progress.uploadPercent : progress.compilePercent}%` : ''}`
: current.outcome === 'ok'
? `✓ ${current.configuration} ${done.toLowerCase()}`
: `✗ ${current.configuration} failed`
chip = stage({
outcome: current.outcome,
scene,
percent: scene === 'upload' ? progress.uploadPercent : progress.compilePercent,
words,
endedAt: current.finishedAt,
})
} else {
strip = null
}
Licence text (MIT)
MIT License Copyright (c) 2026 Andrew Lyeklint Hancock (Vortitron) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
How to build this: Pane (panel), Deny a tool call
What its code calls
env varstool callsrememberscalls tools
What its code shows
Read from the source at commit 481600983d53 on 2026-10-11. The first group decides whether a mod is listed; the rest is for you to weigh. A later commit is not read until the next crawl.
| Decides the listing: code you can check | |
|---|---|
| Entry read | Every module hooks/hooks.json names was read.claude-plugin/vome-esphome/hooks/register.tsx |
| Parses | Every file parses as TypeScript or JavaScript.4 files parsed |
| All its code is in the mod | Every import is a file of the mod or the engine's own module; no packages, no require.all its code is in the mod |
| Readable | No minified lines, no eval or new Function, no import of a computed path, no encoded blobs.no minified code, no eval, no encoded blobs |
| Calls in the open | Network and programs are reached as $.http.fetch and $.process.run in place, never passed around.every call outside goes through $ in the open |
| For you to weigh before installing | |
| Where it draws | The terminal, the desktop app, both, or nothing (hooks only: a guard or a prompt rewriter), as its code says. Shown, never a reason to leave a mod out.draws in the terminal and the desktop app, the same in both |
| Install line | Whether its repository's own .claude-plugin/marketplace.json lists it, so it installs from that marketplace with the lines on its page.listed in its repository's .claude-plugin/marketplace.json: installs from there |
| Programs on Windows | Whether every program it starts through $.process exists on Windows (tail, date, open, osascript, /usr/… do not).runs no program a Windows PC lacks |
| Network | Whether every fetch names its https host in the code.no network |
| Programs | Whether every program it starts is named in the code and is not a shell, an interpreter or a network tool.starts no programs |
| Reads and sends | Whether it both reads something of yours (files, environment variables, the transcript, settings) and reaches outside (the network, an MCP server, another session, telemetry).reads environment variables and reaches an MCP server |
| Keys in the source | Whether the source holds what looks like an API key or a private key.no keys in the source |
| Licence | An open licence (MIT, Apache-2.0, BSD, ISC, Unlicense, 0BSD, CC0) with its text lets ModsCode show its code; otherwise the code is linked.MIT |
| Settings hooks | Hooks declared in hooks/hooks.json or plugin.json beside the module: a command (a shell when it has no args), an HTTP request, an MCP tool or a model prompt at an event. They run outside $.no settings hooks: its function hooks alone |
| Servers it ships | MCP servers (a program, or a URL; a headersHelper is a shell command; a .mcpb bundle is unpacked at run time), LSP servers, monitors (a shell command for the whole session) and bin/ (on the PATH of the Bash tool).ships no MCP or LSP server, no monitor, no bin/ |
| Skills, commands, agents | What its Markdown declares beyond text: allowed-tools granted for the turn, hooks added when a skill is invoked, a command run before Claude reads the skill.no skills, commands, agents or workflows |
| Tools and MCP | Whether every tool it calls through $.tool.call and $.mcp.call is named in the code, and none is a shell (Bash through the tool runs a shell without $.process).claude-plugin/vome-esphome/hooks/register.tsx:532 an MCP tool named at run time; claude-plugin/vome-esphome/hooks/register.tsx:596 an MCP tool named at run time |
| Asks of the model | Completions it runs ($.model.complete, fork, classify), subagents it spawns, prompts it submits as you, and the tools, commands and agents it adds.adds command esphome |
| Events it hooks | By what a hook there can do: gates (refuse a tool call, a prompt, a setting, another plugin), shapes (what the model reads: the system prompt, tool descriptions, each request), reads (your input, the events of the settings hooks, every event with *), and the rest.gates: plugin.register, command.run (esphome), tool.call · also: session.start, ui.render (Pane) · timers: clock.every |
| Reads, by name | The environment variables and files it names, and whether it reads the transcript, settings.json, the prompt box or the mouse selection.env: CLAUDE_CONFIG_DIR, HOME |
| Writes, by name | The files and environment variables it names, and whether it changes settings, the prompt box, the clipboard, the conversation (a row the model reads) or another session.the clipboard |
This is a reading of the code text, not a security review: it does not run the mod, and it cannot see what a program the mod starts does. The check before installing is yours. How mods are chosen
Install it
Check it yourself before you install it. Mods run unsandboxed, with your permissions, and ModsCode does not vouch for what this code does. Read its code (or run claude plugin validate . in its folder), weigh what it reaches, and install the commit you read.
From its marketplace
Its repository is its marketplace. Add that marketplace (in the terminal with these commands, or in the desktop app's plugin settings) and install the mod from it:
/plugin marketplace add Vortitron/home-assistant-mcp/plugin install vome-esphome@vome/reload-pluginsThis installs the marketplace's latest commit, which may not be the one read here (481600983d53). Compare them before you install. /reload-plugins loads it into a session that is already open.
Try the commit ModsCode read
No marketplace needed. In a terminal, clone the repository, check out the commit read, validate the mod, and load it for one session:
git clone https://github.com/Vortitron/home-assistant-mcpgit -C home-assistant-mcp checkout 481600983d53bce705fe68cb00361ee150a68171claude plugin validate home-assistant-mcp/claude-plugin/vome-esphomeclaude --plugin-dir home-assistant-mcp/claude-plugin/vome-esphomeThe validate line lists the events the mod hooks and what it asks Claude Code to do, without running it. The last line loads the mod for this session only and writes nothing to your settings. If the author has rewritten history, the commit may no longer exist.
Ask Claude about it
With the ModsCode connector added, Claude can read this mod's code and what it reaches, and build on them. Ask it like this:
Read the ModsCode mod "vortitron-vome-esphome" with its code and make me one like itSearch them from Claude: the MCP connector
Similar mods
- answer-paneVedant Andhale★ 4
- chimaera-ui-probemartinappberg★ 4
- desktop-markdown-readerYash Thakker★ 3
- mdviewAnji Xu★ 3
- human-tasksAndrew Stephenson★ 2
- pr-commentsaguiddir★ 2
More from this repository
Badge for your README
If this is your mod, paste this into your README. It links to this page.
[](https://modscode.com/claude-mods/mods/vortitron-vome-esphome/)