Native Sessions stay native
Transcript, tools, reasoning, permissions, memory, compaction and resume semantics remain owned by the harness that actually created the Session.
Harness Remote 3 · Official 3.0 release
Your sessions.
Any coding agent. Any device.
A local-first control plane for native AI coding-agent sessions. Start work in your normal CLI, pick up the same native Session remotely, and hand the work to another agent when it is the better tool for the next step.
Apache-2.0 · Your code, credentials and subscriptions stay on your machines.
Codex CLI
Claude Code
OpenCode
Oh My Pi
PI
Harness Remote 3 · native sessions
Native Session live
Machine → Project → Session
One control plane, not another agent
Stop rebuilding your context every time the best agent changes.
Coding agents are becoming specialized. The hard part is no longer choosing one forever — it is keeping the work coherent while moving between them. Harness Remote makes that continuity explicit without flattening every agent into the same fake interface.
Start outside. Continue inside.
Begin in your normal coding-agent CLI. Open Harness Remote later and discover, observe or continue the native Session instead of importing it into a proprietary conversation model.
Hand off without pretending
Continue with another harness using explicit objective, decisions, unresolved work and lineage. No claim that hidden vendor context magically transfers between agents.
01 · START
Use your normal CLI
Work with Codex, Claude Code, OpenCode, OMP or PI where your project already lives.
→02 · PICK UP
Open it remotely
Find the native Session from desktop, web or Android and follow the real activity.
→03 · HAND OFF
Choose a better agent
Create a linked native Session with explicit context for the next coding agent.
→04 · RETURN
Keep the lineage
See which Session did what, return to it later, and keep the project history intelligible.
Session-first architecture
The Session is the product identity — not an implementation detail.
Harness Remote 3 uses a deliberately simple user-facing model: Machine → Project → Native Session. The control plane surrounds the Session; it does not replace it.
✓Preserve each harness's real transcript and behavior.
✓Discover sessions that were started outside Harness Remote.
✓Keep source → target handoff lineage explicit and inspectable.
✓Avoid lowest-common-denominator controls the harness never advertised.
auth-refactor
workstation
OpenCode · Session A
Explore the failing authentication path
Continue with Codex →
Codex CLI · Session B
Implement and validate the fix
Continue with Claude →
Claude Code · Session C
Independent review · native context
A clean ownership boundary
Let the coding agent be the coding agent.
Harness Remote owns the durable coordination layer. The harness keeps ownership of the behavior it already knows how to perform correctly.
Owned by the native harness
The work itself
Transcript
Reasoning / activity
Tool execution
Questions
Permissions
Context / memory
Compaction
Resume semantics
Owned by Harness Remote
The control plane
Machines
Projects
Session discovery
Remote control
Capability discovery
Handoff lineage
Reconciliation
Desktop / web / Android
Local-first by design
Your machine stays the place where the work is real.
Source code, repositories, coding-agent CLIs, credentials, provider subscriptions and native Session persistence stay on the computers you control. Harness Remote gives you a remote surface over that environment instead of asking you to migrate it.
development-machine · connected
Repository~/Software/project
Source codelocal
Agent credentialslocal
Native sessionslocal
Remote surfaceHR3
Use a trusted LAN or VPN for remote access. Harness Remote is a control plane, not an operating-system sandbox and not a hosted inference proxy.
Harness Remote 3.0 is here
Help shape Harness Remote 3.
Harness Remote 3.0 is the official Session-first release. Native coding-agent Sessions, remote control, reconnect recovery and explicit cross-agent continuation now ship from main.
Get Harness Remote 3.0
Clone Harness Remote and use the official v3.0.0 tag, or follow main for the current stable release line.
git clone https://github.com/giuliastro/harness-remote.git
cd harness-remote
git checkout v3.0.0
Harness Remote 3
Keep ownership of your tools. Keep ownership of your sessions.
Change coding agents without turning your real project history into a collection of disconnected chats.