Ptx

A local AI development workspace for real coding work.

Ptx gives Pi and OMP one calm desktop workspace for sessions, project context, scheduled work, and human review. It runs locally on macOS, Linux, and Windows; bring your own model account.

English | 中文

Download · Task workflow · Security · Contributing

• Two harnesses, one workspace — switch between Pi Work and OMP Work without losing running work.
• Local-first projects — open local folders and Git worktrees, then resume persistent sessions in context.
• Review before accepting — inspect messages, tool activity, Git changes, and browser evidence before work is accepted.
• Built for desktop — terminal, browser, voice, desktop pets, schedules, and keyboard-first navigation.
• English & 简体中文 — the interface ships with a built-in language selector.

The three-pane workspace keeps conversation, project context, and evidence together. Tool activity stays compact while the inspector exposes session progress, Git changes, browser tabs, and project files.

Create a schedule, inspect its next run and history, run it immediately, or pause it. Work remains tied to the selected project and harness.

Enable and review local capabilities without losing the security boundary of the selected harness. Ptx does not own harness authentication.

Ptx supports English and Simplified Chinese, along with light, dark, and system themes.

Use the switcher in the top-left corner to move between Pi Work and OMP Work. Ptx detects the harnesses installed on your computer and shows the ones that are ready. Refresh detection or set a custom executable path in Settings → Harness.

Each harness keeps its own projects, sessions, model list, provider visibility, and running work. Switching harnesses changes the workspace without stopping work already running in another one.

You only need one harness to get started:

• Pi is the base coding-agent harness in the Pi family.
• OMP adds its own plugins, commands, and approval controls.

The Tasks page is a free local preview for defining goals and acceptance requirements, reusing templates, choosing a project folder or worktree, and reviewing actual session tools and current Git changes. Execution ending only makes a task ready for human review.

See the task workflow guide and commercial validation playbook. No paid checkout is live; existing features remain free and the repository remains MIT-licensed.

The Capabilities page brings together packages, plugins, extensions, skills, prompts, and MCP servers. Ptx can manage local stdio MCP definitions for OMP and adapter-enabled Pi. Network MCP and authentication stay under the selected harness's direct control; those entries are visible but read-only in Ptx, with bounded definition-only removal available for cleanup. Discovery has an independent 2,500-definition-per-settings-file limit and reports an explicit warning before unrelated rows can be hidden.

Ptx does not keep its own MCP configuration. It reads and writes the definition files each harness already owns:

Pi has no native MCP support. Its definitions load through the third-party pi-mcp-adapter extension, so enable that adapter from the Capabilities page (or run pi install npm:pi-mcp-adapter) before a stdio entry takes effect. Open a new session after changing definitions.

A stdio definition uses the standard schema, and command / args must point at an executable on your machine:

{
  "mcpServers": {
    "example": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/server.mjs"]
    }
  }
}

Ptx also ships optional capabilities for native Ask User dialogs, controlled browser access, and TryCUA computer control when the separate CUA Driver is installed. Ask User and computer control are off by default.

• Dictate prompts with OpenAI, Groq, Deepgram, or a local whisper.cpp installation.
• Open the realtime voice companion to search, discuss work, and start a task in the selected harness.
• Choose an animated desktop pet that reacts while an agent works and carries realtime voice controls. Ptx includes the Orb and Ptx pets and can discover compatible Codex pets.

1. Install Pi, OMP, or both.
2. Sign in or configure a model provider through each harness's own CLI.
3. Download Ptx from GitHub Releases, or run it from source.
4. Add a project folder and start a session.

Ptx checks common install locations automatically. If a harness is missing, open Settings → Harness to refresh detection or choose its executable.

GitHub Releases provides a DMG and ZIP for macOS, common Linux package formats plus AppImage, and a Windows installer and ZIP. Installed builds check for updates shortly after launch and again every three hours; click the title-bar update indicator for a manual check.

Harness provider credentials stay with the harness. Optional voice keys are encrypted with the operating system's secure storage, and local whisper.cpp dictation needs no API key.

Use ⌘ on macOS and Ctrl on Linux or Windows.

The Queue and Steer shortcuts can be swapped in Settings → Harness → Message shortcuts.

Ptx is built around local projects and local harness sessions. It does not rewrite session history or take ownership of Pi or OMP credentials.

Remote pages open in a separate browser profile with Node access disabled. Project paths and desktop actions are checked in the main process, and third-party capabilities still run with your operating-system permissions. Review packages, commands, MCP servers, and projects before allowing them to act.

For suspected vulnerabilities, follow the security policy and do not post sensitive details publicly. See docs/security.md for the full technical security model.

You need Node.js 24.15.0 or newer and npm 12.0.2 or newer. The repository pins both versions, so installs made with a different toolchain fail rather than producing a subtly different build.

nvm install && nvm use
npm run toolchain:bootstrap

The bootstrap command verifies the exact size and SHA-512 of the checked-in npm archive, then installs it offline with install-time lifecycle scripts disabled into the invoked npm's configured global prefix, verifies the installed CLI and both tool versions against package.json and .nvmrc, and makes its shim available to subsequent GitHub Actions steps before dependencies are installed.

npm install
npm run dev

If node_modules/electron/dist is missing after installation, fetch Electron's platform binary before starting the app:

node node_modules/electron/install.js
npm run dev

npm install --ignore-scripts skips Electron's platform download and native-dependency rebuild. If you used it, recover with:

npm install --ignore-scripts
node node_modules/electron/install.js
npx electron-builder install-app-deps

node-pty is a native dependency. If Electron cannot rebuild it with your default Python environment, point npm at a Python installation with the required build tools:

export npm_config_python=/path/to/python3
npm install --ignore-scripts
node node_modules/electron/install.js
npx electron-builder install-app-deps

npm run typecheck
npm run check
npm test
npm run test:e2e
npm run build

See the validation guide for the source-of-truth checks and reproducible commands.

To make an installable local QA build, run the command for your operating system:

npm run package:mac:local-qa
npm run package:linux:local-qa
npm run package:win:local-qa

Build packages on their target operating system so native dependencies match the release.

Ptx is released under the permissive MIT License.