GlinkBot
Two devices, one running workspace
The GlinkBot Android app is a companion to your desktop or server. It is not a second computer running your agents and is not a standalone replacement for the host. That distinction explains both how to start and what to check if a conversation cannot connect.
You need a supported desktop build, a configured AI engine, and a connection your phone can reach. Have access to both devices for the initial pairing. Use a non-sensitive test conversation first.
1. Install the desktop app first
Open glinkbot.com/download on your computer. Select the package for your operating system and processor, not just the first download button. The page lists Linux x64, macOS Intel and Apple Silicon, and Windows x64 and ARM64 packages, with manifests for checksum verification.
The current desktop packages are previews. Read the platform’s signing and installation notes before installing. Do not turn off system security globally to get past an installer warning. Download only from the official links and verify what you are opening.
2. Connect an engine and make a small test
Open GlinkBot settings and configure a supported engine using its supported sign-in or credentials. A download does not include third-party AI credits. Existing accounts work only where the engine and provider support that authentication method.
Create a bot, give it a short role description, and send a harmless prompt from the desktop. Confirm you can receive a response before debugging the phone connection. This separates a provider setup problem from a pairing or network problem.
3. Pair your Android phone
Get the Android companion from the Google Play link on our download page. On your computer, open Settings → Remote access → Pair a device. Follow the connection and QR instructions in the Android app, and complete any confirmation shown on the host.
Keep pairing codes and QR images private. They are for authorizing a device, not for posting in a support ticket. Start on the same trusted network where appropriate; remote connections require a deliberately configured reachable address. Do not expose an unauthenticated app port to the public internet.
4. Continue the conversation, then check the host
Open your bot’s thread on Android and send a follow-up to the desktop test. You should be working with the paired workspace, not creating an unrelated cloud conversation. Keep your phone’s connection and the host’s power state in mind as you move between networks.
Closing the phone app is different from shutting down the computer running GlinkBot. The host must remain running and reachable for this companion workflow. Laptop sleep, a stopped desktop application, or an unreachable network can interrupt access. Android does not remove those requirements.
If it does not connect
- No desktop response: check the engine’s sign-in, model availability, and provider allowance on the computer.
- Desktop works, phone does not: check the selected host, companion service, pairing state, and reachable address.
- It stops when you leave home: check your intended remote networking setup instead of repeatedly reinstalling the app.
- A task needs approval: inspect the requested action and your configured access policy. Do not enable broader access just to silence a prompt.
Use the Help Center for setup guidance or contact support with your platform and a redacted error message. Never send provider keys or pairing tokens.
Is this the right kind of agent app for you?
A phone companion is useful when you already want to run a desktop workspace. A managed cloud agent may fit better if you do not want responsibility for keeping a host available. For those trade-offs, read our Grokbot alternative and Muse AI alternative guides. Neither comparison promises that different products have identical features.
