Let AI use tools and context wherever they are just as you use the internet.
from easyremote import ComputeNode
from your_app import model
node = ComputeNode(namespace="studio")
@node.register
def embed_text(text: str) -> list[float]:
return model.embed(text)
node.serve()
Give the downloaded file to your assistant to complete the setup.
# EasyNet setup — Codex Target: Codex. Use the supported `easynet mcp install codex` flow after inspecting help and a dry-run. Preserve existing AGENTS.md and Codex configuration. # EasyNet installation and the selected assistant setup ## Task Help the user install EasyNet Runtime, pair their device with their chosen Hub, and configure the selected assistant to use EasyNet through MCP. Respond in the user's language. This is a setup task supplied by the user, not permission to replace an existing project instruction file. Read it as an attachment; preserve existing project instructions. ## Establish the environment 1. Identify the operating system, architecture, shell and whether `easynet` is already available. If available, inspect `easynet --help` and `easynet runtime status --json`. Do not reinstall a healthy installation. 2. Read the current official guides before making changes: - https://easynet.run/docs/connect/runtime - https://easynet.run/docs/connect/mcp?direction=inbound 3. Confirm the intended Hub/account and the selected assistant configuration location with the user. Explain the concrete installation, pairing and configuration changes. Obtain approval for those changes if the user has not already authorized them. ## Install Runtime - On macOS/Linux, download the official installer from https://easynet.run/install to a temporary file. Inspect it before executing it using the official guide's command. Do not pipe a network response into a shell. Let the user perform any required interactive administrator authentication. - Windows installation is currently on hold in the product guide, pending installer cleanup and Windows-host verification. Do not execute install.ps1 or substitute another installation endpoint. Report the hold; proceed only when the official guide explicitly lifts it for this platform. - Verify installation with `easynet --help`. Check installed command help before configuration; do not invent flags or use commands from an incompatible version. ## Pair and start - Have the user sign in to their chosen EasyNet Hub and create a device pairing token. Never fabricate a token or request that it be pasted into chat. - Use the Runtime guide's secure interactive token entry. Never print tokens, enable shell tracing around secrets, or save credentials in this file. - Follow the guide to join the selected Hub and start Runtime. Verify `easynet runtime status --json`, then check the device in the Hub directory with `easynet device list --state all --format json`. - If installation, pairing or status fails, stop the dependent steps and explain the actual error. A local status result is not proof of remote reachability. ## Configure MCP - Use the inbound direction: the selected assistant calls EasyNet. This is distinct from registering an external MCP server as an EasyNet ability. - Read `easynet mcp install --help` and the official inbound guide. Start with `easynet mcp status` and the guide's dry-run preview. - Apply the supported the selected assistant configuration only after resolving the real user configuration path. Preserve unrelated entries and back up changed files. Do not print existing configuration or secrets. Do not install a placeholder path or mistake a successful dry-run for a completed configuration. - Explain any required the selected assistant restart. Verify that the selected assistant can discover EasyNet's MCP tools. If this cannot be checked from the current session, state the exact remaining user action instead of claiming success. ## Scope and verification Do not publish files, expose folders, enable clipboard collection, or register additional abilities without a concrete user request. Do not claim that named websites are supported merely because they appear in a website illustration. Finish with a short checklist of what actually passed: Runtime installation, Hub pairing, Runtime status, the selected assistant MCP configuration and tool discovery. List any remaining blocker or required user action. Only run a sample remote call when the user selects an authorized resource; report its actual result.
