Into a terminal
Upload a file to the workstation and insert its remote path in your current prompt.
Built for remote AI development
Change screens.
Keep your flow.
One terminal session. Several workstations.
Pick up where you left off on another screen.
Go somewhere else.
Keep the same session.
Your phone, computer and browser can join the same hosted terminal. Its process, directory and output stay on the workstation.
One remote instance, multiple connected devices
Unfold and get to work.
A larger terminal, desktop-style keys and session tabs make a foldable a practical coding workspace.
One workspace for your computers.
Develop on one machine, build on another. Find each machine’s terminal, desktop, files and web preview in one place.
Drag and drop.
Keep files with your work.
Move files between your authorized devices without first uploading them to a third-party cloud drive.
Into a desktop
Send a local file to the workstation you are controlling, ready to open in a remote app.
Into Transfer Hub
Leave it on one device and pick it up on another. Share files, text and links.
Open a browser.
Resume your session.
A compatible browser can join your shared terminal. Your CLI keeps running on the workstation.
Open web terminal ↗Workstation · localhost:3000
Hello, next idea.Remote web preview · Illustration
Your phone or another computerCheck the result as you go.
Use the native client to preview a web service running on your workstation. Edit in the terminal and see the result without deploying it to the public web.
Scan to sign in.
Confirm the sign-in from an already signed-in phone instead of retyping your credentials.
A little personality.
CPU load companions, a curtain for your workspace and terminal themes make it feel like yours.
Animation credits: RunCatGood to know
Shared terminals and running sessions
Devices share terminal instances created and hosted by Bitseed. Existing system terminals aren’t automatically taken over. The workstation must stay online; restarting, stopping the service or ending a session can interrupt tasks. Sharing a session does not replace execution confirmations in third-party tools.
File drops and transfers
Remote terminals accept files, not folders. Uploading inserts the path without running a command. Desktop drops require the desktop client and transfer permission on the destination. Transfer Hub needs the original file and source workstation to remain available. Connections may use the public internet or a relay.
Native clients and the browser
The web client focuses on shared terminal sessions, related messages and files. Remote desktop and web previews require a supported native client. Remote web preview also requires a running service on an online, authorized workstation.
Sign-in and workspace extras
QR sign-in requires confirmation and does not bypass workstation or system permissions. The companion reflects CPU load, not AI progress. The curtain covers the workspace without locking the system.
Remote AI development
starts here.
Pick up your AI coding session and move files between your own devices with a drag and drop.