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.

• Handling Agents with Love
• Separating Claude Code Personal Sub and Claude Code Company Sub

• TSMC
• The Shadows Strikes Back (interface buttons)
• 무제한 번역
• 인쇄해서 보면 오류가 보인다
• Korean Discount
• R=VD and Generative AIs
• Prompt Injection
• AI 단톡방
• You can do everything on computers but you really should not
• Everyone has their intern now; Everyone is a CEO
• 언어학과 우주적 소음
• Are Social Networks drugs and are tech companies pharmaceutical companies?
• database wrappers
• pipe companies dumb pipe cloudflare openai
• nintendo and emulators free cash grab? platform expansion
• Notion and Zawinski's law
• neural computer clock engine digital
• diminishing openai cost
• 모두가 일하러 모이는 곳과 자부심
• 피상적인 직업 - 검색 기술사와 프롬프트 엔지니어
• 크롬 주소창 제미니
• Turing Complete Transformers
• DOS
• 전화교환원
• 워크비자는 족쇄인가?
• 뉴욕 줌 가판대 - 월급이란?
• meta ai, llama and react
• database wrappers
• accountability
• free car
• 와비파커
• 야크쉐이빙
• time to regulate psychiatric drugs social network
• 구글 조급해 말라
• analog is power
• 비스마르크
• 차상위 시민권
• Do not use location or particle-dependent UX writing
• Lindy Effect
• Chestertons fence
• Gustafson's Law
• hypnagogic inspiration
• nonintrusive computing
• Heath's Resume