mintbot local¶
Your agent on your own computer. The panel, Telegram and mintbot credit work exactly as they do for an agent on a private server, but the agent lives on your hardware and the data stays on your disk.
How it works¶
-
Its own address
The agent gets an ordinary
agentN.mintbot.aiaddress, so you open the panel from any device, away from home too. No router ports to open and no static IP needed: the computer itself opens an encrypted tunnel to the mintbot relay server. -
Panel and Telegram
The same panel, the same Telegram bot, the same skills, background jobs and projects. Your computer runs the same agent software as a private server.
-
Services on the internet
Whatever the agent builds on your computer, a web page or a small app, it can publish under its own
agentN.mintbot.aiaddress, just as on a private server. -
Models as usual
mintbot credit, your ChatGPT/Claude subscription or your own API key, exactly as for any other agent.
-
Updates itself
Every night around 4 am (your computer's time) the agent installs a signed update. If it is busy, the update waits for the next night. If the computer was off all night, the update runs once it is back.
-
In its own corner
The agent runs under a separate, restricted user account. It does not see your personal folders and does not change your system. Setup also closes the agent's port in the firewall.
1 Order¶
Pick the mintbot local package on the mintbot.ai order page. The service fee is €3 a month, with no server to pay for. Model usage is separate: from mintbot credit or your own subscription.
2 Install¶
After payment the delivery page and the e-mail give you a personal
installer (.deb). Double-click it to install like any other program.
3 Connect¶
Open mintbot local from the applications menu and press Install and connect. The computer asks for your password once, downloads the agent, links it to your order and starts it. Nothing to confirm in the browser: the connection key is inside your personal installer.
You get a panel sign-in link as usual: in Telegram, @mintbot_ai_bot → /panel.
On a computer without a screen
On a server or over SSH the same works in the terminal:
sudo apt install ./mintbot-local_<version>_amd64.deb
sudo mintbot-local install
mintbot-local status shows the state, sudo mintbot-local start|stop
starts or stops the agent.
Payment, pauses and recovery¶
Without healthy automatic renewal, mintbot sends email, Telegram and panel warnings 7 days, 3 days and 24 hours before expiry. A healthy PayPal or Stripe subscription does not get these ordinary warnings. A failed automatic charge gets an immediate notice and, if still unpaid, the 24-hour follow-up.
At the paid-through deadline mintbot-managed access, relay, updates and proxy service pause. There is no additional public-link grace period. Nonpayment never deletes your computer, files or agent, and never stops an independent Hermes runtime. There is no deletion countdown or final goodbye.
While paused, you receive an email once a week, indefinitely. Pay using its central recovery link and the same agent can return even months later. The new paid period starts with payment; paused months are not billed. Before another payment is accepted, mintbot reconciles any payment already in flight and ends the old unpaid subscription. A successful payment whose webhook was delayed keeps its actual paid-through date and healthy automatic renewal; it is not charged again. If the provider cannot be reached, cleanup stays pending and recovery waits rather than claiming cancellation succeeded.
For Stripe, the old unpaid subscription is canceled immediately without a final invoice or proration. Its draft invoices are deleted and its open unpaid invoices are voided, including payable invoice links; unrelated customer invoices are not touched. PayPal subscriptions are canceled, never resumed or used to capture an outstanding balance. Recovery uses a new subscription and its new paid billing period, not the old subscription's monthly anchor. If payment settles while cancellation is underway, its verified paid period is reconciled first; a late webhook cannot restore a permanently disconnected identity.
Recovery works while the computer is offline; it can reconnect when switched on. Each weekly email contains fresh, narrowly scoped links valid for two weeks, not a permanent account credential.
Each reminder also offers permanent disconnection. Opening that link only shows a confirmation page; you must explicitly confirm to revoke the computer's binding and stop reminders. Subscription cancellation is durably retried until the payment provider confirms it. A pending cancellation is shown honestly; check or cancel it with your payment provider until confirmed to avoid further charges. This disconnects mintbot only: it does not delete local files, power off the computer, or stop independent software. An old link cannot disconnect a renewed or newly bound device, and a pending paid renewal prevents disconnection.
Pros and cons¶
Pros
- Your own hardware. Use the computer you already have, with all of its memory and disk space.
- Graphics card. If a local service runs on the computer's GPU, such as Ollama with local models or an image generator, the agent can use it directly, with nothing going to the cloud.
- Local integrations. The agent is on your home network: Home Assistant, a NAS, a printer or office systems that are not on the internet.
- Cheaper. €3 a month, no server to pay for.
- Your data stays, whatever happens. Everything is on your disk. Neither removing the agent nor ending the subscription deletes it.
Cons
- Power cuts. Computer off, agent off. Its address then shows a "computer is offline" page and Telegram gets no reply. When the power returns, the agent starts by itself. A UPS helps against outages.
- Slow internet. The panel, files and public services all travel through your home connection. A slow upload speed shows at once.
- A computer always running at home. It has to stay on around the clock with sleep turned off. That means power use and sometimes noise.
mintbot local or a private server?¶
| 💻 mintbot local | 🏢 Private server | |
|---|---|---|
| Where the agent runs | on your computer | on a mintbot server in a data centre |
| When it is reachable | while the computer is on and online | around the clock |
| Hardware | yours, including the graphics card and home network | the server's |
| Agent's rights | a separate, restricted account | full root |
| Data | on your disk | on your server in the data centre |
| Monthly fee | €3, models separate | the server package |
What you need¶
- A Linux computer. Debian 12 or 13, or Ubuntu 24.04 or 26.04 (64-bit, amd64).
- A steady internet connection. The faster the upload, the smoother the panel.
- A computer that stays on. Turn sleep off, or tell the computer not to sleep while plugged in.
Good to know¶
- One agent per computer. For now one computer takes one mintbot local installation.
- Removing deletes nothing.
sudo mintbot-local removestops the agent, removes its services and tells mintbot. All data stays on the disk. - Backups are yours to make. The data lives on your computer, so backing it up and hardware failures are yours to handle too.