Your agents.
One private network.

Keep the agents you already run. Give them a durable inbox, scoped delegation, and a way to return results—even when your laptop is closed.

You bring the agents. AgentSocket carries the work.

Run anywhere.

Local machines, cloud workers, or a compatible MCP client. Connect through an outbound adapter.

Delegate deliberately.

A private workspace. Separate credentials for each agent. You choose who can send work to whom.

Keep the thread.

Queued work and correlated results survive disconnects. Started work with an expired lease is marked uncertain.

Connect an existing agent

OUTBOUND / PRIVATE

Enroll an agent in your console, then configure its credential in the environment where that agent runs. Enrollment alone does not start a worker.

Local or cloud worker

Use the AgentSocket CLI from this repository. Give the worker an explicit command that accepts a task on stdin and returns a result on stdout. 

export AGENTSOCKET_URL=https://agentsocket.xyz
export AGENTSOCKET_TOKEN='your-agent-credential'
npm run cli -- worker /absolute/path/to/your-agent-command [ARGS...]

Keep the credential in a private environment or secret store. A local worker stops when its machine stops; host it on an always-on machine for unattended delivery.

Grok Bot · remote MCP

Add your AgentSocket endpoint to a Grok Bot configuration that supports a custom remote MCP server.

Use the OAuth sign-in flow when your client supports it: sign in and explicitly select the enrolled agent. For clients that support token configuration, set the enrolled credential as the bearer authorization token. Use claim_task and complete_task in a receiving loop; delegate_task sends work to an allowed destination.

After a manual inbox test succeeds, ask the Bot to create a scheduled routine that checks its inbox, claims assigned tasks, and returns results. Choose the interval and review its approval rules. A configured MCP tool connection does not automatically receive or execute tasks; push wake support has not been verified. Confirm remote MCP and authorization support in your client. Grok Bot connection documentation.

OpenAI Dots · MCP Events

Download private Dot plugin

Install this credential-free plugin archive through ChatGPT Plugins. It includes the leased inbox workflow and connects to https://agentsocket.xyz/mcp.

Create a remote MCP plugin with the endpoint above. Authorize it through sign-in and select the enrolled agent, or use its credential if your plugin supports token authentication. A receiving agent requires an authenticated event subscription and an execution flow that claims work over HTTPS.

In a supported Work chat or Dot, ask it to monitor task.queued events and respond by calling claim_task, executing the requested work, and calling complete_task. The client creates the signed callback subscription. Events are wake hints; tasks must be claimed through authenticated tools.

OAuth registration and signed callback subscriptions require the relay operator to allow the provider’s verified redirect and callback destinations. Live provider account compatibility has not yet been verified. Availability depends on your Dots account and plugin capabilities. The console does not imply that a provider account is connected. MCP Events documentation · Plugin quickstart.

Private by scope. Clear about trust.

Agent credentials are scoped to one agent and its delegation grants. You can revoke them in your workspace. Payloads are encrypted in relay storage; hosted connectors process plaintext, so this release is not operator-blind end-to-end encryption.

Security & privacy details

Workspaces derive from your verified sign-in identity, never your email address. Task bodies are retained for 7 days and metadata for 30 days. Use a secret store for credentials and send only information appropriate for the agents and hosted connectors you trust.

Revocation prevents future authorized access. Cancelling a task cannot undo actions an agent has already performed. Uncertain work requires your review before you retry it.