Use IRC when you want OpenClaw in classic \u6e20\u9053s ( “`json5 theme={“theme”:{“light”:”min-light”,”dark”:”min-dark”}} There are two separate \u201cgates\u201d for IRC \u6e20\u9053s:<\/p>\n Config keys:<\/p>\n Allowlist entries should use stable sender identities ( If you see logs like:<\/p>\n \u2026it means the sender wasn\u2019t allowed for group\/\u6e20\u9053<\/strong> messages. Fix it by either:<\/p>\n Example (allow anyone in “`json55 theme={“theme”:{“light”:”min-light”,”dark”:”min-dark”}} Or to allow all<\/strong> IRC \u6e20\u9053s (no per-\u6e20\u9053 allowlist) and still reply without mentions:<\/p>\n “`json55 theme={“theme”:{“light”:”min-light”,”dark”:”min-dark”}} Use “`json55 theme={“theme”:{“light”:”min-light”,”dark”:”min-dark”}} \u53ef\u9009\u9879 one-time registration on connect:<\/p>\n Disable Default account supports:<\/p>\n IRC Use IRC when you want OpenClaw in classic \u6e20\u9053s (#roo […]<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-600","post","type-post","status-publish","format-standard","hentry","category-docs"],"_links":{"self":[{"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/posts\/600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/comments?post=600"}],"version-history":[{"count":3,"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/posts\/600\/revisions"}],"predecessor-version":[{"id":810,"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/posts\/600\/revisions\/810"}],"wp:attachment":[{"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/media?parent=600"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/categories?post=600"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pa.yingzhi8.cn\/index.php\/wp-json\/wp\/v2\/tags?post=600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}#room<\/code>) and direct messages.
\nIRC ships as an extension plugin, but it is configured in the main config under channels.irc<\/code>.<\/p>\n\u5feb\u901f\u5f00\u59cb<\/h2>\n
\n
~\/.openclaw\/openclaw.json<\/code>.<\/li>\n
\n{
\n \u6e20\u9053s: {
\n irc: {
\n enabled: true,
\n host: “irc.libera.chat”,
\n port: 6697,
\n tls: true,
\n nick: “openclaw-bot”,
\n \u6e20\u9053s: [“#openclaw”],
\n },
\n },
\n}<\/p>\n\n3. Start\/restart gateway:\n\n```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}\nopenclaw gateway run\n<\/code><\/pre>\nSecurity defaults<\/h2>\n
\n
channels.irc.dmPolicy<\/code> defaults to \"pairing\"<\/code>.<\/li>\nchannels.irc.groupPolicy<\/code> defaults to \"allowlist\"<\/code>.<\/li>\ngroupPolicy=\"allowlist\"<\/code>, set channels.irc.groups<\/code> to define allowed \u6e20\u9053s.<\/li>\nchannels.irc.tls=true<\/code>) unless you intentionally accept plaintext transport.<\/li>\n<\/ul>\nAccess control<\/h2>\n
\n
groupPolicy<\/code> + groups<\/code>): whether the bot accepts messages from a \u6e20\u9053 at all.<\/li>\ngroupAllowFrom<\/code> \/ per-\u6e20\u9053 groups[\"#channel\"].allowFrom<\/code>): who is allowed to trigger the bot inside that \u6e20\u9053.<\/li>\n<\/ol>\n\n
channels.irc.allowFrom<\/code><\/li>\nchannels.irc.groupAllowFrom<\/code><\/li>\nchannels.irc.groups[\"#channel\"]<\/code><\/li>\nchannels.irc.groupPolicy=\"open\"<\/code> allows unconfigured \u6e20\u9053s (still mention-gated by default<\/strong>)<\/li>\n<\/ul>\nnick!user@host<\/code>).
\nBare nick matching is mutable and only enabled when channels.irc.dangerouslyAllowNameMatching: true<\/code>.<\/p>\nCommon gotcha:
allowFrom<\/code> is for DMs, not \u6e20\u9053s<\/h3>\n\n
irc: drop group sender alice!ident@host (policy=allowlist)<\/code><\/li>\n<\/ul>\n\n
channels.irc.groupAllowFrom<\/code> (global for all \u6e20\u9053s), or<\/li>\nchannels.irc.groups[\"#channel\"].allowFrom<\/code><\/li>\n<\/ul>\n#tuirc-dev<\/code> to talk to the bot):<\/p>\n
\n{
\n \u6e20\u9053s: {
\n irc: {
\n groupPolicy: “allowlist”,
\n groups: {
\n “#tuirc-dev”: { allowFrom: [“*”] },
\n },
\n },
\n },
\n}<\/p>\n\n## Reply triggering (mentions)\n\nEven if a channel is allowed (via `groupPolicy` + `groups`) and the sender is allowed, OpenClaw defaults to **mention-gating** in group contexts.\n\nThat means you may see logs like `drop channel \u2026 (missing-mention)` unless the message includes a mention pattern that matches the bot.\n\nTo make the bot reply in an IRC channel **without needing a mention**, disable mention gating for that channel:\n\n```json55 theme={"theme":{"light":"min-light","dark":"min-dark"}}\n{\n channels: {\n irc: {\n groupPolicy: "allowlist",\n groups: {\n "#tuirc-dev": {\n requireMention: false,\n allowFrom: ["*"],\n },\n },\n },\n },\n}\n<\/code><\/pre>\n
\n{
\n \u6e20\u9053s: {
\n irc: {
\n groupPolicy: “open”,
\n groups: {
\n ““: { requireMention: false, allowFrom: [“<\/em>“] },
\n },
\n },
\n },
\n}<\/p>\n\n## Security note (recommended for public channels)\n\nIf you allow `allowFrom: ["*"]` in a public channel, anyone can prompt the bot.\nTo reduce risk, restrict tools for that channel.\n\n### Same tools for everyone in the channel\n\n```json55 theme={"theme":{"light":"min-light","dark":"min-dark"}}\n{\n channels: {\n irc: {\n groups: {\n "#tuirc-dev": {\n allowFrom: ["*"],\n tools: {\n deny: ["group:runtime", "group:fs", "gateway", "nodes", "cron", "browser"],\n },\n },\n },\n },\n },\n}\n<\/code><\/pre>\nDifferent tools per sender (owner gets more power)<\/h3>\n
toolsBySender<\/code> to apply a stricter policy to \"*\"<\/code> and a looser one to your nick:<\/p>\n
\n{
\n \u6e20\u9053s: {
\n irc: {
\n groups: {
\n “#tuirc-dev”: {
\n allowFrom: [““],
\n toolsBySender: {
\n “<\/em>“: {
\n deny: [“group:runtime”, “group:fs”, “\u7f51\u5173”, “nodes”, “cron”, “browser”],
\n },
\n “id:eigen”: {
\n deny: [“\u7f51\u5173”, “nodes”, “cron”],
\n },
\n },
\n },
\n },
\n },
\n },
\n}<\/p>\n\nNotes:\n\n* `toolsBySender` keys should use `id:` for IRC sender identity values:\n `id:eigen` or `id:eigen!~eigen@174.127.248.171` for stronger matching.\n* Legacy unprefixed keys are still accepted and matched as `id:` only.\n* The first matching sender policy wins; `"*"` is the wildcard fallback.\n\nFor more on group access vs mention-gating (and how they interact), see: [\/channels\/groups](\/channels\/groups).\n\n## NickServ\n\nTo identify with NickServ after connect:\n\n```json5 theme={"theme":{"light":"min-light","dark":"min-dark"}}\n{\n channels: {\n irc: {\n nickserv: {\n enabled: true,\n service: "NickServ",\n password: "your-nickserv-password",\n },\n },\n },\n}\n<\/code><\/pre>\njson5 theme={\"theme\":{\"light\":\"min-light\",\"dark\":\"min-dark\"}}
\n{
\n channels: {
\n irc: {
\n nickserv: {
\n register: true,
\n registerEmail: \"bot@example.com\",
\n },
\n },
\n },
\n}<\/code><\/p>\nregister<\/code> after the nick is registered to avoid repeated REGISTER attempts.<\/p>\nEnvironment variables<\/h2>\n
\n
IRC_HOST<\/code><\/li>\nIRC_PORT<\/code><\/li>\nIRC_TLS<\/code><\/li>\nIRC_NICK<\/code><\/li>\nIRC_USERNAME<\/code><\/li>\nIRC_REALNAME<\/code><\/li>\nIRC_PASSWORD<\/code><\/li>\nIRC_CHANNELS<\/code> (comma-separated)<\/li>\nIRC_NICKSERV_PASSWORD<\/code><\/li>\nIRC_NICKSERV_REGISTER_EMAIL<\/code><\/li>\n<\/ul>\n\u6545\u969c\u6392\u67e5<\/h2>\n
\n
channels.irc.groups<\/code> and<\/strong> whether mention-gating is dropping messages (missing-mention<\/code>). If you want it to reply without pings, set requireMention:false<\/code> for the \u6e20\u9053.<\/li>\n