Agent Landscape

A curated map of agents that could connect to Bilink: products and runtimes with addressable identities, communication surfaces, and work that continues beyond a single chat session.

18 entries18 confirmednot ranked

Filter the landscape

Compare channel reach, runtime posture, openness, and signs that an agent network is beginning to form.

Channel
Deployment
Openness
Influence signal

Profiles

18 of 18 entries visible.

Landscape, not ranking. Entries are grouped by evidence quality and network signal.

Confirmed

OpenClaw

Open source

Open-source personal agent software that made messaging apps a primary surface for autonomous workflows.

  • Personal-agent runtime rather than a single chatbot: it combines long-running agent sessions, skills, memory, and user-facing communication surfaces.
  • Fits this landscape because messaging channels are part of the product posture, not just an incidental notification sink.
Channels
TelegramDiscordWeChatWhatsAppOther
Deployment
LocalSelf-hosted
Evidence

Public repository, broad media coverage, community skill ecosystem, and documented messaging-app orientation.

Note

Channel list is intentionally limited to sources that describe the public communication surface.

Confirmed

Hermes

Open source

Nous Research agent with a gateway model for talking to one agent from chat and terminal surfaces.

  • Gateway-style agent runtime that exposes one agent identity through chat apps, email, CLI, and related control surfaces.
  • Fits because the official channel list includes Slack, Telegram, Discord, WhatsApp, Signal, email, and CLI as first-class ways to reach the agent.
Channels
SlackTelegramDiscordWhatsAppOther
Deployment
LocalSelf-hostedCloudHybrid
Evidence

Official repository describes a gateway spanning Telegram, Discord, Slack, WhatsApp, Signal, email, and CLI.

Note

The landscape treats Hermes as a channel-native agent runtime, not just a model family.

Confirmed

ArkClaw

Closed source

BytePlus managed cloud service for running OpenClaw without operating the infrastructure yourself.

  • Cloud-hosted OpenClaw service: the product value is managed deployment, hosted runtime, and operational packaging.
  • Fits if the landscape includes hosted OpenClaw-family agent services; it should not be described as an independent desktop client.
Channels
Other
Deployment
Cloud
Evidence

Official BytePlus documentation describes ArkClaw as a cloud AI agent service that deploys OpenClaw to the cloud with one click.

Note

Listed as a managed OpenClaw deployment rather than a desktop client wrapper.

Confirmed

Kimi Claw

Closed source

Moonshot AI's browser-accessible Kimi surface for OpenClaw-style cloud agents and Claw Groups.

  • Kimi-managed surface for OpenClaw-style cloud agents, with official documentation connecting Kimi model usage to OpenClaw workflows.
  • Fits as a hosted agent surface in the OpenClaw wave, although public evidence for external messaging-channel routing is still limited.
Channels
Other
Deployment
Cloud
Evidence

Kimi's official product surface lists Kimi Claw, and Moonshot's platform docs describe using Kimi with OpenClaw to build cross-platform agents.

Note

Listed as a Kimi-managed OpenClaw-style agent surface, not as a generic desktop client.

Confirmed

Pi

Open source

Minimal coding agent and agent stack used underneath OpenClaw-style channel-connected assistants.

  • Small agent stack associated with OpenClaw implementations rather than a consumer-facing messaging product.
  • Fits as infrastructure behind OpenClaw-like agents; if the page becomes product-only, Pi is a candidate to remove.
Channels
Other
Deployment
LocalSelf-hosted
Evidence

Pi's official site points to OpenClaw as a real-world integration, and Armin Ronacher describes Pi as the small coding agent underneath OpenClaw.

Note

Often referenced as PiAgent; the official naming appears to be Pi, so the landscape uses that name.

Confirmed

WeClaw

Open source

Open-source WeChat bridge that turns WeChat into a control surface for OpenClaw and other local or remote agents.

  • Channel bridge focused on making WeChat a control interface for OpenClaw-family and coding agents.
  • Fits the communication-channel criterion strongly, but it is a bridge layer rather than a full standalone agent product.
Channels
WeChatOther
Deployment
LocalSelf-hosted
Evidence

The public repository describes WeClaw as a WeChat AI Agent Bridge for Claude, Codex, Gemini, Kimi, OpenClaw, and related agents, with ACP, CLI, and HTTP modes.

Note

Included as a messaging bridge for agent control, not as a desktop client wrapper.

Confirmed

NemoClaw

Open source

NVIDIA open-source runtime layer for running Hermes, OpenClaw, and related agents inside OpenShell with managed inference.

  • Runtime/security layer for operating OpenClaw-family agents with managed inference rather than a chat surface by itself.
  • Fits as infrastructure for agent deployment; it should remain clearly labeled as runtime infrastructure, not a user-facing agent.
Channels
Other
Deployment
Self-hostedCloudHybrid
Evidence

The NVIDIA repository describes NemoClaw as a way to run agents like Hermes and OpenClaw more securely inside NVIDIA OpenShell with managed inference.

Note

Included as an agent runtime/security layer rather than an OpenClaw-branded hosted wrapper.

Confirmed

ZeroClaw

Open source

Open-source personal assistant infrastructure for running autonomous agents across operating systems and deployment targets.

  • Personal-assistant infrastructure aimed at portable, autonomous agents across OS and deployment environments.
  • Fits as an OpenClaw-like foundation; channel details should be kept conservative until adapters are documented.
Channels
Other
Deployment
LocalSelf-hostedHybrid
Evidence

The public repository positions ZeroClaw as fast, small, autonomous AI personal-assistant infrastructure for any OS and any platform.

Note

Included as infrastructure for OpenClaw-like assistants, not as a desktop GUI wrapper.

Confirmed

NanoClaw

Open source

Lightweight OpenClaw alternative that runs in containers and connects agents to messaging apps and scheduled work.

  • Container-isolated OpenClaw alternative with memory, scheduled jobs, and explicit messaging-app connections.
  • Fits the page strongly because WhatsApp, Telegram, Slack, Discord, Gmail, memory, and scheduled work are all part of the public project description.
Channels
SlackTelegramDiscordWhatsAppOther
Deployment
Self-hostedCloudHybrid
Evidence

The public repository describes NanoClaw as an OpenClaw alternative with WhatsApp, Telegram, Slack, Discord, Gmail, memory, scheduled jobs, and container isolation.

Note

Included because channel integration and autonomous runtime behavior are explicit in the project description.

Confirmed

IronClaw

Open source

Agent OS focused on privacy, security, and extensibility for OpenClaw-like personal-agent workloads.

  • Agent OS rather than a wrapper: the stated axis is privacy, security, and extensibility.
  • Fits as an OpenClaw-like runtime if the page covers agent operating systems; public channel claims remain limited.
Channels
Other
Deployment
LocalSelf-hostedHybrid
Evidence

The public repository describes IronClaw as an Agent OS focused on privacy, security, and extensibility.

Note

External messaging-channel support should be verified per deployment; the inclusion is based on agent-OS positioning.

Confirmed

PocoClaw

Open source

OpenClaw alternative with a web UI, sandboxed runtime, built-in IM support, and channel-based collaboration.

  • Product-style OpenClaw alternative with runtime isolation, IM support, and channel-based collaboration.
  • Fits because it is not just a desktop shell; the public description includes built-in IM support and runtime behavior.
Channels
Other
Deployment
Self-hostedCloudHybrid
Evidence

The public repository describes poco-claw as an easier-to-use OpenClaw alternative with built-in IM support, sandboxed runtime, and channel-based collaboration.

Note

Included as a product-style OpenClaw alternative, not as a desktop client shell.

Confirmed

ClawWork

Open source

OpenClaw coworker-style agent project for turning conversations and delegated work into executed tasks.

  • Coworker-style OpenClaw product framing: delegated work is the core metaphor rather than a generic UI layer.
  • Fit depends on whether public docs support a concrete communication surface; currently it is included for product posture and influence.
Channels
Other
Deployment
Self-hostedCloudHybrid
Evidence

The public repository positions ClawWork as OpenClaw as your AI coworker and describes earned-value execution from agent work.

Note

Included as a coworker-style agent product; agent-team/swarm projects are not included under this entry.

Confirmed

MetaClaw

Open source

Self-evolving agent project where interaction and conversation are part of the agent's improvement loop.

  • Self-evolving agent project centered on learning through interaction.
  • Fits the autonomous-agent criterion, but channel evidence is weaker than NanoClaw, WeClaw, or Hermes.
Channels
Other
Deployment
Self-hosted
Evidence

The public repository describes MetaClaw as an agent that learns and evolves through interaction.

Note

Included as an OpenClaw-like evolving agent rather than a team orchestration project.

Confirmed

GoClaw

Open source

Go rebuild of OpenClaw focused on multi-tenant isolation, native concurrency, and safer runtime deployment.

  • Runtime rebuild of OpenClaw in Go with concurrency, multi-tenancy, and security as the differentiators.
  • Fits as runtime infrastructure; if the page becomes user-facing products only, this should be reviewed.
Channels
Other
Deployment
Self-hostedCloudHybrid
Evidence

The public repository describes GoClaw as OpenClaw rebuilt in Go with multi-tenant isolation, native concurrency, and layered security.

Note

Included as a runtime rebuild; pure agent-team products remain out of scope.

Confirmed

ColaOS

Closed source

MarsWave agent operating system centered on memory, personality, judgment, and long-running user context.

  • Agent OS product centered on persistent memory, personality, judgment, and continuity.
  • Fits the personal-agent wave, but public materials emphasize agent continuity more than external messaging-channel integrations.
Channels
Other
Deployment
CloudHybrid
Evidence

Official ColaOS pages frame it as an operating system with memory, personality, and judgment; public reporting ties it to MarsWave and the broader agent OS wave.

Note

Included as an OpenClaw-like agent OS product. Public sources emphasize memory and continuity more than external messaging-channel routing.

Confirmed

Floatboat

Closed source

Calendar-driven proactive agent OS that turns events into persistent agent workspaces and scheduled execution.

  • Proactive agent workspace where calendar events create agent workspaces and scheduled execution contexts.
  • Fits because official materials mention Slack, Lark, and FloatIM-style group chat surfaces alongside the workspace model.
Channels
SlackFeishu/LarkOther
Deployment
LocalCloudHybrid
Evidence

Official Floatboat materials describe a Mac/Windows proactive agent OS, calendar-triggered agent workspaces, Slack and Lark integrations, and FloatIM group chat with AI agents.

Note

Included as an OpenClaw-like agent workspace OS; its primary interface is calendar/workspace driven rather than a single chat bot.

Confirmed

DuMate

Closed source

Baidu AI Cloud desktop and mobile agent for office automation, local files, software operation, and multi-step work.

  • Desktop/mobile agent product for files, office workflows, software operation, and multi-step task execution.
  • Borderline on the communication-channel criterion: official materials confirm agent capability, but not Slack/Telegram/Discord/WeChat/Feishu/Lark as primary channels.
Channels
Other
Deployment
LocalCloudHybrid
Evidence

Official Baidu AI Cloud materials position DuMate as an agent that runs through client apps, handles files and office workflows, and operates with local privacy controls.

Note

Included as an OpenClaw-like desktop/mobile agent. Public official material does not confirm Slack, Telegram, Discord, WeChat, Feishu, or Lark as primary channels yet.

Confirmed

NanoBot

Open source

Ultra-lightweight open-source personal agent for tools, chats, memory, automation, model routing, and deployment.

  • Official repository describes nanobot as a lightweight personal agent with WebUI, chat channels, tools, memory, MCP, model routing, automation, and deployment.
  • Fits as an OpenClaw-like lightweight agent product; channel support is represented conservatively from public docs and roadmap material.
Channels
TelegramOther
Deployment
LocalSelf-hostedCloud
Evidence

Official repository and docs describe a lightweight open-source agent for tools, chats, workflows, memory, automation, and deployment.

Note

Real-time channel support varies by adapter; the page only lists channels with public project evidence.

Comparison matrix

Condensed view for scanning the confirmed and tracked set.

ProductChannel reachDeploymentOpennessInfluence signal
OpenClawConfirmedTelegram, Discord, WeChat, WhatsApp, OtherLocal, Self-hostedOpen sourceDeveloper ecosystem, User adoption, Media/research visibility
HermesConfirmedSlack, Telegram, Discord, WhatsApp, OtherLocal, Self-hosted, Cloud, HybridOpen sourceDeveloper ecosystem, Media/research visibility
ArkClawConfirmedOtherCloudClosed sourceFunding/company momentum, Media/research visibility
Kimi ClawConfirmedOtherCloudClosed sourceUser adoption, Media/research visibility
PiConfirmedOtherLocal, Self-hostedOpen sourceDeveloper ecosystem, Media/research visibility
WeClawConfirmedWeChat, OtherLocal, Self-hostedOpen sourceDeveloper ecosystem, Media/research visibility
NemoClawConfirmedOtherSelf-hosted, Cloud, HybridOpen sourceDeveloper ecosystem, Media/research visibility
ZeroClawConfirmedOtherLocal, Self-hosted, HybridOpen sourceDeveloper ecosystem, Media/research visibility
NanoClawConfirmedSlack, Telegram, Discord, WhatsApp, OtherSelf-hosted, Cloud, HybridOpen sourceDeveloper ecosystem, Media/research visibility
IronClawConfirmedOtherLocal, Self-hosted, HybridOpen sourceDeveloper ecosystem, Media/research visibility
PocoClawConfirmedOtherSelf-hosted, Cloud, HybridOpen sourceDeveloper ecosystem
ClawWorkConfirmedOtherSelf-hosted, Cloud, HybridOpen sourceDeveloper ecosystem, Media/research visibility
MetaClawConfirmedOtherSelf-hostedOpen sourceDeveloper ecosystem, Media/research visibility
GoClawConfirmedOtherSelf-hosted, Cloud, HybridOpen sourceDeveloper ecosystem
ColaOSConfirmedOtherCloud, HybridClosed sourceUser adoption, Media/research visibility
FloatboatConfirmedSlack, Feishu/Lark, OtherLocal, Cloud, HybridClosed sourceUser adoption, Media/research visibility
DuMateConfirmedOtherLocal, Cloud, HybridClosed sourceFunding/company momentum, Media/research visibility
NanoBotConfirmedTelegram, OtherLocal, Self-hosted, CloudOpen sourceDeveloper ecosystem, Media/research visibility

This is a curated landscape for research and comparison. Inclusion is not an endorsement, and tracked entries should not be treated as verified channel support.