컴퓨트로늄
컴퓨트로늄

컴퓨트로늄

Backlinks (2)
  • 컴퓨트로늄
  • 260618
I prefer CLI
I prefer CLI

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

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.

Backlinks (1)
  • 260619
Debian Setup
Debian Setup

Debian Setup

sudo apt update && sudo apt install git && /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" && echo >> ~/.bashrc && echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)"' >> ~/.bashrc && eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)" && sudo apt-get install build-essential && brew install gcc btop
Backlinks (1)
  • 260415
260204
260204

260204

  • 세상의 확산
Backlinks (1)
  • 세상의 확산
Index
cho.sh
I prefer CLIBB9A08260619260619컴퓨트로늄37A88F컴퓨트로늄0CF03F컴퓨트로늄2C60FB260618260618260418260418260528260528AutoBuilder63849A260419260419Setup9AC296StellaD226F7260415260415Debian SetupD2F701260414260414anaclumos/configs/AGENTS.mdED86A3Ramp의 AX (회사를 AI로 물들이는 법)840774260413260413How to get your company AI pilled46544C260411260411260409260409260407260407260406260406Separating Claude Code Personal Sub and Claude Code Company Sub33A53C
컴퓨트로늄 정의
컴퓨트로늄이 뭐야?

컴퓨트로늄(computronium)은 계산을 수행하는 데 최적으로 설계된 가상의 물질이다.

쉽게 말하면, “물질을 최대한 컴퓨터처럼 만든 것”이다. 일반 컴퓨터는 실리콘 칩, 전선, 냉각 장치, 케이스처럼 계산에 직접 쓰이지 않는 부분이 많다. 컴퓨트로늄은 그런 낭비를 극단적으로 줄이고, 물질의 질량·에너지·구조 전체를 계산에 쓰도록 만든다는 개념이다.

예시로는 다음이 있다.

  • 행성 전체를 컴퓨터로 바꾼 구조
  • 별의 에너지를 둘러싸서 계산에 쓰는 거대 컴퓨터
  • 인간 뇌보다 훨씬 조밀한 인공 신경망 물질
  • 우주 전체를 계산 장치처럼 재구성한다는 극단적 미래 시나리오

이 개념은 주로 SF, 미래학, 인공지능 이론, 트랜스휴머니즘, 우주공학적 상상에서 나온다.

핵심은 이것이다.

컴퓨트로늄 = 계산 효율을 극한까지 높이기 위해 재구성된 물질

현실에 아직 존재하는 물질 이름은 아니다. 물리학적으로 가능한 한계, 열 방출, 에너지 공급, 정보 저장 밀도 같은 제약 때문에 실제 구현은 가설 수준이다.

sudo apt update && sudo apt install git && /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" && echo >> ~/.bashrc && echo 'eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)"' >> ~/.bashrc && eval "$(/home/linuxbrew/.linuxbrew/bin/brew shellenv bash)" && sudo apt-get install build-essential && brew install gcc btop