LocalHarness — the dispatch plugin
Dispatch
← the plugins /dispatch
On once the dispatch extra is installed; turning it off leaves the terminal as it was.
how it works
- allowlisted messages a message from an allowed user becomes a turn; the reply posts back.
- questions in the chat when the gate needs you, the bot asks and you answer with a reaction.
- machine-level settings the token, allow list and channels; a project cannot change who drives the agent.
- the token never printed; doctor checks it without logging in.
- no network at start the bot connects when the session starts the channel, not before.
Setup
Turn it on from the session, fill in its settings, and it checks they work; your coding agent can do the hardware part.
~/project — localharness start
shipped
qwen3.6-27b ~/project
Plugins: memory, dispatch, autoresearch
❯ /plugins enable dispatch
Restarting with dispatch on — your conversation is kept.
Discord bot token:
Your Discord user id(s), comma-separated: 123456789012345678
✓ dispatch enabled in ~/.localharness/overrides.yaml
set dispatch.discord.token = '**********'
set dispatch.discord.allow = '123456789012345678'
Checking it now:
✓ dispatch: Discord configured — 1 allowed user(s); listens in any channel the bot can see
Then start the Discord session: localharness start --channel discord
Restarted with dispatch on. Your conversation continues.
dispatch: on in this session
in a session: /plugins enable dispatch · from a shell: localharness plugins enable dispatch
paste into your coding agent to set it up for your hardware
Set up the LocalHarness dispatch plugin on this machine. Install LocalHarness with its dispatch extra, keeping the extras I already use. Walk me through the Discord side: in the Discord Developer Portal, create a bot, turn on the Message Content intent and invite it to my server (OAuth2 > URL Generator, scope bot); then have me turn on Developer Mode and copy my user id. Then run `localharness plugins enable dispatch` and let me type the token at its hidden prompt myself: never print the token, store it in a file, or paste it into this chat. You are done when `localharness doctor` shows Discord configured and `localharness start --channel discord` answers my message.Surfaces
where you reach it
- localharness start --channel discord runs a session from Discord.
- dispatch.discord.token · allow · channels · ack the bot, who may drive it, where it listens, and the reaction it leaves.
- mode <name> typed in the chat, works as /mode.
- commands and tools none; it adds only a channel.
- localharness plugins enable dispatch enable asks the token (hidden) and your user id; --set does the same in a script.
- /plugins enable dispatch inside a running session: until it is set up, asks what it needs and checks it; then restarts with your conversation kept.