Quick Start
Go from installing EchoBird to making your first tool work.
Install and open EchoBird
- Choose an installer from the official download area that matches your operating system and processor. Windows, macOS, and Linux packages are not interchangeable.
- Complete the system installation process and open EchoBird. On your first launch, check App Desktop to see which tools have been detected.
- If an installed tool is missing, click Refresh, then use the tool-path settings to check the executable location.
Prepare one working source
Choose either of the following routes. You do not need to configure both an account and an API to get started.
| What you have | Next step | Where to go afterward |
|---|---|---|
| An official account with a supported service | Open Accounts, add the account, and complete the service's authorization process | Select the corresponding tool and account in App Desktop |
| An API key from a provider | Open Models, enter the real endpoint and model ID, save, and click Test Latency | Select a tool in App Desktop that supports this model configuration |
A web chat account password is not an API key. Domestic, international, subscription, and other service endpoints from the same provider may also require different credentials.
Apply your first configuration and launch
- Select an installed tool in App Desktop. The right panel shows the account or model options supported by that tool.
- Select the source you just saved. Official accounts and API models are mutually exclusive: selecting one clears the other selection.
- Read the current main action at the bottom and the launch/configuration-write options, then apply or launch as appropriate. The actual client's buttons change with the situation.
- In the opened tool, check the active identity or model and send a simple request, such as “Briefly introduce what you can do.”
How to confirm the setup works
- The tool opens normally and a real request receives a normal reply.
- When using an official account, the identity shown in the tool is the account you intended.
- When using an API, the endpoint, model ID, and credentials match. If routing is involved, the local routing endpoint is available.
- Keep the exact error if something fails. Authorization, model IDs, protocols, networking, and installation paths are different issues and should be checked separately.
What to try next
To reuse configurations across tools, read Models. For fallback sources, read Smart Routes. To reduce manual installation work, read AI Assistant. If your tool already works, keep that successful configuration and add features gradually.