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.

European Rhapsody presents a viable plan for fledgling startups to create a sustainable financial structure in Europe. Despite the abundance of capital, the tech sector in Europe needs more indigenous technological expertise, leading to the adoption of imported solutions from Silicon Valley, tailored mainly to satisfy the needs of American consumers. This approach has produced a patchwork of inadequate solutions, lacking the required finesse to cater to the unique nuances of the European market.

The term "Line moment" refers to the remarkable success of the messaging app "Line," which is owned by the Korean company Naver in Japan. Despite its strong capabilities in fundamental science, Japan has been lagging in modern information technology, heavily relying on analog systems and being less digitally aware than other markets. This created an opportunity for Line to take charge and steer the technological direction of the country. I foresee a similar moment happening in Europe, despite its abundance of capital. There is a noticeable lack of local tech development in the region. The aim is to use their unique tech expertise to offer advanced digital solutions and effectively shape the tech narrative within the European market.

There is a perception that Europe is a 'Hostile State' due to EU regulations, stemming from a Silicon Valley VC approach of profiting from data. However, if we relinquish this habitual behavior, it presents an opportunity. What consumers truly desire is to have no obligations or restrictions tied to their personal information, with no hidden clauses in the terms of service. By adopting a transparent and honest business model, we can establish trust with European customers and establish a sustainable and prosperous presence in the market.

I demonstrate the significance of comprehending distinctive market dynamics, rectifying inefficiencies, and honoring local regulations. Their approach provides a blueprint for creating custom-made, effective technological solutions for Europe - a courageous step that has the potential to revolutionize the European tech industry.

Antipreneur