-
Notifications
You must be signed in to change notification settings - Fork 159
Remote and Multi device
Your work should not disappear when you leave one screen. BitFun can connect a desktop workspace to a phone, another signed-in device, a remote development environment, or selected messaging services while keeping the desktop experience at the center.
Open Remote Connect on the desktop and pair a mobile browser by QR code. The mobile experience supports:
- viewing, searching, renaming, and resuming sessions;
- starting a Code, Cowork, or Assistant session;
- switching workspaces, including supported remote workspaces;
- choosing automatic, primary, or fast model routing;
- sending queued messages and image attachments;
- following responses, tool activity, and generated files;
- copying or removing messages;
- checking connection health and changing language or theme.
Mobile web is designed for continuity and control, not to shrink every desktop panel onto a small screen.
Connect directly on the same network. This is a natural choice at home, in a studio, or inside a trusted office network.
Use an ngrok-based connection when direct LAN access is not practical and you already work with that service.
Use BitFun’s relay for convenient pairing across networks. The public relay is intended for trial and everyday evaluation; users with stronger operational or governance requirements should consider a self-hosted option.
Point BitFun at a relay you operate or trust. This provides more control over availability, policy, and deployment.
Paired remote payloads are end-to-end encrypted using ephemeral session keys. Relay infrastructure forwards encrypted traffic rather than receiving plaintext work content.
Some connection metadata—such as routing, timing, device presence, and service-level diagnostics—is not the same as encrypted payload content and may still be visible to the infrastructure involved. Security also depends on the devices, accounts, networks, and providers you choose.
Read the full security overview →
BitFun can open projects where they actually live:
- SSH hosts;
- SSH jump-host chains;
- containers reached over SSH;
- local containers;
- environments that expose SSH from inside a container.
The selected remote target is shared across the explorer, terminal, agent, search, Git, upload, and download experiences. This helps a remote project feel like one coherent workspace rather than a collection of disconnected tools.
With a BitFun account, supported clients can see device presence and start or continue sessions on another signed-in device. Account features can also synchronize selected settings and support session handoff.
Account services are optional for core local desktop use, but required for account-based device control and Pages.
BitFun can connect selected assistant and workspace flows to:
- Telegram
- Feishu
- WeChat through iLink
These connectors are useful for quick questions, session updates, and continuing selected work from a familiar chat surface. Their exact capabilities depend on the platform, bot configuration, current workspace, and permissions.
Remote access is an extension of the BitFun workspace, not a claim that every device has identical capability. The desktop currently provides the richest experience; mobile web, messaging, CLI, and remote control are optimized for the parts of the workflow that make sense on each surface.
BitFun’s longer-term vision is to let work remain continuous across desktop, browser, phones, wearables, and more ambient devices. Mobile web and remote control are useful today; broader native-device coverage is still evolving and should be understood as a direction, not a promise that every client is already complete.
Next: get started, review security, or explore the product overview.
BitFun · Website · Releases · Issues · MIT License
Built in the open. Made for work that deserves more than a chat box. / 开放共建，为那些不该止步于聊天框的工作而生。