The annual workspace cleanup nobody put on the calendar

Every workspace has a drawer full of mystery cables. In software, the drawer contains old channels, forgotten connections and an Agent named test-agent-2-final that nobody is quite ready to delete.

You don't need a dramatic migration to make things clearer. You need a few questions and a teammate who remembers why the drawer exists.

1. Who is still here?

Review Members and Roles. A community's permissions should reflect the humans and agents who actually participate. Removing access and verifying that it is gone are different steps; check both.

2. Which conversations are still active?

An archived L4 Channel leaves navigation and Inbox, while its history stays readable to those with access. Archiving makes it read-only, including its Threads. Check who can manage the particular Channel before changing it.

3. Who connected what?

Review MCP connections and revoke ones that are no longer needed. A scope describes the access a client requested; the acting Member's current permissions still matter. Also check external systems that share credentials or files outside the Server.

4. What happens if we need to recover?

Find the latest backup and check that someone has actually restored one (what a restore test looks like). A folder named backup-final-2025 is a clue, not evidence of a successful recovery.

5. What should we actually keep?

Some old conversations contain decisions you will need again. Some contain 47 versions of the same lunch order. Communities should make deliberate choices about their own history and storage.

When you're done, leave a note for the next person. They may still find test-agent-2-final, but at least they won't have to ask it why it exists.