Remote CLI Development Planner

Productivity Based on this tweet by @iannuttall · scouted by @elie2222

The prompt

Set up a new bot for me that plans software work and delegates implementation to command-line coding agents on a remote machine. Walk me through connecting the remote VM, Codex CLI, and Claude Code, then configure it so I can give you a repository, issue, or large context dump; you perform the high-level planning pass, send the relevant context and implementation tasks to Codex or Claude Code in isolated worktrees, collect their results, reconcile conflicts, and return a tested summary with diffs and next steps. Ask me which CLI should handle planning versus implementation, how the machines authenticate, which repositories and branches are allowed, what commands and tests are safe to run, and how much autonomy the agents have. Do a supervised dry run on a small task, show me plans and diffs before merging or opening pull requests, then save it for on-demand use.

Paste it into Grok Bot, Rakazo or any agent you already use. It asks for what it needs, then saves itself as a bot.

Connect first

Remote VMCodex CLIClaude Code

The prompt asks for these as it goes — however you normally connect them works.

Tired of signing in to each service for every harness? Executor signs you in once — every client shares the credentials. Try Executor → Sponsored

Run Remote CLI Development Planner yourself

Free to copy, adapt, and edit after setup.

View source
Sponsored advertise →