← Back to directory

pi-messenger

Multi-agent communication extension for pi coding agent

CoordinationVerified with notes★ 526MIT

Safety notes

Verified with notes
Multi-agent chat/task/file coordination using local files; no daemon/server.

Static scan findings

This is a first-pass static screen, not a formal audit. It flags patterns worth reading before install.

MEDIUM · token_access
index.ts
  • session: { toolCalls: 0, tokens: 0, filesModified: [] },
MEDIUM · token_access
lib.ts
  • tokens: number;
MEDIUM · token_access
handlers.ts
  • const tokens = a.session?.tokens ?? 0;
  • if (tokens >= 1000) {
  • parts.push(`${(tokens / 1000).toFixed(1)}k`);
MEDIUM · token_access
overlay-render.ts
  • const tokens = info.progress.tokens > 1000
  • ? `${(info.progress.tokens / 1000).toFixed(0)}k`
  • : `${info.progress.tokens}`;
MEDIUM · token_access
README.md
  • **Living Presence** - Status indicators (active, idle, away, stuck), tool call counts, token usage, and auto-generated status messages like "on fire" or "debugging...". Your agent
  • The planner sees a compact index of all discovered skills and can tag tasks with relevant ones. Workers see tagged skills as "Recommended for this task" with the full catalog under
  • Always use Bearer token auth. Paginate with cursor-based `?after=` params.
MEDIUM · spawn_shell
store.ts
  • import { execSync } from "node:child_process";
  • const result = execSync('git branch --show-current', {
  • const sha = execSync('git rev-parse --short HEAD', {
MEDIUM · token_access
store.ts
  • reg.session = { toolCalls: 0, tokens: 0, filesModified: [] };
MEDIUM · token_access
CHANGELOG.md
  • - **Dynamic skill loading for crew workers** — Workers can now acquire domain-specific knowledge on demand during task execution. A three-tier discovery system scans user skills (`
  • - **Lobby workers** - `+` spawns workers: assigns ready tasks directly when available, otherwise pre-spawns idle lobby workers that join the mesh and chat. Lobby workers receive ta
  • - **Chatter mitigation** - Per-worker outgoing message rate limiting via `messageBudgets` config. Coordination level and per-worker token count displayed in overlay header.
MEDIUM · token_access
tests/store.test.ts
  • session: { toolCalls: 0, tokens: 0, filesModified: [] },
  • session: { toolCalls: 0, tokens: 0, filesModified: [] },
MEDIUM · token_access
tests/crew/live-progress.test.ts
  • tokens: 1500,

Package scripts captured

package.json
{
  "test": "vitest run",
  "test:watch": "vitest"
}