Cross-provider control

Switch agents without rebuilding your remote workflow.

Use one mobile control surface for Claude Code, Codex, OpenCode and Pi while preserving what makes each provider different.

Denshin showing a provider-aware coding-agent run
Before

A remote feature tied to one model vendor turns the supervision layer into another reason not to switch.

With Denshin

Denshin normalizes durable product primitives while every event keeps its provider and fidelity.

What changes in practice.

01

Common primitives

Conversation, work, runs, decisions, changes and provenance form the shared vocabulary.

02

No fake parity

A provider that does not expose a todo, decision or control does not receive a synthetic one.

03

Multiple adapter modes

Native events, transcripts and rollout data can coexist behind the same provider-free view model.

04

Raw escape hatch

Every supported agent still has the terminal behind it.

Your computer should stay. You should not have to.

Join the pilot