Floe Agent, Floe Bridge, and the terminal, file and MCP capabilities work together on this Mac.
What your tasks can use.
You approve access on both the Mac and in Floe. Capabilities open with the connection and end when it closes.
Terminal
Start terminal jobs on the Mac, read output, send input and end processes.
Files
List, read and write files inside a workspace, with paths constrained by local policy.
MCP
Bring configured MCP services into the same task alongside terminal and files.
This connection does not need a Linux image. Once disconnected, these Mac capabilities are no longer available to the task.
Install, connect, then get to work.
Go from download to first connection in order; permissions are requested only when needed.
Install
Check the system, chip and Floe version requirements for that release.
Download the installation file from its release page and follow that version’s instructions.
Launch Floe Bridge; once its menu bar icon appears, start the connection from Floe.
Use it on the same Mac as Floe; check the corresponding release for version requirements.
First connection
Choose this Mac from Floe to start a connection.
The Mac and Floe each show a native confirmation; compare the matching code.
The connection opens only after both sides allow it. A refusal on either side leaves it closed.
The connection is established only on this Mac.
Permissions
Terminal, files and MCP are the connection capabilities. Screen Recording and Accessibility are requested only when you choose a feature that needs them; their state appears in Connections and Storage….
When a terminal task touches a protected folder, macOS may ask for that folder; allow only what the task needs.
Declining one permission does not block the others, and you can revoke it later in macOS System Settings.
Disconnect and clean up
Floe Bridge menu → Connections and Storage… → Disconnect. This revokes the pairing and cancels its terminal jobs.
Choose Quit Floe Bridge from the menu to stop the local listener and end any remaining terminal jobs.
In Storage, move Caches and Logs to the Trash; use Manage Unused Items… for unused tasks and skill versions.
To remove everything: quit, move the app to the Trash, then delete ~/Library/Application Support/Floe Bridge, ~/Library/Caches/Floe Bridge and ~/Library/Logs/Floe Bridge.
Moving only the app to the Trash leaves workspace data in place; deleting ~/Library/Application Support/Floe Bridge removes the tasks, workspaces and skill copies managed by Floe Bridge. Confirm you no longer need them, and do not delete files you saved elsewhere.
When something does not work.
Check the version, connection and system permissions first; reinstall only if those do not explain it.
The Floe Bridge icon is missing from the menu bar.
Launch Floe Bridge from Applications. If macOS blocks the first launch, follow the system prompt in System Settings → Privacy & Security; do not bypass a security warning.
The two confirmation codes differ.
Cancel the connection on both Floe and the Mac, confirm Floe is 1.7.62 or later, then start again from the same Mac.
A terminal task cannot reach a folder.
macOS may ask for that folder separately. Allow only the folder the task needs; if you declined, adjust it in System Settings → Privacy & Security → Files and Folders, then run the task again.
How is this different from a remote iPad-to-Mac bridge?
Floe Bridge runs on the same Mac as Floe; it is not a remote bridge from iPad to Mac. The connection is established only inside this Mac, exposes no LAN address and uses no remote relay. After disconnecting, terminal, file and MCP capabilities are no longer available to the task.