Account and Updates

Your account

The door. When the engineer will not run, one line just above the prompt says why — with or without a conversation open — and clicking it takes you to the remedy.

• add your Anthropic API key in Preferences ▸ Agent to use the engineer — no key yet.
• your sign-in has lapsed — sign in again (File ▸ Sign In) — a sign-in lasts 90 days.

What you may see from Anthropic, on your key, always as plain feed messages:

• your Anthropic API key was rejected — replace it in Preferences ▸ Agent
• your Anthropic account is out of credit — top it up at console.anthropic.com
• your Anthropic account's rate limit — the run waited it out and it did not clear — the engineer waits out a per-minute limit on its own; this appears only when the wait is exhausted (a new account's limits are low, and rise with use).
• Anthropic is overloaded right now — nothing is wrong with your key; try again in a minute
• Anthropic had a server error — nothing is wrong with your key; try again in a moment
• this API key can't use the model you picked — choose another in Preferences ▸ Agent — the key's workspace doesn't have that model.
• your Anthropic organization's data-retention setting doesn't allow this model — the Fable models need 30-day retention; pick another model.
• this conversation no longer fits the model's context window — start a new session, or pick a model with a larger window.
• Anthropic took too long to answer and the request timed out — try again; a lower effort level answers sooner.
• the connection to Anthropic dropped — check your internet connection, then try again.

And two notes that can appear in the conversation itself:

• (The model declined this — Anthropic's safety check stopped the reply …) — nothing from that reply ran (any earlier step of the same message did, and Undo takes it back). A false alarm usually clears if you rephrase, or pick another model. In a run, the same thing reads the model declined this pass.
• (That reply was cut off — I ran out of room …) — ask it to continue, or lower the effort level for shorter thinking.

While the door is shut, the composer keeps your message rather than sending it, and the rest of the DAW is unaffected — audio never depends on the network.

Privacy posture

Your audio, stems, and project files stay on your machine. The service receives the conversation, the compact session snapshot (track names, settings, arrangement structure), and analysis numbers — what the engineer needs to reason — never audio. Help ▸ Report a Problem copies diagnostics with no project content and no account identity.

Updates

• Automatic check shortly after launch (toggleable) + File ▸ Check for Updates… (always reports a result, including "You're up to date").
• An update shows version, build, and release notes; Install & Relaunch downloads, verifies the archive's integrity (SHA-256) and the new app's code signature, swaps the bundle crash-safely (the old app is kept until the new one is in place), and relaunches. Unsaved changes get the normal save prompt first.
• A build whose own signature can't be verified refuses to self-update — a deliberate safety gate.
• ~/Library/Logs/Zammoth/update.log records every attempt.