Everything that is not the chat itself: Bots, people, credentials and the phone.
Your team of always-on Bots that you can give real work to
By using mogbot, you additionally agree to these Terms.
Copy a Bot summary into a channel. The link starts connected.
Start a Bot from a template. Its name, emoji and instructions are copied.
Machine identities a team can use. Disable one to stop it working.
Credentials the Bots may use. Entries stay locked until you unlock them.
Three steps: connect the phone, give the Bot something to do, then finish.
The key is stored locally in the mogbot database. It never leaves the machine except in model requests.
Rules match the tool call text. Max 20 rules per list, 1,000 chars each. “Always allow” appends a rule here; delete it to ask again.
Record what you do on the phone, then stop. Every action is counted as a step.
The agent works on the phone. Refresh to take a new frame.
Model Context Protocol servers the Bots can call, configured once for this account.
Publish a Bot as a link. Link shares are readable by anyone with the token.
Notes and files a Bot can read while it works.
An MCP server the Bots can call. A connector needs auth before it can run tools.
A team groups Bots and members. Private teams keep their Bots out of shared listings.
A routine runs a prompt on a schedule. Runs create their own chat.
Reusable instructions for this Bot, injected into its prompt. Editing keeps the previous version so you can restore it.
One active device. The mock always works; a real phone needs adb.