Polystro logoPolystro
FeaturesPricingDocsCompare
Log inSign up

Docs

Desktop product docs, organized as a docs tree instead of a marketing page.

Need full docs search? Use Cmd+K or Ctrl+K.

Getting Started

Overview

Installation

CLI Setup and Auth

Core Concepts

Workstreams and Isolation

Browser and Services

Worktree Modes

Workflows

Agent Workflows

Sessions and Layout

Planning and Ideation

Review and Merge

Search and Shortcuts

Imported History and Project Actions

Operations

Services and Previews

Environment and Routing

Automation and Remote Access

Scripts vs Automations

Command Routing and Slash Commands

Local Viewer

Settings and Integrations

Updates, Licensing, and Support

Troubleshooting Index

Permissions and Safety

HomeDocsOperationsLocal Viewer
Operations

The local viewer keeps a session moving when you are away from the full desktop shell.

Polystro’s viewer model is designed for continuation, not for replacing the main app. It can open locally on loopback or expose a LAN share link, then let a paired device reconnect to the desktop runtime later.

What The Viewer Is

The local viewer is a browser-accessible surface tied back to the desktop host. It exists so you can check progress, answer a question, or send the next prompt without the full desktop app in front of you.

Open and Share

The desktop app can open the viewer locally on loopback or generate a share link for LAN access when available. The LAN path is meant for same-network continuation, not for turning Polystro into a general internet-hosted service.

Pairing by QR or Link and PIN

First-time enrollment can happen by scanning the QR code from the desktop app or by pasting the Mobile/Web link and entering the PIN shown in the same dialog. Once paired, the device can use its stored credential to reconnect later without repeating the initial enrollment step.

Trusted Devices

Trust is explicit

A device becomes trusted only after a completed pairing flow.

Reconnect without re-pairing

Trusted devices can request a fresh viewer session later.

Manage from Settings

Trusted devices are listed in the settings surface and can be revoked individually.

Desktop remains authoritative

The trusted device is a continuation client, not the primary runtime.

Limits and Expectations

What the viewer is not

The viewer is not meant to replace the full desktop workflow with its multi-pane shell, editor handoff, service control, and review surfaces. Use it to keep a session moving, not to turn the product into a fully remote IDE.

Previous

Command Routing and Slash Commands

Create custom commands, import prompt files, route commands to models, and test routing policies.

Next

Settings and Integrations

General behavior, browser/layout settings, CLIs, MCP, skills, voice, notifications, and keybindings.

On This Page

What The Viewer IsOpen and SharePairingTrusted DevicesLimits
Polystro logoPolystro

The desktop app for running parallel agents without port, browser, or git collisions.

Product

  • Features
  • Pricing

Resources

  • Docs
  • Compare

Company

  • Privacy
  • Terms

© 2026 Polystro. All rights reserved.

Built for multi-agent software development on desktop.