This was a real bug — nullclaw channel start was hardcoded to only look for Telegram and Signal. If neither was configured, it would exit with "No messaging channel configured" even if you had Discord, Slack, or anything else set up perfectly.

This has been fixed today (59165a5) and will be available in tonight's build. The channel start command now supports all 16 channels (everything except cli and webhook).

How it works now:

• nullclaw channel start discord — starts your Discord bot directly
• nullclaw channel start (no argument) — auto-detects the first configured channel (prefers Telegram → Signal → any other)

Discord config example (~/.nullclaw/config.json):

{
  "default_provider": "openrouter",
  "models": {
    "providers": {
      "openrouter": {
        "api_key": "sk-or-..."
      }
    }
  },
  "channels": {
    "discord": {
      "accounts": {
        "main": {
          "token": "YOUR_DISCORD_BOT_TOKEN",
          "guild_id": "123456789"
        }
      }
    }
  }
}

You can also use the flat format without accounts if you only have one:

{
  "channels": {
    "discord": {
      "token": "YOUR_DISCORD_BOT_TOKEN",
      "guild_id": "123456789"
    }
  }
}

Optional Discord fields:

• allow_from — list of user IDs that can interact with the bot (empty = everyone)
• require_mention — only respond when @mentioned (default: false)
• allow_bots — respond to other bots (default: false)

Then just run:

nullclaw channel start discord

Full channel setup docs: https://nullclaw.github.io/channels