Choose your models, give each bot a role, and pick up
the conversation from your phone.
Desktop + Android companion · Public releases in preparation
Features
Models, tools, computers, and conversations. Connected in one workspace.
Keep your preferred model for each bot, or change it for a single thread. Model and reasoning options follow the engine you connect.
Available models depend on your provider account and installed engine.
Move beyond a text reply with supported browser, local VM, or cloud computer environments. Choose the environment in the bot’s computer panel.
Requires setup and a compatible engine. Local desktop control varies by platform; Linux Wayland is not supported.
Configure connected apps or add trusted MCP servers to give compatible bots access to tools. Review each connection and its permissions before enabling it.
App connections need a configured connection service. MCP servers may run local commands or contact external services.
Create threads and folders, pin important work, mark conversations unread, and archive what is finished. Give different projects their own space.
The screenshot shows actual bot and conversation controls in a sample workspace.
Manage engine sign-ins, optional API keys, and OpenAI-compatible endpoints from your workspace settings. Choose the authentication method your engine supports.
Provider subscriptions, API charges, and usage limits are separate from GlinkBot.
Choose a voice engine, configure spoken replies, and decide when your bot should notify you. Keep voice and alert preferences together in its profile.
Voice calls currently require the macOS desktop app. Voice engines may need a separate account or local setup.
Real app screens from a demonstration workspace. Feature availability depends on platform, engine, and configuration.
Use cases
Start with a clear task. Add a schedule when it becomes a routine.
Example workflow
Summarize what needs my attention today. Draft replies, but wait for my approval before sending.
Example workflow
Review this invoice list. Flag overdue items and draft a polite reminder for each. Do not send anything.
Example workflow
Compare this release with the acceptance checklist. Show what passed, what failed, and what you could not verify.
Example workflow
Review this change for correctness and regressions. Give me concrete findings with file references. Do not edit the code.
Example workflow
Compare these products using their current official information. Link every source and separate facts from your interpretation.
Example workflow
Turn this week’s project updates into a short report. Highlight completed work, blockers, and decisions needed. Do not invent missing numbers.
Example workflow
Group these support messages by topic and urgency. Suggest replies and flag anything that needs a person. Leave all replies as drafts.
Example workflow
Help me plan a realistic week from these commitments. Protect focused work and leave some breathing room. Keep my calendar unchanged.
Examples depend on connected tools, permissions, and a running host. Always review important results.
How it works
A desktop workspace. An Android companion. The AI provider you choose.
Access your paired agents
and conversations.
Keep the host running and reachable.
Your account, model,
and usage limits.
Configure a supported engine using its sign-in or API credentials. Start with the provider you already use.
Set its instructions, add useful context, and separate ongoing work into focused threads.
Choose the tools and environment it needs. Review permissions, approvals, and the work it produces.
Workspace data uses ~/.glinkbot by default. Requests to cloud providers still leave your device.
Integrations
Configure supported integrations in your workspace. Accounts and usage charges are separate.
Claude Code engine
OpenAI’s Codex agent engine
Cursor agent engine
xAI provider integration
OpenCode agent engine
Kimi agent engine
Qwen agent engine
Factory’s coding agent
Hermes agent engine
Pi agent engine
Antigravity agent engine
Your compatible API endpoint
Connect an installed engine or configure its supported provider access. Availability and model choices depend on your account and build.
An isolated desktop on your machine
Local control on supported desktop sessions
A separately configured browser environment
A configured remote computer environment
Run the workspace on a host you manage
Keep computer access disabled
Not every engine supports every environment. Installation, credentials, platform support, and separate service charges may apply.
Email context and actions
Calendar context and events
Files and documents
Structured spreadsheet data
Team conversations
Repository and issue workflows
Pages and workspace knowledge
Issues and project work
Trusted local commands or server URLs
Examples from the connection catalog, not preconnected services or partnerships. Each needs authorization and a configured connection service; tool availability varies.
Compatibility does not imply partnership. Availability varies by platform and configuration.
Team playbooks
Turn a repeatable process into focused agents, shared instructions, and reviewable routines.
Go from a scoped idea to a reviewed change, with a clear handoff at each step.
Turn the goal into steps and acceptance checks.
Work on one approved change at a time.
Check behavior, evidence, and remaining risks.
Start with a well-framed question. Finish with a draft you can trace back to its sources.
Find useful evidence and keep source links.
Shape a clear draft without losing the caveats.
Review instructions, connections, and schedules before enabling a playbook or importing a team.
GlinkBot for your devices
One workspace to return to. Another screen to reach it from.
macOS · In preparation
Bring your agent conversations, computer tools, and voice settings together on your Mac.
Official GlinkBot release links will appear here when ready.
The macOS desktop app is required for voice calls. Final supported OS versions and signing details will accompany the release.
GlinkBot pricing has not been announced.
AI provider subscriptions and usage charges are separate.
Windows · In preparation
Keep focused agents, project threads, and provider settings together on your PC.
Official GlinkBot release links will appear here when ready.
Final architecture support, system requirements, and installer verification details will be published with the Windows release.
GlinkBot pricing has not been announced.
AI provider subscriptions and usage charges are separate.
Linux · In preparation
Run your agent workspace on your Linux desktop. Keep your conversations, projects, and tools in one place.
Official GlinkBot release links will appear here when ready.
Planned Linux package formats. Local desktop control needs a supported Xorg session; chat and other configured tools do not require it.
GlinkBot pricing has not been announced.
AI provider subscriptions and usage charges are separate.
Android · In preparation
Pair the Android companion with your GlinkBot desktop or server to access your agents and threads from another screen.
Official GlinkBot release links will appear here when ready.
Keep your paired host and phone companion service running and reachable. Google Play availability has not been announced.
Android companionPair with your running hostConnection illustration, not an Android screenshot.
GlinkBot pricing has not been announced.
AI provider subscriptions and usage charges are separate.
FAQ
Straight answers before you get started.
No. It is a workspace for the agent engines and providers you choose. You configure the accounts, models, and tools that power your bots.
The Android app is a companion. It needs a paired, reachable desktop or server with the companion service running. It is not a replacement for that host.
No. Workspace data is stored locally by default, but cloud AI providers and connected tools receive the requests and context needed for the task. Their own terms and privacy practices apply.
Where the installed engine supports it, you can use its existing sign-in. Other engines use API credentials. Account eligibility, subscriptions, and usage limits remain with the provider.
Only with a configured, supported environment and appropriate access. Browser, cloud, VM, and local desktop capabilities differ. Review permissions and approval settings before enabling tools.
Public GlinkBot installers and the Google Play listing are being prepared. The download page will carry official release links when they are available. Pricing has not been announced.
GlinkBot
Examples depend on connected tools, permissions, and a running host. Always review important results.
Review instructions, connections, and schedules before enabling a playbook or importing a team.
Apple Silicon