Why? Multi-tenant environments. First, we need to understand a few differences between environments:

• End-user UI
• Agent Runtime Environment
• LLM Server

So

• When you run Claude Code on your local MacBook, the first two are always local. The third is usually the Claude.ai server.
• When you ssh to a virtual private server (VPS) and install Claude Code there, the first two are your remote server. The third is still the Claude.ai server.
• When you run Claude RC on your virtual private server and code from your iPad using the Claude app, the end-user UI is on your iPad, the agent runtime environment is on your VPS, and the server is still Claude.ai.

Most people physically separate their tenancy, such as Claude Code, from their personal vs. work laptops. So in most cases, it's not a big deal.

But when you need multi-tenancy, it becomes super stressful. For example, say you have two different toolkits:

• personal toolkits (personal Notion, personal Sentry, personal Linear)
• workplace toolkits (company Notion, company Sentry, company Linear)

Most MCP auth states or code harnesses don't support profiles, so you can only log in to one.

So therefore... a natural evolution was to have both:

• a personal VPS with all personal toolkits set up
• a workplace VPS with all workspace toolkits set up

to physically isolate tenancies.

Now we've solved the multiple-profile issue, but the client's problems persist. Now let's get back to the environments:

• End-user UI
• Agent Runtime Environment
• LLM Server

All MCP auth or toolkit auth info should always be saved in the Agent Runtime Environment IMHO. However, a surprising number of harnesses tie them to the LLM server (such as Codex Apps or Claude.ai Plugins) or put them in the end-user UI (Claude Desktop or Codex Desktop).

Now the problem is:

• If the auth data is put on the LLM server, you cannot reuse LLM accounts across tenants
• If the auth data is put on the end-user UI, you cannot use the same app to access multi-tenants.

The only way to reliably isolate different auth information is thus:

• You ssh to a virtual private server (VPS) and run Claude Code there. Never use LLM server plugins.

Then

• End-user UI
• Agent Runtime Environment

are both isolated VPS, and

• LLM Server holds no information on the tenancy

This way, you can provide different toolkits, creating multiple dev environments.

• AutoBuilder
• @github@anaclumos@rsc-swr

Goongoom

AGENTS

• Bento Grid에서 Map/GitHub 위젯을 Dynamic Import + BrowserOnly로 지연 로딩하고 SSR 대비 로딩 카드 스켈레톤을 추가함.
• Backlink 모바일/사이드바/본문에서 링크 목록과 발췌 계산을 memoize해 렌더 비용을 줄임.
• React 컴포넌트의 Shuffle 순서를 마운트 기준으로 고정하고 Habit Tracker/Now Playing 파생 데이터를 memoize함.
• Giscus를 클라이언트 전용 lazy load로 전환하고 YouTube/Apple Music 임베드에 loading="lazy"를 적용함.
• 랜덤 페이지에서 sitemap fetch를 useEffect로 분리하고 abort 처리로 Server-side Rendering 렌더 안정성을 개선함.
• React useDeferredValue로 그래프 검색 입력 지연을 적용하고 Fun Facts 리프레시 타이머 정리를 추가함.
• 웹 UI 가이드라인 기준으로 Accessibility 점검을 수행하고 Backlink/Bento Grid/그래프 UI의 ellipsis, aria-live, name/autocomplete, 아이콘 버튼 라벨, 포인터 전용 캔버스 개선 항목을 정리함.
• Accessibility 개선: Backlink ellipsis를 …로 통일하고 로딩 영역 aria-live/role 상태, 그래프 입력 name/autocomplete, Canvas (HTML5) 키보드 조작, 랜덤 페이지 이동을 앵커 기반으로 보완함.