Ekko Studio v0.7.38 | A link-based service provider import system with seamless local and remote switching v0.7.38 has been released. This update simplifies service provider integration and provides finer control over model APIs; the desktop app now supports switching between local and remote Studio instances. One Link, Import Service Providers Service provider configurations can be shared as links. When opened on desktop or web, a preview import dialog appears first. After selecting the target Profile and completing API Key details, confirmation is required before saving. Imported models become the default model for that Profile; existing service providers with the same name will not be overwritten. Automatic API Mode When adding, editing, or importing a service provider, you can select “Automatic (Match Model)” as the API mode. Studio will automatically match protocols based on known service provider addresses and model rules—no need to fix all models to a single protocol. Model names prefixed with service provider identifiers are also recognized; if no match is found, manual selection remains available. New connections still default to Chat Completions. Model API Keys: Restrict Models and Set Budgets Each API key can be configured to allow access to specific models and set a cumulative USD spending limit. Leaving the limit blank means unlimited usage; setting it to 0 pauses all calls. By default, newly created keys enable all currently available models; newly added models require manual key editing for authorization. Modifying the name, models, or budget does not change the key or reset usage totals. Internal usage is now细分 by Agent, displaying Token count, cache usage, and session numbers. Additionally, cloud access has been added: computers connected to the cloud can provide a fixed model API endpoint, requiring a dedicated key for access. Cloud access is disabled by default and must be explicitly enabled. Ekko Computer Operations: Semantic Matching and Result Validation When Ekko interacts with a computer, JEV can locate UI elements semantically and verify whether the outcome matches expectations. “Desktop Element Semantic Matching” and “Desktop Result Semantic Validation” are located under “Model → JEV,” disabled by default but can be enabled individually—they take effect starting with the next Ekko session. Only element names, types, and enabled/selected states are sent to JEV; input field contents and screenshots are excluded. Validation performs only judgment—no automatic retry of operations. Switch Between Local and Remote Devices Anytime A device button has been added to the top-right corner of the desktop window, listing both local and saved remote Studio instances. Devices can be added, removed, or switched via Device Management. Before switching, the system checks if the target device is available; upon confirmation, the window restarts and connects to the selected device. Login states and website data are isolated between devices. Other Updates - New browser configurations now default to using system proxy; existing configurations remain unchanged - Fixed session saving in DSH ACP 0.2.1—responses are now correctly saved after completion - Chat attachments now validate permissions based on the currently active Profile, fixing authentication errors after Profile switching - Improved TOS 7 installation, upgrade, uninstallation, and reverse proxy entry points; added privacy policy entry; updated vulnerable dependencies - Added preliminary firmware preview for M5Stack Cardputer-Adv over LAN, supporting text and short voice chat; compatible with devices having existing partition layouts—requires manual upgrade
The latest version of the Ekko Studio App is now live. It introduces new features: local model API routing and relay token sharing. In the Ekko Studio App, select “Create Cloud Link Share” to generate a dedicated URL/v1—local models are fully supported. Generate a unique API Key and share both the Key and the URL with your friends. Your friends don’t need to install Ekko Studio or configure any models. They can directly call your model via API and even integrate it into their own agents, software, or scripts. You can monitor usage counts, token consumption, and set limits, pricing, and permissions.
I've noticed that developers on X have been really irritable lately. Today I opened GitHub again to revisit the guide to life.
Upcoming Preview of Ekko Studio | P2P Direct Connection Is Coming To make file transfers faster, we’re enabling the App to connect directly with the desktop version of Studio. The next version will introduce a P2P network. When network conditions permit, the App will establish a direct data connection with Studio, reducing wait times when you access files from your computer or download attachments provided by Agent. This video demonstrates the dynamic effect of direct connection and data transfer. The feature is not yet live—actual speeds will depend on your network environment and bandwidth on both ends, and not all connections will experience the same performance improvement.
