Repository navigation
Research Pilot 0.6.10
Research Pilot 0.6.10 is a reliability release. Research runs no longer stall on experiments that can never report back, a delegated reviewer survives long quiet stretches, and a run's cost limit now holds even when several reviewers work at once. Terminals reattach with their colours and state intact, and phone attachments are stored privately.
Research runs
- A run no longer waits forever on an experiment whose status can never be refreshed, such as a backend that is no longer configured or has changed version. The coordinator is woken once with the reason, so it can re-run or report the job. When a backend is only temporarily unreachable, the run keeps waiting without spending model calls and tells you why.
- A delegated reviewer that is thinking for minutes inside one request is no longer mistaken for a stalled one. If a checkpoint was requested during such a quiet stretch, it is withdrawn once that reviewer resumes. Hung or looping sub-agents are still stopped by the overall time limit.
- The run's cost limit now holds with parallel reviewers. At most one reply's worth can go over the limit, however many requests run at once. Requests whose cost was never reported count at their maximum possible cost for the limit. A request that only has to wait for others to finish waits up to a minute instead of reporting the budget as spent.
- A run can no longer close as answered after an accepted code audit or design review behind its evidence was withdrawn.
Terminals
- Reloading the window, or opening a workspace in a second window, now restores each Claude and Codex tab faithfully. The screen, the most recent 3000 lines of history, colours, cursor, and terminal modes all come back. Stray fragments such as
36;231;221mno longer appear at the top of the history. - A terminal that hit an error while being shown now keeps following window resizes.
Phone and attachments
- Photos, files, and pasted images are now stored in
~/.pipilot/attachments, private to your account, instead of the shared temporary folder. Files older than 30 days are removed, and the folder is kept under 1 GB. - Two files with the same name no longer overwrite each other. Long names keep their extension, and long non-Latin names no longer fail to save on Linux.
- Uploads are written to disk as they arrive rather than held in memory. A file over 25 MB is refused on the phone before it is sent, and the phone now shows the size limit instead of a generic "upload failed".
Settings and the PI agent
- Saving Settings no longer resets the PI reasoning effort.
- Endpoints and API keys saved in Settings reach PI sessions in every window, including sessions started from the phone, without interrupting them. Web search picks up a newly saved Brave key immediately.
- The Default model list follows the self-hosted models editor as you edit it. If the saved default no longer exists, the list says what will happen instead of showing a different model.
- Self-hosted model entries edited by hand in
config.jsonthat cannot be used are kept as written and listed in Settings with the reason, instead of being deleted by the next save. - Form fields have a clearly visible edge in every theme, at a contrast of at least 3:1. Panel dividers stay quiet.
Memory
- A project memory saved again under its title is treated as current, instead of staying hidden because it had once been replaced.
Install or upgrade
Finish active tasks and quit Research Pilot before replacing the application. Research data remains separate from the application under ~/.pipilot by default.
| Platform | Recommended package | Alternative |
|---|---|---|
| macOS · Apple Silicon | mac-arm64.dmg | mac-arm64.zip |
| Ubuntu/Debian · Intel / AMD 64-bit | linux-amd64.deb | linux-x86_64.AppImage |
| Ubuntu/Debian · ARM 64-bit | linux-arm64.deb | linux-arm64.AppImage |
Windows and Intel Mac installers are not included. Prefer the deb on Ubuntu. AppImages on Ubuntu 24.04 require libfuse2t64; arm64 additionally requires zlib1g-dev. Older Ubuntu releases use libfuse2. If Chromium sandbox setup prevents AppImage startup, use the documented --no-sandbox fallback.
For Claude Code or Codex sessions, install the corresponding CLI and sign in once. No separate Node.js installation is required for Research Pilot itself. Electron remains at 31.3.1 in this release.
Detailed installation, permissions, and API setup guide.
Agent permissions
Desktop and phone launch Claude Code with --dangerously-skip-permissions and Codex with --dangerously-bypass-approvals-and-sandbox. Agents can run commands, modify or delete files, and access the network with your OS account's permissions without per-action approval. Codex's own sandbox is disabled. This does not grant administrator privileges or bypass OS access controls. Use trusted workspaces and tasks, and keep backups of important files.
Download one of the six named application packages above. GitHub's automatic Source code (zip) and Source code (tar.gz) entries contain the public README snapshot, not the application source or an installer. The named mac-arm64.zip asset is the packaged Mac application.
Release validation
For 0.6.10, 1062 automated tests passed on the shipped code, together with Electron typechecking, the production build, release size and dependency budgets, and the end-to-end demo. Every fix in this release has a regression test that fails on the previous code. The shipped bundles were checked to contain the new code.
The macOS application and DMG passed Developer ID signature, Apple notarization, stapled-ticket, and Gatekeeper checks. The applications inside both the DMG and the ZIP report version 0.6.10 and pass signature and stapled-ticket validation.
Both Linux debs were installed in clean Ubuntu 24.04 containers. Each installed the intended ALSA provider, set the Chromium sandbox permissions, shipped the native terminal library for its architecture, and started the packaged data service with appVersion 0.6.10. Both AppImage payloads passed the same architecture and service checks. The arm64 package was extracted with its own runtime. The x86-64 payload was extracted directly, because its AppImage runtime cannot execute under Apple Silicon Docker emulation.
Packaged graphical startup was not exercised on either platform. The terminal reattach, reviewer watchdog, and concurrent cost-limit changes were verified by tests against the real modules, not in a live app session. The x86-64 checks ran under emulation rather than on physical x86-64 hardware.