PytxoDesktop setup
Connect your coding agents, choose a repository, and get ready for your first task.
What you need
- Windows x64 and Pytxo Desktop. The separate Pytxo CLI is optional.
- At least one agent CLI installed and signed in through its own sign-in flow: Codex, Claude Code, Cursor Agent, OpenCode or Antigravity.
- A Git repository with its build and test dependencies installed.
Local Core needs no Pytxo account. Agent access and usage costs belong to your agent accounts.
Complete the welcome steps
- Welcome: choose Get started.
- Agent: Pytxo lists the agents it found. Finish any sign-in, then Check again. Opening a sign-in window alone does not confirm access. OpenCode needs a provider stored with
opencode auth login; agents do not receive API keys from your shell. - Project: choose Select folder, or Try the guided example.
- Ready: choose Enter Pytxo Desktop.
You can skip agent or project setup and finish it later. Skipping does not make a run ready.
Choose your repository
If you skipped the folder step, choose Add workspace. Select your Git repository and review its requested permissions. New projects start in the Orbit permission profile with local PTY execution.
Open Setup → Agents & permissions to recheck your agents. A detected installation and a working sign-in are separate checks.
Then open Work → New work and follow First mission.
Find your way around
| Place | Use it to |
|---|---|
| Work | Describe a task, review its plan, follow execution, and open Review changes |
| History | Return to a recorded run and check whether its changes were applied |
| Setup | Manage workspaces, agent access, appearance, and updates |
| Approvals | Respond to runtime permission requests; these do not apply repository changes |
If you cannot run
- Agent missing: follow its install guide, then recheck in Setup.
- Sign-in required or unknown: complete the vendor sign-in, then check again.
- Plan blocked: read the reason beside Run. The preview requires Orbit and
execution_backend = "pty". After changing configuration, build a fresh plan. - No checks found: add a command that already works in your project under Additional verification commands before building the plan.
Changing the default permission profile does not change an existing repository's trust or configuration. See Troubleshooting.
Updates
In the preview, use Setup → General → Check for updates. Finish active work and resolve any reported recovery issue before installing. After reopening, check the running version. An installer opening does not confirm that an update finished.
A local preview can be newer than the public download. Check the offered version before using Manual download.