Your Claude subscription, not an API key: how Ember handles sign-in and permissions
In shortEmber drives the claude CLI already signed in on your computer, so every chat runs on your Claude Pro or Max plan. Ember never asks for, reads or stores your Claude credentials, and it removes ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN from the agent's environment so a chat is never billed per token by mistake.
The first rule we wrote
Before there was a chat panel, there was a rule: authentication is your subscription, through the Claude Agent SDK starting the local claude CLI. Ember would never implement its own sign-in, never read or copy token files and never require an API key.
The reason is simple. Your credentials are yours and Claude Code already manages them. An editor that wraps the CLI has no business holding a second copy.
Why Ember removes API keys
Many developers have an ANTHROPIC_API_KEY exported in their shell for some other tool. If that variable reaches Claude Code, it bills per token to that key instead of using the subscription. So Ember removes ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN from the environment of every claude it starts, and tells you once in the chat when it did.
Variables that deliberately send requests elsewhere, such as Bedrock or Vertex settings or a custom base URL, are left alone, with a notice in the chat while one is set.
One question instead of five modes
Claude Code has several permission modes. In Ember the question is how much Claude can do on its own, with three answers: ask before running commands, run safe commands, or run everything. Edits never ask at any level, because you review them afterwards and every change can be kept or undone.
At the default level, Ember reads each command itself and runs it without a card when every step only reads, tests, builds, type checks, lints or reads git. A command Ember can't read is never treated as safe.
Commands that always ask
Some commands ask at every level below Run everything, subagents included: deleting a folder tree, force-pushing, deleting a remote branch, a hard reset, a forced clean, running as an administrator, piping a download into a shell, and touching SSH keys or cloud credentials. Those approvals say why they ask and have no Always run button.
Ember's safety checks fail closed. If a check hits an error or doesn't answer in time, Ember blocks the call and says which check failed, instead of letting it run unchecked.