Files

psb-gemma 47a8b40fdb Add growth state frontmatter to all 280 wiki files

TREE(74): training modules, entity profiles, 2890 references, keyword indices
SPROUT(42): knowledge pages, project docs, curated source material
SEED(164): daily notes, raw session logs, unprocessed material

Updated AUDIT_MANIFEST.json with growth classifications.

2026-05-14 01:27:59 +00:00

3.3 KiB

Raw Blame History

pageType, id, title, sourceType, sourcePath, ingestedAt, updatedAt, status, growth

pageType	id	title	sourceType	sourcePath	ingestedAt	updatedAt	status	growth
source	source.tasks-channel-setup	tasks-channel-setup	local-file	/home/topher/.openclaw/workspace-2890-bot/docs/tasks-channel-setup.md	2026-05-02T21:24:29.951Z	2026-05-02T21:24:29.951Z	active	seed

tasks-channel-setup

Source

Type: local-file
Path: /home/topher/.openclaw/workspace-2890-bot/docs/tasks-channel-setup.md
Bytes: 2661
Updated: 2026-05-02T21:24:29.951Z

Content

# 🦅 #tasks Channel — Setup Guide

This doc walks you through getting the #tasks Discord channel fully operational.

---

## Step 1 — Create the #tasks Channel (Discord)

1. In Discord server settings → **Channels**
2. Create a new text channel: `#tasks`
3. Set permissions so your team can read/write
4. Pin the `tasks-channel-guide.md` overview for reference

---

## Step 2 — Route #tasks to 2890-bot (OpenClaw Gateway)

The OpenClaw gateway controls which channels route to which agents. You need to add a routing rule so messages in `#tasks` go to 2890-bot.

**Dashboard path:** `openclaw gateway` → configure → Discord → channel routing

OR via config file, add to the Discord plugin section:
```json
{
  "channels": {
    "#tasks": {
      "agent": "2890-bot",
      "skill": "tasks-channel"
    }
  }
}
```

**What this does:**
- Messages in `#tasks` → routed to 2890-bot
- 2890-bot reads `skills/tasks-channel/SKILL.md` for context
- Bot responds using `scripts/task-handler.js` and `scripts/standup-handler.js`

---

## Step 3 — Test It

In `#tasks`, try these:

```
!task list
!task add My first test task $scouting
!board summary
!standup status
```

The bot should respond with formatted output.

---

## Step 4 — Pin Board Summary (Optional)

Once working, pin a `!board summary` post in `#tasks` for the team to reference between standups.

---

## Step 5 — Start the Web Board (Wall Display)

On the machine running OpenClaw (or any machine on the same network):

```bash
cd /home/topher/.openclaw/workspace-2890-bot
node kanban-server.js
```

Then open `http://<machine-ip>:8080/board` on a tablet/monitor in the workspace.

---

## Rollback

If something goes wrong:
1. **Remove the channel routing** from the gateway config (go back to default)
2. **Restore openclaw.json** from backup:
   ```
   cp /home/topher/.openclaw/openclaw.json.bak-2026-04-27 /home/topher/.openclaw/openclaw.json
   openclaw gateway restart
   ```
3. Disable the #tasks channel routing — the board.json and scripts stay, they're just not connected to Discord

---

## Architecture Summary

```
Discord #tasks ──gateway──► 2890-bot agent
                              ├── reads SOUL.md + skills/tasks-channel/SKILL.md
                              └── execs scripts/task-handler.js
                                        └── reads/writes board.json

Web Board (tablet/monitor) ──http──► kanban-server.js (:8080)
                                          └── reads board.json
```

Both Discord and the web board share the same `board.json` — updates from either side are reflected in the other.

Notes

No related pages yet.

3.3 KiB Raw Blame History

tasks-channel-setup

Source

Content

Notes

Related

3.3 KiB

Raw Blame History