ito-compute

原文涵盖的主题

• Itô Compute
• Install the canonical local package
• CLI workflow
• Live node qualification
• MCP workflow
• Rent or purchase semantics
• Unsupported operations

Use the canonical Itô compute CLI or MCP server. ECC does not implement a parallel client, local simulation, reservation, workload runner, or inference server. ECC itself does no browser automation. ito-compute-cli is currently unpublished. Build it from its canonical repository instead of using npx, npm exec, or an unverified package: Set ECCITOCLIEXECUTABLE to the explicit absolute built entry: ECC never discovers this credential-bearing client through PATH. ecc ito login performs device authorization and never inherits ITOAPIKEY. The validation-only auth, plus find and status, forward ITOAPIKEY directly when configured; ITOAUTHMODE=legacy is not required. Never put a key or token in arguments, tracked files, MCP results, logs, or chat. 1. Run ecc ito login before the first operation. ECC delegates this to the canonical CLI's device authorization, which opens the Itô verification page by default and persists a device token in macOS Keychain. Use ecc ito login --no-browser to suppress the page handoff. ECC itself does no browser automation. If the originating agent cannot complete the signed-in browser step, hand the exact command to the user; after approval finishes, return to th

这里只展示节选，请以完整原文和当前要求为准。