Harness Remote — Development skill for Claude Code
Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI.
How to install Harness Remote
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open giuliastro/harness-remote and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Harness Remote does
Native-session control plane for Codex, Claude Code, OpenCode, OMP and PI. Run, resume and hand off coding sessions across your machines.
Alternatives in Development
- Create Handoff — You are tasked with writing a handoff document to hand off your work to another agent in a new session 10k ★
- Zeron — A native control plane for Claude Code, Codex, Cursor, Devin and other coding agents 1.4k ★
- OpenSquirrel — For people who get distracted by agents 1.3k ★
README
Harness Remote
Your sessions. Any coding agent. Any device.
**A local-first control plane for native AI coding-agent sessions.**
Run, observe, resume and hand off work across **Codex CLI, Claude Code, OpenCode, Oh My Pi and PI** from desktop, web or Android — while your code, credentials, subscriptions and native Sessions stay on your own machines.
[](https://github.com/giuliastro/harness-remote/stargazers) [](LICENSE) [](docs/HARNESS_3_ROADMAP.md)

**Start in your CLI → pick it up from another device → hand it to a different coding agent → return to the native Session that did the work.**
Harness Remote lets you remotely run, observe and resume the coding agents already installed on your machines. When another agent is better for the next step, continue the work there with an explicit handoff instead of copy/pasting context into an unrelated chat.
**Harness Remote is not another coding agent.** It is the continuity and remote-control layer for the coding agents you already use, while their native Sessions remain the source of truth.
Why Harness Remote 3
AI coding tools are getting better fast — and the best tool for planning, implementation, debugging or review is not always the same one.
The problem is that every coding agent normally becomes its own island: its own sessions, transcript, controls, models and resume semantics.
Harness Remote 3 is built around a different idea:
Machine
Project
OpenCode Session A
└─ Continue with Codex
Codex Session B
└─ Continue with Claude
Claude Session C
Each Session remains **native to the harness that created it**.
Harness Remote adds the continuity
Related Skills
Mjolnir
Manage Codex, Claude Code, Muse Code, Kimi Code, Grok Build, and DeepSeek Harness with durable sessions, isola
Remote For Xirp
Remote For Xirp — mobile web control surface for the Xirp agent daemon: machines, projects, sessions, live tmu
Dsh Acp Plugin
Agentic Control Plane for DeepSeek Harness — policy-check every tool call before it runs
Takeoff
Create, resume, or clear a session hand-off baton (one per work line)
Fleet Handoff
/fleet-handoff — hand off across a context boundary, then auto-clear + resume
Jmunch Console
Local, opt-in control-plane GUI for the jMunch suite (config, index/watcher health, savings/ROI, sessions, age
Related Agents
VespeR
Control plane for Claude Code workflows: interactive sessions, agents, patterns, DAGs, and resumable context.
Paperclip Reviewer
Paperclip 2026.529+ governance-first integration platform code review specialist — control plane + adapters tw
Pipeman
Use this agent to push code to the remote repository after QA1's first gate passes, and to push follow-up fixe