pi-meeting-blackboard

Blackboard-based brainstorm and debate meetings for pi subagents.

pi-meeting-blackboard adds two meeting commands, /brainstorm2 and /debate2. In a meeting, each participant writes its full contribution to an append-only blackboard under .pi-meetings/.... The main chat shows compact entry cards and facilitator summaries, while the full transcript remains available on disk.

中文说明见 README.zh-CN.md.

Features

• Blackboard-based meeting records stored in .pi-meetings/.
• Compact visible cards for participant entries in the main conversation.
• Full participant contributions stored as Markdown files.
• A JSONL index for lightweight cross-round context.
• Built-in commands for brainstorming and debate workflows.
• Bundled default participant agent definitions for first-time setup.

Install

From npm:

pi install npm:pi-meeting-blackboard

From GitHub:

pi install git:github.com/Jarcis-cy/pi-meeting-blackboard@v0.1.1

For local development:

pi install /Users/jarcis/Project/pi-meeting-blackboard

Prerequisites

This extension expects pi's subagent tool to be available. The command handler creates the meeting blackboard and then instructs the main agent to run:

• gpt-brainstormer
• deepseek-brainstormer
• minimax-brainstormer

On first use, if any of these user-level agents are missing, the extension asks before writing bundled defaults to ~/.pi/agent/agents/. Existing files are never overwritten.

Commands

/brainstorm2 <topic>
/debate2 <topic>

/brainstorm2 starts a three-round blackboard brainstorming session.

/debate2 starts an open-ended blackboard debate that should continue until convergence or user intervention.

How It Works

participant -> meeting_append_entry -> .pi-meetings/... files
participant -> short WROTE_ENTRY summary -> facilitator context
file watcher -> compact visible card -> main chat
facilitator -> structural summary / final conclusion

The blackboard files are the source of truth for the meeting. The facilitator can read the index or specific entries when producing summaries.

Tools

The extension registers three tools for meeting participants and the facilitator:

• meeting_append_entry writes a full participant contribution to disk and returns only a short reference.
• meeting_read_index lists blackboard entries by id, speaker, phase, summary, and path.
• meeting_read_entry reads one full entry when the facilitator or a participant needs it.

Files

Each meeting writes an append-only folder under the current working directory:

.pi-meetings/YYYY-MM-DD-topic/
  manifest.json
  index.jsonl
  blackboard.md
  entries/
    0001-gpt-round_1.md
    0002-deepseek-round_1.md

blackboard.md is the full meeting transcript. index.jsonl is the compact context entry point. Full participant text lives in entries/.

Safety

The extension validates that meeting paths stay under the current workspace's .pi-meetings/ directory and rejects symlinked meeting paths, entry files, index files, and blackboard files. Entry writes use exclusive creation to avoid overwriting existing files.

Development

npm pack --dry-run

The extension is TypeScript loaded by pi through its extension loader. Runtime dependencies imported from pi (@earendil-works/pi-coding-agent, @earendil-works/pi-tui, and typebox) are declared as peer dependencies per pi package guidance.

License

MIT