Stella

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.

Photoshop for text -- Stephan Ango

• When I think about editing images, many options come to mind: contrast, saturation, sharpening, blur, airbrush, clone stamp, etc. Even basic image editors offer dozens of useful image manipulation tools
• When I think about editing text, a much narrower definition comes to mind: cut, copy, paste, find, replace, spell check -- nothing that modifies the totality of the writing. This is changing
• Up until now, text editors have been focused on input. The next evolution of text editors will make it easy to alter, summarize and lengthen text. You'll be able to do this for entire documents, not just individual sentences or paragraphs
• Text filters will allow you to paraphrase text so that you can easily switch between prose styles: literary, technical, journalistic, legal, and more. You will be able to easily change an entire story chapter from first-person to third-person narration or transform narrative descriptions into dialogue
• In some ways, it is surprising that filtering text is technically challenging. The text seems easier to manipulate than images. But languages have far more rules than images do
• A reader expects writing to follow proper spelling and grammar, a consistent tone, and a logical sequence of sentences
• I'm excited to see community efforts like Obsidian Ava driving in this direction.