Window layouts and project handoff
Pip 0.8.0 adds a Layout tool that tiles and arranges your windows, and a way to hand a project's working setup to another Pip on the same network.
Arrange your windows
The new Layout tab draws a map of each display before anything moves, with every window named by its app.
- Keep a display tiled as Halves, Main + stack, or Columns. Pip retiles as windows open, close, minimise, and move, and dragging one window onto another swaps their places. Which displays you tile is remembered for the next run.
- Arrange once to tile a display's windows a single time, without keeping that display tiled.
- Leave a window out of tiling, and let it back in when you want it placed.
- Open a project's windows together. When a project's server or agent is running and two of its windows are open, one click arranges them as Main + stack on the main window's display and focuses it.
- Put back a single window, or all of them, to where they were before Pip moved them, including after Pip restarts. Putting every window back stops tiling on all displays.
The grid
Turn the grid shortcut on, then press Ctrl+Alt+Shift+Space (⌃⌥⌘Space on a Mac) over any window to cover its display with a grid. Drag across cells, or move the block with the arrow keys and size it with Shift and the arrows, then press Enter to place the window. Esc puts the grid away. Choose a 4 × 3, 6 × 4, or 8 × 6 grid. The shortcut is off by default.
Layout is available on Windows and macOS. Pip only tiles on its own on a licensed machine, and never during Game mode. Stopping tiling and putting windows back stay available without a licence, so a lapsed licence never leaves your windows held or a grid on screen.
Hand a project to another machine
The new Transfer tab sends a project's working setup to another Pip on the
same network: the .env files, the branch with its unpushed commits, and any
uncommitted changes.
- Start a transfer from the Transfer tab, a project header, a Repositories
row, or the command palette. Choose the
.envfiles and whether to include the branch and changes, then create a six-digit code. - Share the code from the waiting screen, which shows how long the code has left, a copy button, and share buttons for WhatsApp, Telegram, Slack, Discord, email, and your system share sheet.
- Receive with the code. The receiving Pip finds the sender on the local network. If that is blocked, the sender's screen shows an address to type instead.
- Review before anything is written. The receiving Pip previews every file
first. A branch and its changes land in a new worktree beside the matching
clone, so your own checkout is never touched. For
.envfiles, Pip lists the key names that were added, changed, or removed, then offers to add only the missing keys or to replace the file, keeping a backup.
The code becomes a shared key and everything travels encrypted. A wrong code
reveals nothing, three wrong attempts end the code, and a code expires after
ten minutes and works only once. Pip shows the key names in your .env files,
never the values.
Receiving a transfer is free, including from the licence screen, so someone can receive a project before they buy. Sending needs a licence. Docker volumes, databases, and transfers over the internet are not part of this release.
Fixes
- Hardened an icon-rendering code path on Windows that security scanning flagged, and renamed misleading variables in the test suite. Neither affected a running app.
Installation notes
Apple has approved code signing for the macOS app, and a Windows certificate is still on the way. Until each signed build ships, your operating system may show a warning. Only continue if you obtained Pip from the official download page.
- Windows: choose More info, then Run anyway in SmartScreen.
- macOS: after attempting to open Pip, go to System Settings → Privacy & Security → Open Anyway and confirm.