Pytxo

Pytxo Desktop is the optional control UI. It has three destinations — Work, History, and Setup — plus a workspace switcher in the title bar and an approvals overlay. It is not a multi-terminal IDE.

Download

Get installers from pytxo.com/download or GitHub Releases (current release: v1.2.1):

Platform	Installer
Windows x64	`pytxo-desktop-windows-x64.msi` (also a setup.exe on the releases page)
macOS / Linux	No v1 binary yet; the GitHub Actions multi-OS Desktop matrix is currently account/billing-blocked

The v1.2.1 Desktop release is deliberately Windows-first until the GitHub-hosted multi-OS matrix completes. If those jobs fail, only the Windows MSI is claimed as v1.2.1. Do not treat older macOS or Linux Desktop artifacts as v1.2.1 builds.

Prerequisites

Install the CLI and confirm pytxo doctor passes.
Install the Desktop package for your OS.
On Linux AppImage: mark executable (chmod +x ...AppImage) before launch.

First session

Trust a folder: pytxo trust orbit (or pick a profile in the Desktop trust flow).
Initialize config in the repo: pytxo init.
Open that repo in Desktop. It becomes the active workspace in the title bar.
Open Setup → Agents and confirm at least one installed agent has an active vendor session.
On Work, choose New run, describe an outcome, inspect the plan, then Run.

Desktop can also create the bundled Approval risk demo from onboarding or Setup → Workspaces. Its baseline tests run without model credentials; dispatching the run uses the agent CLI selected in New run.

What you should see

Work — the run ledger by wave on the left, the commit boundary and its enforcement receipt on the right
History — every run with its outcome and Apply state, and the boundary panel for the selected run
Setup — Providers, Workspaces, Agents, Appearance, Keyboard, Voice, Privacy, and Account
Approvals — an overlay from the title bar: evidence, consequence, then Apply or Discard
Run Review — the exact package a finished run prepared, reached from History

Agent sessions and API providers

Pytxo does not ask for ChatGPT, Claude, or other vendor passwords. Agents detects installed CLIs and can launch their official sign-in command:

ChatGPT subscription access is represented by the vendor-owned Codex CLI session.
Claude subscription access is represented by the vendor-owned Claude Code session.
Cursor Agent, OpenCode, Gemini CLI, and Aider keep their own login or provider setup.

Direct API keys are separate. Configure those under Setup → Providers; Desktop shows only configured/not-configured state and never returns key values to the webview.

Build from source

If you are contributing to Desktop itself, see Contributing. End users should use the installers above.

Desktop setup