260406
No backlinks found.
No backlinks found.
Why? Multi-tenant environments. First, we need to understand a few differences between environments:
So
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:
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:
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:
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:
The only way to reliably isolate different auth information is thus:
Then
are both isolated VPS, and
This way, you can provide different toolkits, creating multiple dev environments.
I'm sorry to hear you didn't really read much this year...
Maybe things would've been better if you had BookTok: the reading app for the distracted generation™
— Vincent van der Meulen (@vincentmvdm) December 31, 2023
The problem is the mental overload. Texts, even for the highly educated, takes energy to parse and understand. Texts naturally is not as captivating as videos… we need a breakthrough, either technical or user behaviorial
— Sunghyun Cho (@anaclumos) February 1, 2023