homie is a Claude Code workflow mod by homie-rocks.
Draws a studio band and panes for a game build, its rooms, and parallel parts, and holds production deploys, paid media calls, and edits to protected files.
It runs inside the Claude Code process. The side panel is only what the author's README names. Read the repo before you install, or run claude plugin validate on the plugin folder.
Version
0.58.14
License
Apache-2.0
Repo stars
7
Last change
2026-10-27
What it can reach
Draws in the session
Holds a command
Reads this turn's file edits
Sees tool calls
Reaches the network or an outside service
Calls another program on this machine
Inside a studio only, a folder with studio.json at or above where Claude Code runs; nothing shows outside one. The install line needs Claude Code 2.1.275 or later and the mod 2.1.287 or later. It asks you to confirm the marketplace, then you pick a scope. From a terminal: claude plugin marketplace add homie-rocks/homie, then claude plugin install homie@homie. The plugin also brings Homie's skills and its MCP server at homie.rocks/mcp, and a studio runs on your own Cloudflare account, on the free plan. The guards hold a call in Claude Code's own question dialog, even in bypass-permissions mode: edits to files studio.json protects, production deploys, paid media calls past the budget, and changes to the studio's Cloudflare account. Secrets come out of tool output before Claude reads it. /studio opens the Studio pane, /parts the parts pane, and /arcade plays a Homie game while Claude works, which needs Node 22 and Google Chrome. Each part has a switch in /config.
The marketplace name is homie, and it holds only this plugin; the same folder also installs in Codex and Grok Build. Following a game build from plan to deploy is why this page files it under workflow. vercel-deploy-status draws the linked project's Vercel deploys in a band. guard-pack asks before a production deploy and redacts secrets in a tool result. This one does both for a Homie studio, with a Studio pane of the build, its live rooms, art direction, and stats, and holds on paid media calls and Cloudflare changes too. In the source, the holds are tool.call hooks, and it has no tool.check hook, so it never approves a call.
Demo
Screenshot of the author's GitHub page.
What it hooks into
session.startWhen a session starts
prompt.submitWhen you send a prompt
session.endWhen a session ends
command.runWhen you run its slash command/studio/build/rooms/play/watch/codex/deploy-status/perf-numbers/parts/arcade/look/lock/assets/cast/clips/lineup/rights/feedback
tool.callAround a tool call, where it can hold oneEditWriteMultiEditNotebookEditBash
turn.completeWhen a turn ends
ui.renderDraws into the sessionAbovePromptPaneAskUserQuestionToolUseToolResultToolGroup
ui.messageAdds a message to the session
ui.closeWhen its pane closes
Read from the on() calls in its hook modules. Open its source under Files to check what each one does.
Files
The author's README and source, 4 files. They load when you open them.