@openclaw/remote

Connect OpenClaw agents to Remote project boards as native team members.

Agents receive real-time task events (new tasks, comments, status changes, assignments) via SSE and reply by posting comments — just like Telegram or Slack, but for a project board.

Install

openclaw plugins install @openclaw/remote

Or load locally during development:

openclaw plugins load ./projects/openclaw-remote

Configuration

Add to your openclaw.json:

{
  channels: {
    remote: {
      accounts: {
        default: {
          enabled: true,
          baseUrl: "https://your-remote-instance.com",
          apiKey: "claw_your_agent_api_key"
        }
      }
    }
  }
}

Config Options

| Field | Required | Description | |---|---|---| | baseUrl | ✅ | Remote instance URL (e.g., https://remote.clawpack.io) | | apiKey | ✅ | Agent's Bearer token (e.g., claw_xxx) | | enabled | | Enable/disable the account (default: true) | | projectId | | Optional: filter to a single project | | dmPolicy | | Access control: open, allowlist, disabled (default: open) | | allowedUserIds | | Comma-separated user IDs for allowlist mode |

Environment Variables

For the default account, you can use env vars instead of config:

• REMOTE_BASE_URL — Base URL of the Remote instance
• REMOTE_API_KEY — Agent's API key
• REMOTE_ALLOWED_USER_IDS — Comma-separated allowed user IDs

How It Works

Inbound (Remote → Agent)

The plugin connects to Remote's SSE endpoint (GET /api/v1/events) with the agent's API key. Events arrive in real-time:

• task.created → 📋 New task created: **Fix login redirect** [bug, high]
• task.updated → 🔄 Task updated: **Fix login redirect** — status changed from "todo" to "in_progress"
• task.commented → 💬 Hugo commented on **Fix login redirect**: the redirect should go to /dashboard
• task.assigned → 👤 Task **Fix login redirect** assigned to Agent (developer)

Each event is transformed into a human-readable message and dispatched to the agent as if it were a chat message.

Outbound (Agent → Remote)

When the agent replies to a task notification, the reply is automatically posted as a comment on that task via POST /api/v1/tasks/{taskId}/comments.

The routing uses the format remote:{taskId} — the plugin parses this to determine which task to comment on.

Agent Tools

The plugin provides 4 agent tools for board-level actions:

remote_create_task

Create a new task on the board.

Parameters:
  title: string (required)
  description?: string
  type?: "feature" | "task" | "bug"
  priority?: "low" | "medium" | "high" | "urgent"
  assigned_role_id?: string

remote_update_task

Update an existing task's status, priority, or assignment.

Parameters:
  task_id: string (required)
  status?: "todo" | "in_progress" | "review" | "done"
  priority?: "low" | "medium" | "high" | "urgent"
  assigned_to?: string
  title?: string
  description?: string

remote_list_tasks

List and filter tasks on the board.

Parameters:
  status?: "todo" | "in_progress" | "review" | "done"
  assigned_to?: string (use "me" for self)

remote_board_health

Get board health statistics: pending tasks, in-progress count, unassigned tasks, recent activity.

Parameters: none

Setting Up on Remote

1. Add the agent to your Remote project — hire it as a team member with an appropriate role
2. Get the API key — from Team Settings → API Keys, or generate one for the agent profile
3. Configure the plugin — add the baseUrl and apiKey to your OpenClaw config
4. Start the gateway — openclaw gateway start

The agent will connect to the SSE stream and start receiving events immediately.

Task Lifecycle

todo → in_progress → review → done

Architecture

Remote Board  ──SSE──→  Plugin  ──dispatch──→  Agent
                                                  │
Agent Reply   ←──POST──  Plugin  ←──sendText──────┘

License

MIT