App Desktop and Store
Find and install tools, choose a source, then apply your configuration and launch the app.
Apps: keep familiar tools together
App Desktop brings together AI clients, CLIs, and related tools. Select an icon to see the accounts and model settings available for that tool on the right. You still use the client you know; EchoBird provides a central place to manage its entry point and supported settings.
Tools do not all support the same operations. Some can switch official accounts, some accept API model configurations, and others mainly provide a launch entry. Check the options actually shown for the selected tool.
An installed tool is not detected
- Confirm that the third-party tool has finished installing and can launch normally from your operating system.
- Return to EchoBird and click Refresh to scan for local tools again.
- If it is still missing, open the tool path settings and check the location of its executable.
- Correct the path and refresh again. Do not point to a launcher from another project, or overwrite an existing account configuration simply to make detection succeed.
Store: from discovery to installation
Store organizes tools that are not installed yet. Select a tool and click Get App to open AI Assistant with an installation request already filled in. Continue the installation based on the assistant’s output and your system environment.
Put an account or model to work in a tool
- Select an installed tool, then choose an official account or an API model. These choices are mutually exclusive, so the client does not receive conflicting identities and endpoints.
- Check the options at the bottom: whether to write configuration and whether to launch at the same time. If you only want to configure the tool, use the options it supports.
- Run the main action and wait for the result. Follow any prompts about a running client or restoring official endpoints.
- Open the client and verify its actual identity and model. A highlight on the right shows your current selection; it does not guarantee that every already-running window switches immediately.
Web Search, Image, and 1M
| Capability | What it configures | What to know |
|---|---|---|
| Web Search | Web search settings for supported tools | Also depends on the model and service capabilities |
| Image | Image input settings for supported tools | Turning it on does not give a text-only model vision capabilities |
| 1M | Large-context mode for supported tools | Actual context length, costs, and limits depend on the tool and service |
The pill buttons are independent and can be enabled separately. In the real client, some tools reapply capability settings when a valid API configuration is already selected; these buttons do not always change appearance alone. If a button is absent, follow the capabilities exposed by the current tool.
A recommended approach
Keep one working official account or model configuration, then establish a clear selection routine for your usual tools. When you need multiple sources and failover, connect the tool to Smart Routes instead of repeatedly changing endpoint addresses inside each client.