Plugin idea: "Remote Control" — drive a local code-puppy session from your phone

[vggg]

Hi @mpfaffenberger — first, thanks for code-puppy; the plugin/callback architecture is a joy to build against.

Idea: a remote_control plugin that lets you monitor and steer a locally running code-puppy session from another device (phone/browser) — see proposed file changes, approve/reject them remotely, and send messages back — similar to Claude Code's recent "Remote Control" feature, but local-first and transport-agnostic.

I've been mapping it against the codebase and it looks like it can be a pure plugin, no core changes, because the seams already exist:

• Approve/reject → the file_permission and run_shell_command hooks (relocate the decision to the remote surface, return it).
• Streaming output → the existing frontend_emitter plugin (its docstring already anticipates "an embedder … a WebSocket backend").
• Lifecycle / "task done" push → agent_run_start / agent_run_end.
• Command → custom_command for /remote-control.
• Reconnect/resume → dbos_durable_exec (opt-in).

The design keeps the transport pluggable and outbound-only (no inbound ports): a small RemoteControlTransport interface with swappable backends — a chat-app bridge (Telegram/Discord = relay + UI + push, lowest friction) first, and a self-hosted FastAPI+WebSocket relay (uvicorn is already in the tree) for richer diffs.

I've got an inert scaffold + a runnable Telegram approve/reject spike working locally already. Before I invest further, two questions:

1. Interest / fit — would you welcome this as a plugin contribution? Or is something like it already planned/underway?
2. Stability of the approval seam — is file_permission (and the get_user_approval flow) a stable extension point you're comfortable having a plugin build on, or is it likely to change? Anything you'd want me to avoid coupling to?

Happy to share the design doc and open a draft PR for the scaffold if useful. Either way, thanks for considering it.

[mpfaffenberger]

Hey there @vggg, check out https://github.com/mpfaffenberger/openpup - this is kinda what you're thinking right?