wirepane

What it hooks into

From an automated scan with claude plugin validate, not a security review. Mods run with your permissions; read the code before installing.

Events

session.startsession.endcommand.runui.rendertool.call

API calls

$.clock.after$.clock.now$.clock.sleep$.command.register$.config.list$.config.set$.env.get$.fs.exists$.fs.list$.fs.read$.fs.write$.process.run$.process.spawn$.prompt.fill$.session.id$.session.root$.state.get$.state.set$.store.get$.store.set$.tool.register$.ui.copy$.ui.log$.ui.open$.ui.resolve$.ui.status$.ui.toast

Draws

Pane

Can see

mcp__wirepane__track_domains callsmcp__wirepane__list_rules callsmcp__wirepane__add_rule callsmcp__wirepane__update_rule callsmcp__wirepane__remove_rule callsmcp__wirepane__resume_request callsmcp__wirepane__send_ws_message callsmcp__wirepane__close_websocket callsmcp__wirepane__list_requests callsmcp__wirepane__get_request callsmcp__wirepane__diagnose callsmcp__wirepane__search_requests callsmcp__wirepane__wait_for_request callsmcp__wirepane__replay_request callsmcp__wirepane__diff_requests callsmcp__wirepane__export_har calls

Reach

level 2 of 3 other: $.process.spawnother: $.state.getother: $.state.setruns processeswrites fileschanges configdrives Claudewrites the prompt boxreads filesreads env varspersists statedraws