Troubleshooting
Almost all setup issues fall into one of these. Find the one that matches what you're seeing.
"Connect" doesn't finish, or the panel says it can't reach the agent
This means the local agent isn't running or isn't installed yet. Most of the time this is because the one-time setup command hasn't been run, or didn't finish successfully.
- Make sure the setup command from the Quickstart ran to completion without errors in your terminal.
- Click Connect again — the side panel checks for the agent automatically every couple of seconds while the setup screen is open, so you don't need to reopen the extension.
- If it's been stuck for more than a minute or two, fully close and reopen the side panel (click the Trace icon again), then try Connect once more.
"Unidentified developer" (macOS) or "Windows protected your PC" warning
You'll only see this if you used the Download & run it instead option on the setup screen rather than the terminal command. It's expected — the file isn't code-signed yet, so your operating system flags it the first time. It is not a sign that anything is wrong.
If the warning dialog only gives you "Done" or "Move to Bin," don't use either. Instead, open your Downloads folder, right-click the file named trace-setup.command, and choose Open. That gives you an explicit "Open" button that a regular double-click doesn't.
Click More info, then Run anyway.
Prefer to skip this warning entirely? Use the terminal command from the Quickstart instead — it installs the exact same agent without triggering either warning.
"Our servers are experiencing high demand right now"
This means the specific model you're using is briefly at capacity upstream — not a Trace outage, and not something wrong with your account or your message. It usually clears up within a minute.
- Wait a few seconds and send your message again.
- If it keeps happening on the same model, switch models from the picker in the side panel and try again.
Still stuck — doing a full reset
If Connect is stuck in a way the steps above don't fix, removing the local agent and reinstalling it clears almost everything. This only removes the local agent itself — it does not touch your project files.
rm -f ~/.local/share/trace-rust/trace-http-bridge
rm -rf ~/.local/share/trace-rust/native-host
rm -f ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/dev.gettrace.rust.host.jsonThen reload the extension (or restart Chrome) and run the setup command from the Quickstart again.