Paper and code are local
Use the macOS desktop app if you want the simplest folder picker workflow.
Use Desktop App
DraftPilot
Quickstart
DraftPilot can run as a desktop app, a local CLI, or a VM-backed CLI tunnel. Start with the path that matches where your paper and code live.
curl -fsSL https://jerrinbright.com/draftpilot/install.sh | bash
powershell -ExecutionPolicy Bypass -Command "irm https://jerrinbright.com/draftpilot/install.ps1 | iex"
Use the macOS desktop app if you want the simplest folder picker workflow.
Use Desktop AppUse the CLI with SSH. It starts DraftPilot beside the remote files and opens a local tunnel.
Use VM WorkflowUse CLI JSON output. It is predictable, parseable, and works well from Codex context.
Use CLI--host, --paper, --main-tex, and --codebase.For multi-device work, keep the paper folder in a private GitHub repo. Clone it wherever you want to write, launch DraftPilot beside that clone, then use normal Git commands to move changes between your laptop, VM, and collaborators.
git clone git@github.com:you/paper.git
cd paper
draftpilot launch --paper . --main-tex main.tex --codebase ../research-code --open
DraftPilot does not need your paper to be public. GitHub stores the project history; DraftPilot opens the local clone and writes to real files on that machine.
main.tex is only the default.draftpilot update. Packaged desktop apps check the app update feed.