Pi Messenger

Pi Messenger connects Pi coding agent sessions working in separate terminals on the same project. It's for developers who want agents to share progress and divide work without editing over one another. Coordination runs through local files, with no separate server or background service.

Agents can send direct messages or broadcasts that prompt recipients to respond. File reservations block other agents from writing to claimed files or directories and clear when the owner leaves or exits. A terminal overlay lets you join the conversation and see each agent's model, Git branch, and current activity. The shared feed records edits, commits, test runs, and task events; stuck detection alerts peers when an agent stays idle with unfinished work.

Crew handles larger assignments. It reads a product requirements document or a plain-language request, examines the codebase, and splits work into tasks with dependencies. Workers tackle independent tasks in parallel, and reviewers check completed work. Autonomous execution continues until tasks finish or hit a blocker. Workers can draw on project-specific skills for domain knowledge.

The optional Team layer adds roles, reusable profiles, persistent project memory, and approval gates for risky tasks. Crew logs and activity records stay in the project folder, while shared messaging state lives locally. Model execution is separate: agents inherit the Pi session's model or use role-specific choices, including Anthropic Claude models through cloud providers.