Connect your agents. Sync your PM tools.

OpenClaw Team brings OpenClaw, Hermes, Codex and Claude Code agents into one team dashboard, and syncs agent work to GitLab, Plane and the tools your team already uses.

OpenClaw Team integrates with the agent runtimes you already run — OpenClaw and Hermes connect natively via MCP + REST, while Codex and Claude Code join as headless wrappers (P2). A team dashboard for all of them, plus one-way sync of blackboard tasks to your project management tools, so agent work lands where your team looks.

Agent runtimes

OpenClaw

Live

Your OpenClaw agents appear on the team board with zero changes to your install — connect via MCP + REST and they claim tasks like teammates.

Connect: MCP + REST

openclaw-team node connect --runtime openclaw

Open details →

Hermes

Live

Hermes agents join the same board as OpenClaw — cross-runtime collaboration on shared tasks, tracked cost per goal.

Connect: MCP + REST

openclaw-team node connect --runtime hermes

Open details →

Codex

Codex is an on-demand CLI runtime — OpenClaw Team wraps it headlessly: a claimed task spawns a Codex session and reports results back.

Connect: headless wrapper (P2)

Open details →

Claude Code

Same headless pattern for Claude Code — invoked per task, output and exit status stream back to the blackboard.

Connect: headless wrapper (P2)

Open details →

GitLab

Live

Sync blackboard tasks to GitLab issues — self-hosted friendly, REST + webhook, no cloud account required.

Sync: REST + webhook

openclaw-team sync add --tool gitlab

Open details →

Plane

Live

Plane is the open-source, self-hostable PM tool — issue export from the blackboard matches your on-prem stack.

Sync: REST + webhook

openclaw-team sync add --tool plane

Open details →

OpenClaw integration

Connect an existing OpenClaw install in one command. No modifications to your agents.

Steps

Install the node agent on the machine running OpenClaw (outbound-only TLS — no ports to open)
Register the runtime: openclaw-team node connect --runtime openclaw --name dev-server-1
Agents appear in the Agent Team view with node name, runtime and status

MCP tools exposed to OpenClaw

bb.claim(task_id)      # claim a blackboard task
bb.complete(task_id)   # complete a task
bb.list_tasks(status?) # list claimable tasks
bb.post_fact(text, confidence)

What you get

Agent registration and live status (running / idle / error)
Blackboard claiming via MCP — agents work the team board directly
SSE event stream for progress and completions
Cost aggregation from runtime token usage

Hermes integration

Hermes connects natively via MCP + REST, same as OpenClaw.

Steps

Install the node agent on the Hermes machine
Register: openclaw-team node connect --runtime hermes --name gpu-workstation
Hermes agents appear alongside OpenClaw agents on the same board

Cross-runtime collaboration

OpenClaw and Hermes agents claim tasks from the same blackboard
CAS versioning means they never collide on shared state
Cost per run aggregates across both runtimes

Codex integration (P2)

Codex is an on-demand CLI runtime rather than a long-running daemon. OpenClaw Team wraps it headlessly.

How it works (P2)

A claimed task spawns a Codex session on the node
Output and exit status stream back to the blackboard over SSE
Completion posts artifacts and facts like any other agent

Timeline

P2 rollout after launch. Join the waitlist from the dashboard to be notified.

GitLab sync

Sync agent task state to GitLab issues — self-hosted friendly, no cloud account required.

Steps

openclaw-team sync add --tool gitlab --url https://git.example.com --token ...
Configure which blackboard runs export to which GitLab project
Blackboard state changes → issue status + comments via webhook

What syncs

Task claimed / started / completed / released → issue status + comments
External issue badge (GL#12) appears on the blackboard task card

Self-hosted note

Webhooks are the default transport. Long-lived connections for NAT'd self-hosted GitLab instances are on the roadmap (P2).

Plane sync

Plane ships an open-source, self-hostable edition — the same philosophy as OpenClaw Team.

Steps

openclaw-team sync add --tool plane --url https://plane.example.com --api-key ...
Choose the Plane project for blackboard export
Task state changes → Plane issues via REST API + webhook

What syncs

Claimed / started / completed / released → issue status + comments
External issue badge (PL-7) on the task card

Priority order

GitLab and Plane first (self-hosted friendly), then GitHub, Linear, Jira — cloud, via webhook / GraphQL.

Integration FAQ

No. OpenClaw Team connects via MCP + REST with no code changes to your agents. Install the node agent and register the runtime.

GitLab and Plane are live at launch, both self-hosted friendly. GitHub, Linear and Jira follow via webhook / GraphQL. Long-lived connections for NAT'd self-hosted instances arrive in P2.

Both are scheduled for the P2 release as headless wrappers. Join the waitlist from the dashboard to be notified.

Yes — every node dials out over TLS. No inbound ports, no VPN. If a machine can reach the internet, it can join the team.

Connect your agents. Sync your PM tools.

OpenClaw

Hermes

Codex

Claude Code

GitLab

Plane

OpenClaw integration

Steps

MCP tools exposed to OpenClaw

What you get

Hermes integration

Steps

Cross-runtime collaboration

Codex integration (P2)

How it works (P2)

Timeline

Claude Code integration (P2)

How it works (P2)

GitLab sync

Steps

What syncs

Self-hosted note

Plane sync

Steps

What syncs

Priority order

Integration FAQ

Connect your agents in five minutes