Agents
Connect your agents to Nodus
Use your coding agent or Ask Nodus to work with remote execution, while keeping the same account, team and spending controls as the console.
Connect your tools
Connect Claude Code, Codex, Cursor or another MCP-compatible client through the setup page. Hosted MCP uses browser consent. Local MCP uses your SDK login and can prepare local project files. Hosted connections use verified uploaded assets or connected GitHub repositories.
Review the requested permissions when connecting. Workloads, sandboxes and managed agents have separate read and write access. You can inspect connected agents and disconnect them from the console. Disconnecting a client does not cancel work it already submitted.
Prepare, execute and retrieve
Agents can validate workload requests before paid execution, submit a reviewed command with an explicit budget, inspect status and logs, cancel work and retrieve output metadata or verified downloads. Stable request keys let uncertain submissions be checked without creating a second run. Sandbox and managed-agent tools also honor their account availability and granted permissions.
Use the Python SDK, async client or CLI for scripted workflows. Authenticate with
nodus login, or use a securely stored API key for unattended clients. Code,
data, requested resources, spending limits and result paths remain explicit.
Ask Nodus in the console
The assistant follows your current view and selected workload. It can explain status and measured costs, help prepare a run, edit supported saved draft fields, and guide you to results or the relevant account controls. Ask presents navigation choices. Auto can navigate and act on an explicitly authorized request within its reviewed limits.
Save project preferences for your team, revisit saved chats, or follow up to eight runs for updates while the console is open. Secrets, payment details and OAuth approval stay in their secure browser controls. Preferences and a budget mentioned in a question do not authorize a paid launch.