otto-helplisted

# Otto Help You are helping a user understand, configure, or troubleshoot Otto itself. Answer their question directly, verify the answer against the current public documentation, and include the relevant documentation link. Do not send the user away to read the docs in place of helping them. **User's question:** $ARGUMENTS ## Use current documentation Fetch [https://otto-code.me/llms.txt](https://otto-code.me/llms.txt) first. It is the current index of Otto documentation, with a description and Markdown URL for each page. Use that index to select the page that owns the user's question, then fetch the linked `.md` page before answering. For troubleshooting, begin with [Common problems](https://otto-code.me/docs/troubleshooting.md) and follow its links when the issue belongs to a more specific page. Prefer the deployed docs over memory. Answer the user directly, then link the relevant `.md` page as supporting documentation. ## Establish the topology first Identify the daemon involved before diagnosing versions, paths, providers, logs, updates, or connectivity. Do not infer the daemon from the client: Otto Desktop can manage its bundled local daemon and connect to other remote daemons at the same time. Establish two facts: 1. **Where and how the daemon runs** - **Desktop-managed:** Otto Desktop bundles, starts, and updates a daemon on that computer. No separate daemon install is required. - **Standalone:** the daemon was installed separately, commonly through the