
I’ve mentioned my “AI Diplomacy” project in a previous post. It started with a Claude Remote Session, but once the initial implementation was done, I found myself needing local access more often, so I had set the remote session aside for a while.
Then, during lunch today, a thought popped into my head.
‘If my OpenClaw AI assistant, N.I.C.K., can run command-line instructions on localhost, doesn’t that mean it can also start a Claude Code remote session for me?’
I opened Telegram and sent a message to N.I.C.K.
> “Can you go into the `~/Projects/ai-diplomacy` directory and run `claude remote-control` as a background job?”
After a moment, the response came back.
> “Yes! I’ll run `claude remote-control` in the background.”
> “The directory doesn’t exist. I’ll check the path.”
> “Ah, the directory name is `ai-deplomacy`! (Spelling error)”
> “Background process started! ✅”
Wow. I hadn’t even realized there was a typo in my project’s path all this time. It’s a little embarrassing, but the fact that it figured out what I meant… moments like these make me think it’s pretty smart.
I opened my laptop, launched the Claude app, and selected the ‘Code’ tab. Sure enough, a new, live remote session was listed—one that wasn’t there before.
I had to be sure.
> “What’s your current working directory?”
> “The current working directory is `/Users/kirinchoi/Projects/ai-deplomacy`.”
It actually works.
Well, I’ve confirmed it’s possible, and that’s enough for today. I opened Telegram again to shut it down.
> “Okay, I’ve confirmed what I needed to. Go ahead and kill that background process and let me know when it’s done.”
> “Understood! Sending the kill signal.”
> “Termination complete! ✅”
A clean shutdown, too.
This is going to be incredibly useful.