Your Mattermost server comes with a vibe-code agent: an AI assistant in the Open WebUI chat that can read your config, run mmctl, query the Postgres database, and restart services. You do not need to learn the admin CLI to get everyday things done. Describe the job in plain language, check what the agent proposes, and let it work. Here are ten ordinary jobs worth delegating.

1. Onboard a new teammate end-to-end

New accounts mean a chain of small steps: create the user, add them to the team, add them to the right channels, send a welcome note. The agent can do the whole chain with mmctl and a bot token, and it will show you each command before running it. It also adds people to private channels by name once the account exists, which the self-serve invite flow handles awkwardly. This pays off most when you hire in batches and the fifth account should take no longer than the first. Try: “Create an account for dana@acme.com, add her to the Engineering team and the #dev, #devops, and #announcements channels, then post a welcome message in #dev tagging her.”

2. Offboard someone cleanly

Deactivating a user is one command; the cleanup around it is what gets forgotten. Ask the agent to deactivate the account, remove channel memberships, and list any channel where the person was the last admin so ownership does not stall. It can export their recent files or key conversations first if a handover is needed, and post a short note in your HR channel saying the account was closed and when. Try: “Deactivate john’s account today, remove him from every channel, and give me a list of channels he owned so I can pick new owners.”

3. Find and archive dead channels

Channels pile up until the sidebar is noise. The agent can query the Posts table for channels with no messages in the last 90 days and archive the ones you confirm. It can also flag channels that look dead but still hold the only copies of shared files, so nothing disappears into an archive unread. Archiving hides a channel but keeps its history, and you can unarchive later if the project comes back. Try: “Show me every channel with zero posts in the past 90 days, grouped by team, then archive the ones I say yes to.”

4. Free disk space from old attachments

Uploaded files eat disk faster than messages do. The agent can inspect the FileInfo table, find the largest offenders, files attached to posts that were later deleted, and anything older than a year. Have it show you the list first; deletes should never be a surprise on a chat server where an attachment might be the only copy of a contract. Ask it to move candidates to a backup folder before deleting if you want a safety net. Try: “Find the 25 largest attachments older than 12 months and list what they are before we delete anything.”

5. Enforce channel naming and tidy headers

Left alone, channels end up as #proj-sales, #Sales_2025, and #sales-stuff. Tell the agent your convention and it renames channels with mmctl and sets the purpose and header text to match. It writes out the old-to-new mapping so links and habits survive the change, and a consistent prefix makes the channel directory searchable once you pass a few dozen channels. Try: “Rename all channels that start with ‘proj-‘ to start with ‘p-‘ instead, and set the purpose on #p-alpha to ‘Alpha launch tracking’.”

6. Reconcile team membership

Someone always discovers they were never added to #incidents, on the day it matters. The agent can compare team rosters against your standard channels and add the missing people, then show you exactly who was added. It can also run the reverse check — people who left a team but kept access to its channels — and remove them. Run it monthly and after every reorg. Try: “Everyone on the Engineering team should be a member of #dev, #devops, #support-esc, and #incidents — add anyone who is missing and show me who was added.”

7. Export a channel’s history for your records

Sometimes you need a channel’s conversation as a file: a project closes, a contract gets disputed, an auditor asks. The agent can pull posts between two dates from the database and hand you a readable HTML or text file, with a list of attachments referenced in the range so you know what the file references in the text point to. You get a timestamped artifact that lives outside the chat system, which is the point. Try: “Export everything posted in #legal-review between June 1 and August 31 as an HTML file I can download.”

8. Get honest usage stats

The System Console shows signups and totals, but not which of your 40 channels people actually use. Ask the agent to count posts per channel and per user for the last 30 days. The quiet list tells you what to archive; the busy list tells you where work really happens. Per-user counts are just as revealing: a power user gone quiet for a month is usually a signal worth a human check. Try: “Give me message counts per channel for the last 30 days, sorted descending, and flag anything under 10 messages.”

9. Bulk-import custom emoji

Emoji are culture, and nobody wants to upload 40 PNGs one at a time through the UI. Drop a folder of images on the server and the agent uploads each one through the API with a bot token, using the file name as the emoji name. Refresh the emoji picker and they are all there, including the inside-joke ones. It can also rename or delete an emoji you regret, though messages that used the old name will show raw text afterward. Try: “Import every PNG in /root/emoji-pack as a custom emoji named after its file.”

10. Schedule recurring announcements

Weekly reminders fail because a human has to remember to post them. The agent can register a small cron job that curls an incoming webhook every Monday at 9:00. Ask it to show you the script and the crontab line first, so you know exactly what runs and can change the message later without touching cron yourself. If the target channel ever moves, updating the webhook URL is a one-line change. Try: “Post ‘Reminder: submit your timesheet by Friday 5pm’ to #general every Monday at 9:00, and show me the cron entry.”

None of these require you to learn mmctl or click through the System Console. Say what you want, review the plan, and let the agent type. To get a Mattermost server with the agent already connected: Mattermost on OpenSysLab.