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

Binary Search

In computer science, binary search, also known as half-interval search, logarithmic search, or binary chop, is a search algorithm that finds the position of a target value within a sorted array. Binary search compares the target value to the central element of the collection. The half in which the target cannot lie is eliminated if they are not equal. The search continues on the remaining half, again taking the middle element to compare to the target value and repeating this until the target value is found. If the search ends with the remaining half empty, the target is not in the array. Binary search algorithm

Backlinks (6)

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

Binary Search

Warning

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

In computer science, binary search, also known as half-interval search, logarithmic search, or binary chop, is a search algorithm that finds the position of a target value within a sorted array. Binary search compares the target value to the central element of the collection. The half in which the target cannot lie is eliminated if they are not equal. The search continues on the remaining half, again taking the middle element to compare to the target value and repeating this until the target value is found. If the search ends with the remaining half empty, the target is not in the array. Binary search algorithm

Backlinks (6)

260418

I prefer CLI

Binary Search

260418

I prefer CLI

Binary Search