Explicit folder grants
Choose the folders that belong in the workflow. The tool does not begin by sharing an entire disk.
Workspace file sharingPrivate pilot
Easy Bridge
Share the folders you choose.
Browse, find and transfer approved workspace files through an owner-controlled file hub.
Ask about Easy BridgeWhat it is for
Easy Bridge is a focused answer to a common engineering problem: useful work is spread across different machines. It gives an owner a way to approve particular folders, browse their contents, search filenames and transfer selected files or folders.
The project also includes encrypted vault capsules and read-only MCP access for approved workflows. Sharing starts with explicit grants and a private connection. You decide what is included and which participating machines may connect.
Read the product detail before committing. Requirements and boundaries are part of the product, not small print.
Designed around the work
Browse, find and preview
Find files by name and use inert previews before deciding what to transfer.
Move selected work
Transfer approved files and folders between configured participants using the documented private connection.
Read-only agent access
An MCP interface gives approved agents a bounded way to inspect shared material without granting general computer control.
What you need
- Node.js 22.17 or later on each participating machine.
- Owner approval for each shared folder and each connection.
- A private, authorised network arrangement.
- A review of files inside each approved folder before sharing.
A good fit for
- Developers moving project assets between their own machines.
- Small teams piloting deliberate folder sharing.
- Agent-assisted work that needs a restricted read-only file interface.
Typical workflow
- Install and start the local service.
- Grant only the folders needed for the project.
- Authorise a private peer and inspect its connection.
- Preview and transfer a small sample before moving more work.
Boundaries to know
- The Windows prototype has been verified locally. Linux/macOS launchers are included; execution on those systems needs separate validation.
- A real connection to another developer machine must be configured and tested during a pilot.
- Protected credential paths are excluded conservatively; ordinary private documents still need owner review.
Talk it through