I prefer CLI

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

End-user UI
Agent Runtime Environment
LLM Server

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.

Backlinks (1)

260619

JSX

JSX (JavaScript Syntax Extension and occasionally referred to as JavaScript XML) is a React extension to the JavaScript language syntax, which provides a way to structure component rendering using syntax familiar to many developers. It is similar in appearance to HTML. React components are typically written using JSX, although they do not have to be, as components may also be written in pure JavaScript. JSX is similar to another extension syntax created by Meta (formerly Facebook) for PHP called XHP. JSX (JavaScript)

Backlinks (3)

I prefer CLI

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

End-user UI
Agent Runtime Environment
LLM Server

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

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.

Backlinks (1)

260619

JSX

Warning

This post is more than a year old. Information may be outdated.

JSX (JavaScript Syntax Extension and occasionally referred to as JavaScript XML) is a React extension to the JavaScript language syntax, which provides a way to structure component rendering using syntax familiar to many developers. It is similar in appearance to HTML. React components are typically written using JSX, although they do not have to be, as components may also be written in pure JavaScript. JSX is similar to another extension syntax created by Meta (formerly Facebook) for PHP called XHP. JSX (JavaScript)

Backlinks (3)

260409

I prefer CLI

JSX

260409

I prefer CLI

JSX