GlinkBot
Product tour
See how the pieces
fit together.
Explore six real screens from a GlinkBot sample workspace.
This is a screenshot tour, not a live agent. It does not send prompts, connect accounts, or access your computer.
Choose a model per bot
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.
A computer when work needs it
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.
Connect the tools you use
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.
Keep conversations organized
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.
Configure your providers
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.
Talk, don’t just type
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.
