Skip to main content
The neus mount command loads a verified agent’s current context into one bundle:
  • verified identity
  • granted permissions
  • current settings
  • skills and tools
  • trust receipt links
Use it when an assistant or worker should act as a specific profile agent. One command replaces several separate lookups.

​
Quick start

This writes:
  • .neus/mount.json: machine-readable agent context
  • .cursor/rules/neus-agent-my-agent.mdc: agent instructions and trust workflow
Start a new Agent chat in Cursor so the project rules load.

​
Assistant tool

When signed in, call neus_agent_mount with agentId. You can also use agentWallet or the identity receipt ID in identityQHash. The tool returns the same bundle as the command-line interface and is available on every plan. Suggested order:
  1. neus_context
  2. neus_agent_mount when acting as a specific agent
  3. neus_proofs_check / neus_verify_or_guide before sensitive actions

​
SDK

Use resolveRuntimeBundleFromMcp with your MCP transport, then applyRuntimeBundle('cursor', bundle, cwd) for project files. The same bundle shape is returned by the neus_agent_mount MCP tool and the neus mount CLI.

​
Where permissions are enforced

Cursor controls third-party tools inside the editor. NEUS supplies verified context and permissions; your host remains responsible for enforcement.

​
Profile UI

Connect in Cursor on the agent card downloads the project files and copies:
Run that command in your project repo for the full write path.
Last modified on July 14, 2026