Grok Botが、隣で実装を走らせた
Tell the orchestrator the local repo. It opens the folder, runs a cloud agent, and merges the result onto your machine.
For
People who already code in a local folder and are tired of remote agents that only bring a patch back.
When you're done
One spoken name. The repo opens. Implementation continues. The merge lands on the desk.
How
- 01 Say the local repo name.
On the desktop app. Ask the orchestrator to open that folder.
- 02 Ask it to continue the implementation.
A cloud agent starts from that repo. You stay in one thread.
- 03 Merge back onto the desk.
The finished work lands in the same folder.
- 04 Keep the ask narrow.
This repo. This change. Not the whole machine.
Notes
What's good: the job is the same motion you already do. The catch: local reach is not wide open. Keep the ask narrow: this repo, this change, then merge.
Prompt
Open the local repository named [repo]. Continue the implementation that is already in progress. When the cloud agent finishes, merge the result back into that folder. Do not touch other repos.
Rewritten from 安曇むすひ / note.com
Related plays
Multi-Repository Dev Orchestrator 
I Just Tested (New) Grok Bot (Now I Understand the $200 Price Tag) kunchenguid/grok-ship: Turn your Grok Bot into a software factory. 
I’ve been using Grok Bot in early access for a little over a week now, and it has been a massive boost to my game dev workflow and my productivity in general. Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About