Your Element server gives your team end-to-end encrypted chat, voice and video calls, and rooms you fully control, with no third party reading along. You run it on your own server, and the vibe-code agent lives inside its chat. You type a request in plain language, and it reads the config, calls the homeserver API, and tells you exactly what changed. Here are ten everyday jobs owners keep handing over.

1. Build your company space tree

Matrix spaces are folders for rooms, and most servers grow them by accident. Ask the agent to design yours on purpose: a top-level space per department, sub-spaces per project, and the standard rooms inside each. It creates them through the client-server API with a bot account, sets join rules, and can also drag your existing rooms into the new structure, which is the tedious part nobody does by hand. Say “Create a space called Acme with sub-spaces for Engineering, Sales, and Support, and put a general room in each.” An hour later the hierarchy exists instead of a flat list of 60 rooms.

2. Spin up a properly configured team room

A default room is flat: everyone can do everything. The agent can set power levels so only leads can pin messages, change the topic, or kick members; pick history visibility; write a real topic; and pin the onboarding links. That stops the slow drift where half the team can’t find the runbook. It uses a bot account with enough privilege to set room state, then shows you the result before people join. Try “Make a private room for the launch team, only @sara:yourserver and I can post for now, and pin the checklist.”

3. Onboard a new teammate end to end

Adding someone to a Matrix server is several small steps: account, invite, the right spaces, a welcome message. Hand the whole chain to the agent. It creates the user through the Admin API, generates an invite token if registration is closed, adds them to the space tree, sets their display name, and sends a welcome DM from a bot so they land in the right rooms on first login. If they forget their password on day two, the agent resets it the same way. “Onboard jordan: give them an account, add them to Engineering, and send a welcome message pointing at the #eng-general room.”

4. Run an announcements room and post as the server

Every company needs one read-mostly room for real news. The agent sets it up with restricted posting so only you and the bot can write, keeps replies open if you want questions, and drafts the posts in your tone. Then you can type “Post to #announcements: the server moves to maintenance this Sunday 02:00–03:00 UTC.” and it goes out under the bot account, formatted, with the date right. Because the bot already holds an access token, scheduled posts and script-driven posts can reuse the same room later.

5. Curate the public room directory

Newcomers find rooms through the directory and through aliases like #engineering:yourserver. Left alone, both fill with dead entries. The agent lists every published room and alias via the Admin API, unpublishes the abandoned ones, and gives active rooms clean canonical addresses. Aliases matter twice: they are what people type to join, and what ends up in old emails and docs. Ask “Clean up the room directory: unpublish anything with no members in 90 days and give the active teams proper aliases.”

6. Spring-clean rooms and accounts

Servers accumulate empty rooms and accounts belonging to people who left months ago. The agent pulls the usage report, lists rooms idle for months, archives the dead ones, and deactivates departed staff, which also wipes their sessions and devices. It always shows the list before deleting anything. “Find rooms with no activity in 6 months and show me which ones you’d archive.” Expect a summary first, a deletion second, and a freed-up disk third.

7. Check encryption health for a user

End-to-end encryption is Element’s strength and its biggest source of support questions. “Unable to decrypt” almost always means an unverified device or missing key backup. The agent inspects the user’s device list and backup status through the server — it can’t read message content, nobody can, but device metadata usually tells the story. Then it walks the user through cross-signing or verifies the new device. “Alice says her new laptop shows garbage in every encrypted room. Check her devices and tell me what’s wrong.”

8. Back up the homeserver and prove the restore works

Your chat history lives in a PostgreSQL database, a media store on disk, and a signing key file that proves your server’s identity. Lose the key and your server becomes a stranger to everyone even with a perfect database. The agent writes a backup script that dumps the database, archives the media, and guards the key, then restores onto a test port and logs in to prove it. A backup you have never restored is a rumor. “Set up nightly backups of Synapse and test-restore them every week; tell me if a restore ever fails.”

9. Decide your federation posture

Federation lets users on other Matrix servers join your rooms. Great for a community, pointless risk for private company chat. The agent checks your config and open ports, then either disables federation cleanly and closes port 8448, or opens it with server ACLs that block abusive homeservers. It can also run your domain through the public federation tester to confirm reachability. “We’re a private team — disable federation and make sure nothing leaks to the public directory.”

10. Rescue a stuck user

Half of all admin work is one user with a weird symptom: a stuck invite, a room that won’t load, a lost security passphrase, messages that refuse to decrypt. Instead of guessing, let the agent read the logs, inspect the room state, rejoin the user by room ID, and clear their stale sessions. Most fixes are boring once diagnosed: the invite went to an old address, or the client cached broken state and needs a clear-cache-and-rejoin. “Bob’s #ops room is stuck loading since yesterday — figure out why and fix it.”

These are everyday jobs, and each takes the agent minutes instead of you an evening. Start with the space tree; it makes everything after it easier.

See it in action

Official walkthroughs from the Element team:

Worth a watch next:

• Element X Launch — the everyday client experience these ten jobs run on.
• Interoperability and federation explained at The Matrix Conference 2025 — useful background for the federation and directory tasks above.

Running Element on your own server already? Element (Matrix) on OpenSysLab