OpenMausBot 0.1.144

What's new in 0.1.144

This Mac, right on the rail

• If your bots live on My Cloud, your computer now sits on the left rail beside it. One click opens a fresh place on this computer; one click takes you back to My Cloud.
• Your Cloud's bots stay on My Cloud, and your computer keeps working for them while you're in This Mac.
• The app still opens My Cloud first.

Bots send without a daily limit

• At Full access, bots send emails and messages through your connected apps as often as the work needs. There's no daily cap any more.
• A bot's Permissions has two plain choices: Ask every time, or Send without asking.

Cloud computers do more

• Bots copy files between their cloud computer and their own folder, in both directions, up to 2 GB a file.
• A long command can run in the background on the cloud computer while the bot checks on it, so big downloads and data jobs no longer time out and run twice.

Team Clouds sleep when idle

• Team Clouds can now sleep when nobody is using them, like the other plans, and wake in a few seconds when someone opens one or a routine is due. Work one bot handed another keeps a Cloud awake until it's done. This turns on over the next few days.

Running MausBot on your own server

• openmausbot doctor --host checks a Linux server can run MausBot and its bot sandbox, and says how to fix anything that's missing.
• pair --ttl keeps a pairing code open for up to a day, and token create makes tokens for scripts and CI.
• send --task new starts a new conversation in a room.
• Sign-in codes can go out through your own mail server.
• The groundwork for teams on their own servers: a server reachable at your own domain with its own HTTPS, a tunnel when no port can be opened, signed updates that roll back on a failed check, and an audit log the server's owner can read.

Fixes

• The MCP servers API accepts "type": "stdio" for a local command server.

npm: npx openmausbot@0.1.144 · https://www.npmjs.com/package/openmausbot/v/0.1.144