Good questions.
Clear answers.

Masbot is a personal AI workspace for people who want their own bots for research, writing, planning and everyday work. Choose a model, give each bot a role and manage its memory. Creators can also launch bot tokens on Solana and publish bots in Marketplace.

Yes. Create bots for writing, learning, planning, project research and other tasks. Solana token launches and Marketplace publishing are additional choices, not the purpose of every bot.

Sign-in guides you through the wallet and any token-holding requirements that apply to your account. Connecting a wallet does not enable bot spending or launch a token. See the setup guide for the steps.

The local Masbot app is free. Optional specialist subscriptions, your AI provider’s plan or usage, and Solana transactions may have separate costs. Review the terms before subscribing or approving a transaction. See how costs differ.

The local Masbot app is free. Optional specialist bots and AI provider plans or usage may have separate costs. See the setup guide for sign-in and wallet requirements.

Masbot runs on Windows x64. macOS, Android and iOS are planned. Subscribe to the newsletter for release news.

Install Masbot for Windows x64, complete sign-in and the wallet/access checks shown for your account, then set up device unlocking. Connect an AI provider or local runtime, create a bot and start with a small task. The setup guide walks through the steps.

No. Your sign-in wallet establishes the access required for your account. Bot payment permissions are a separate choice, and payments start off. Connecting a wallet does not launch a token or authorize a bot to spend.

Masbot combines a local Windows workspace, compatible AI provider choice and personal bots with editable memory. Meta describes Muse as a personal agent running on Muse Secure VM, with background work and app connections. Choose Masbot when choosing your model and keeping a local bot workspace matter most. Compare Masbot and Muse and read Meta’s Muse introduction.

Grok is an assistant for chat, voice, media and connected tools. Grok Bot adds persistent cloud computers, named bots and routines. Masbot focuses on personal bots in a local workspace, with compatible provider or local-model choice and optional specialist subscriptions. Compare Masbot and Grok; see the official Grok and Grok Bot guides.

ChatGPT Dots are ongoing agents with their own cloud computers, ChatGPT context and permitted app connections; they can also use a connected local computer. Masbot gives you a local Windows workspace for personal bots and a choice of compatible AI providers or local runtimes. Masbot’s hosted computers are planned. Compare Masbot and ChatGPT Dots and read OpenAI’s Dots guide.

The useful comparison is the work you need to do. Masbot brings model choice, saved bot context, local workspace storage and optional specialist workflows together. Results depend on the selected model, tools, permissions and task. We do not claim a universal intelligence, speed or accuracy advantage. See which approach fits your work.

Your bot’s saved conversations, memory and files stay in your Masbot workspace when you change its model. Models have different capabilities and context limits, so responses and the context available for a request can differ. An online provider receives the information needed for requests you send to it.

Open Settings → AI Providers. Connect Codex with your ChatGPT account, connect your Cursor or Claude account, or choose a local model. Provider plans and usage limits apply.

Yes. Masbot supports local model runtimes such as Ollama and LM Studio. Bring a downloaded model that fits your device and connect the runtime in Settings. Licenses, hardware needs and capabilities vary. See provider options.

Local model inference can run on your device. Sign-in and access checks, public-web research, hosted model requests and connected services may still need internet. A local model does not make every Masbot feature available offline.

Yes. Choose the model suited to each bot’s role from the providers available to your account. Switching the selected bot’s model keeps its saved conversations, memory and files in your workspace. Provider availability and usage limits still apply.

Use the model picker in the chat or task header. Browse the providers and models available to your account; supported models expose effort choices. Connecting a provider is a separate action in Settings, and active work can restrict changes.

Yes. Review and edit useful saved memory in your workspace. Each bot has its own role and context. Changing a model does not erase that saved work, though models can differ in how much context they can use.

Yes. You can create and use personal bots without launching a token for them. A token launch and public Marketplace listing are separate choices you review and approve.

Yes. Give each personal bot its own role, instructions and personality. You can create bots for research, writing, planning and other tasks, then choose the model and permissions suited to each job.

Bring your own bots into a group and use @mentions to address a bot directly. Choose which conversation history to share when adding a bot. A group is a place to compare perspectives and work together.

No. You choose the conversation history to share with a group. Group discussion does not automatically expose every private bot conversation or grant additional action permissions.

Bot names use 1–40 English letters, numbers, underscores or hyphens and start with a letter. Spaces and other whitespace are not supported. Registration checks whether the name is available.

No. Subscription renewals are manual. Review and approve another access period when you want to continue.

No. Bot spending permission and Marketplace subscription renewal are separate. You still choose whether to renew subscription access.

No. Your model provider’s plans and usage charges are separate from a specialist bot subscription.

Paid access ends at the end of its period. The bot cannot continue paid work until you renew; saved conversations and files stay in your workspace.

Explore ResearchBot for token investigations, LaunchBot for launch planning, TraderBot for manual trading work, SniperBot for market-watch conditions and RadarBot for public wallet intelligence. Each full profile includes capabilities, workflows, example requests and controls. Review current availability, prices and access periods in the app before installing. An installed bot has its own conversations in your workspace. Explore Marketplace.

Some specialist bots charge for subscription access. Review the price, access period and separate network fee in the app before approving payment. Renewals are manual: you choose whether to pay for another period. Read about bot subscriptions.

A token and a paid bot subscription are separate. Check the bot’s listing for its access terms. Bot payments, model-provider charges and network fees are separate too. Understand the different costs.

The local app is free. Marketplace offers optional specialist bots that may have their own fees. Listings show the applicable terms before you subscribe.

Yes. Add it to a group in your workspace and choose the history you share. A paid bot needs current subscription access to take part.

Publish a bot you created. A Marketplace install is a private copy for your use and cannot be republished as your own.

Open Marketplace inside the Masbot app. This website explains the experience; purchases and installation happen in the app.

Yes. The public Marketplace page introduces the specialist bots and lets you browse their roles. Current subscription terms, access checks and installation are handled in the Masbot app.

No. Bot payment permissions control money a bot may spend on your behalf. The local app is free; optional specialist subscriptions and model-provider charges are separate.

Yes. Payments start off and can remain off. Connecting a model, creating a bot or approving an ordinary task does not enable bot spending.

No. Autopay follows the payment budgets and fee caps you save. Larger USDC payment requests ask for confirmation. Token launches and Marketplace subscription renewals have their own review and approval.

Local bot payments need Masbot running and the workspace unlocked. Hosted computers for bots are planned.

Yes, if you choose Autopay within limits for that bot. Payments start off. Back up its wallet and save your USDC spending limits and SOL network-fee caps before enabling Autopay. You can also choose Ask for confirmation. This controls your bot’s spending, separately from Marketplace subscription fees. Learn about bot payments.

The bot wallet needs a recovery plan before you enable spending. Follow the Backup step for the selected bot in Settings → Wallet, then review payment permission and budgets. Keep recovery material private and separate from public reports.

The payment setup includes a daily USDC budget and SOL network-fee caps. Payments off, Ask for confirmation and Autopay within saved limits are separate choices. Review the selected bot and the policy before saving. Read about payment controls.

Yes. Launch a token for your personal bot on Pump.fun through Masbot. Prepare the token details and image, review the costs, and approve the launch in your wallet. See the bot-token launch flow.

Yes. Publish a personal bot you created, connect its token identity to a Marketplace listing, and choose the subscription terms and which knowledge or skills to share. Private conversations and wallet keys stay out of the public copy. Read about publishing a bot.

Yes. Open Launchpad in Masbot, choose a personal bot, prepare its token details and image, review the costs, and approve the launch in your wallet.

The guided flow requires you to review the details and approve the launch transaction in your wallet. A chat request does not itself authorize a token launch.

Yes. Choose the bot’s plan and price, then review and approve its public Marketplace listing. Bot subscription access is separate from trading or holding its token.

Publish a personal bot you created. Installed Marketplace bots cannot be republished as your own.

Review the public bot copy, its description and subscription terms before publishing. Private conversations and wallet keys are not included in that public copy. Read the publishing journey.

The planned split of platform profit is 50% for $MAS buybacks, 30% for staking and 20% retained as protocol revenue for infrastructure and operations. This applies to profit from Masbot-owned bot subscriptions and platform fees. Independent creators keep their own earnings. Explore the Masbot economy.

$MAS is Masbot’s own token. A bot token is a separate Solana token launched for a personal bot. Holding a bot token does not by itself give you a paid subscription to that bot. Read about bot tokens.

The planned allocation of platform profit is 50% for $MAS buybacks, 30% for staking and 20% retained as protocol revenue to maintain infrastructure and operations. These percentages describe the use of profit, not token supply distribution.

The split applies to Masbot’s platform profit from its own bot subscriptions and platform fees, after costs are accounted for. Independent creators keep their own earnings under their listed terms. Customer wallet funds are separate.

The platform uses its 50% buyback allocation to purchase $MAS from the market. A purchase is distinct from a burn: burning permanently removes tokens from supply. A burn policy has not been announced.

30% of platform profit is reserved for the planned staking program. Eligibility, reward calculation, lock periods, claiming rules and the launch date will be announced before participation opens. No fixed yield or live staking rewards are announced.

The 20% protocol revenue share supports infrastructure and ongoing operations, including hosting, maintenance and the services that keep Masbot running.

App access and paid bot subscriptions follow their own terms. Holding $MAS or an individual bot token does not by itself activate a paid subscription to that bot.

This page explains the planned model. Buyback timing, public transaction records and staking allocation reporting will be added when available. The example above is illustrative, not a record of completed activity.

The public directory is planned after launch. It will bring together tokens launched through LaunchBot and published bots, with links to each bot and its associated token.

Token supply, distribution, vesting, launch and liquidity details remain to be announced. The 50 / 30 / 20 allocation on this page concerns platform profit.

Your conversations and settings are stored on your computer. When you use an online model or connected service, it receives the information needed to complete your request.

No. The website does not read your desktop conversations, files, memory or preferences. Website usage measurement is separate from access to your local Masbot workspace. Read the privacy information.

When you choose an online model or connected service, it receives the information needed for the request you send. Your workspace remains stored on your computer, while the selected service’s own terms and data handling apply to that request.

Yes. An optional backup can send the backup you choose off your device. Review the app’s backup and recovery options and keep the recovery material needed to restore your work. Publishing a bot is a separate choice from backing up private work.

No. Only the report you review and choose to send is included. Conversations, logs, keys and attachments are not automatically attached. Keep passphrases, private keys and recovery phrases out of reports and public posts.

The website may use Google Analytics and Microsoft Clarity for website usage and performance. Those services can process usage and device information and use cookies. This does not give them access to your desktop workspace. See website privacy information.

A transaction on Solana is recorded on a public blockchain. Review the details before approving it in your wallet. Local conversations and private wallet recovery material are separate from the public transaction record.

For local tasks, your computer needs to stay on and your workspace unlocked. Hosted computers for bots are planned.

Hosted computers for bots are planned. Subscribe to the newsletter for updates as they take shape.

Close Masbot and try reopening it. If it reports a local file verification or startup failure, use the official Masbot installer to reinstall the application. If the problem continues, note the exact message and app version for support.

Check the connection in Settings → AI Providers and the models currently available to your account. Provider sign-in, plans, model support and usage limits can affect availability. Choosing a different provider in the picker does not connect that provider automatically.

Open Settings → Help & support → Feedback and bug reports. Choose Feedback or Bug report, describe what you expected and what happened, review the message and slide to send. Use Check submitted reports to confirm receipt. See the support steps.

No. A receipt confirms that your report was received. It does not mean the issue has been resolved. Include useful reproduction steps and your app version so the report is easier to investigate.

Follow what’s next, subscribe to the newsletter or visit the official @Masbot_si account on X. Hosted computers, macOS and mobile support remain planned.