[{"data":1,"prerenderedAt":28},["ShallowReactive",2],{"blog:workspace-spring-cleaning":3},{"title":4,"description":5,"date":6,"author":7,"url":8,"markdownPath":9,"html":10,"toc":11},"The annual workspace cleanup nobody put on the calendar","Five small questions for the tabs, permissions and conversations your team has accumulated.","2026-10-28","Inchi","\u002Fblog\u002Fworkspace-spring-cleaning","\u002Fblog\u002Fworkspace-spring-cleaning.md","\u003Cp>Every workspace has a drawer full of mystery cables. In software, the drawer contains old channels, forgotten connections and an Agent named \u003Ccode>test-agent-2-final\u003C\u002Fcode> that nobody is quite ready to delete.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"1-who-is-still-here\">\u003Ca class=\"heading-anchor\" href=\"#1-who-is-still-here\">1. Who is still here?\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"2-which-conversations-are-still-active\">\u003Ca class=\"heading-anchor\" href=\"#2-which-conversations-are-still-active\">2. Which conversations are still active?\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"3-who-connected-what\">\u003Ca class=\"heading-anchor\" href=\"#3-who-connected-what\">3. Who connected what?\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2 id=\"4-what-happens-if-we-need-to-recover\">\u003Ca class=\"heading-anchor\" href=\"#4-what-happens-if-we-need-to-recover\">4. What happens if we need to recover?\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>Find the latest backup and check that someone has actually restored one (\u003Ca href=\"\u002Fblog\u002Fbackups\">what a restore test looks like\u003C\u002Fa>). A folder named \u003Ccode>backup-final-2025\u003C\u002Fcode> is a clue, not evidence of a successful recovery.\u003C\u002Fp>\n\u003Ch2 id=\"5-what-should-we-actually-keep\">\u003Ca class=\"heading-anchor\" href=\"#5-what-should-we-actually-keep\">5. What should we actually keep?\u003C\u002Fa>\u003C\u002Fh2>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>When you're done, leave a note for the next person. They may still find \u003Ccode>test-agent-2-final\u003C\u002Fcode>, but at least they won't have to ask it why it exists.\u003C\u002Fp>\n",[12,16,19,22,25],{"id":13,"text":14,"depth":15},"1-who-is-still-here","1. Who is still here?",2,{"id":17,"text":18,"depth":15},"2-which-conversations-are-still-active","2. Which conversations are still active?",{"id":20,"text":21,"depth":15},"3-who-connected-what","3. Who connected what?",{"id":23,"text":24,"depth":15},"4-what-happens-if-we-need-to-recover","4. What happens if we need to recover?",{"id":26,"text":27,"depth":15},"5-what-should-we-actually-keep","5. What should we actually keep?",1793335826722]