AutoBuilder

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.

당근(Karrot)은 대한민국의 중고 거래, 소상공인 홍보 등 생활정보 소프트웨어이다. 중고거래, 지역업체, 질문답변, 부동산, 구인구직 등 지역 내에서 발생하는 생활정보를 검색하고 게시자와 실시간으로 채팅할 수 있다. 당근 서비스 이용자 수가 급증했으며, 중고거래 앱 관심도 설문조사에서 중고나라보다 당근에 더 높은 관심도가 있음이 확인되었다. 당근

당근 후기에 쓸 내용

• 모든 것을 문서화 + 실험
  • 실험은 정말 인상 깊었다
    • 배너 자리로 버튼을 만들어 넣음
  • Kontrol, Airport
• 점진적 배포
• 문화의 날
• 찾고 연구하고 자동화하고 만들고 공개하고
• 블라인드병 (신났는데 자중해야?)
• 공부가 훨씬 재밌어졌다 (연구의 재미)
• 아쉬운 점: 팀이 작다보니 정리되지 않은 부분들이 있었고, 정신없이 목표를 달려가다보니 커맨드 안 내려진 SCV처럼 가만히 멀뚱멀뚱 있게 되는 순간들이 있었다. 아마 내가 더 열심히 찾아 했어야겠지
• 하이퍼로컬?