Pastey is a local-first desktop transfer and device workspace for moving text, files, and images directly between your Windows, macOS, and Linux devices on the same LAN. It uses encrypted local transport—no account system, cloud relay, remote storage, or analytics pipeline.
Bridge sessions are ephemeral. Devices join through nearby discovery or an 8-digit code; current session state can be burned when it is no longer useful. SQLite stores metadata, while payload bytes and decryption remain local to participating devices.
- Layer 1 — encrypted and reliable LAN transfer
- Layer 2 — factual device and link intelligence
- Layer 3 — transfer and control orchestration
- Layer 4 — Bridge sessions, peers, routing, and control transport
- Layer 5 — guided planning and bounded object workflows
Layers 1–4 form the non-AI Pastey core. Layer 5 adds one Rust-owned Bridge Plan lifecycle with four primitives: Search finds an object, Transform changes it, Transfer moves it, and Execute runs it. The immutable Plan, one requester approval, current-session binding, one-use grants, and attempt state are the only mutation or execution authority.
Ask Bridge normally uses a guided Search / Transform / Transfer / Execute Block Composer; natural-v1 providers are optional and advisory only. Search selects an object on an explicit Host. Transform records reviewed modification intent for that same logical object and conceptually advances its revision without moving it. Only an authored Transfer changes location. Execute records reviewed execution intent for the exact current revision without selecting a runtime. Capability observations never select an executor, add movement, or authorize a step.
Search and Transfer are currently executable. Transform and Execute are Plan-framework primitives only: they can be composed and reviewed, but attempts containing either fail closed until a future Agent layer supplies an implementation. Pastey Core deliberately does not define patch formats, mutation workers, runtimes, shells, process launch, or containment policy.
- Architecture and layer map
- Layer 1 — transfer
- Layer 2 — device intelligence
- Layer 3 — orchestration
- Layer 4 — Bridge
- Layer 5 — agent workspace
- Reference
- Development and release
- Product website
- Changelog
Download the latest release, or browse all GitHub Releases.
- Download the latest
.dmg. - Open the
.dmg. - Drag
pastey.appinto Applications. - Launch
pastey.
- Download the latest
.msior.exeinstaller. - Run the installer.
- Launch
pasteyfrom the Start menu.
Linux release artifacts are validated against Ubuntu 24.04 x86_64.
AppImage:
chmod +x pastey_*.AppImage
./pastey_*.AppImageDebian package:
sudo apt install ./pastey_*.debnpm install
npm run tauri:devFor local transfer-throughput testing, use the optimized dev-fast mode:
npm run tauri:dev-fastFrontend only:
npm run buildPackaged desktop app:
npm run tauri:buildPackaged desktop app with artifact audit:
npm run build:checkednpm run release:version -- X.Y.Z "Release Title"
git push origin main --tagsSee docs/development.md for the full release workflow.
Release builds write local diagnostics here:
- macOS:
~/Library/Application Support/pastey/logs/pastey.log - Windows:
%LOCALAPPDATA%\pastey\logs\pastey.log
Logs rotate at 5 MB and keep the last two rotated files. Agent Bridge lifecycle entries use bounded redacted structured fields and shortened references. Logs are audit mirrors only: they are never workflow state, consent, authority, or trust.
- macOS may ask for network access permission the first time you run active LAN transfers.
- Windows Defender Firewall may prompt for local network access when the temporary transfer server starts.
- Linux release validation currently targets Ubuntu 24.04 x86_64.
- Global shortcut defaults to
Ctrl+Shift+Von Windows andCmd+Shift+Von macOS.
- LAN-only.
- Sender must be online during transfer.
- No cloud relay.
- No WebRTC or TURN fallback.
- UDP discovery is simple broadcast-based LAN discovery.
- Durable peer identity and persistent Bridge continuity are not complete.