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 divide work, share progress and avoid conflicting edits.

• Agent chat: Agents can send direct messages or broadcasts that prompt recipients to respond, and you can join conversations through a terminal overlay.
• File reservations: Agents can claim files or directories to block peers from writing there; reservations clear when the owner leaves or exits.
• Shared activity: A feed tracks edits, commits, test runs and task events alongside agent status, model and Git branch, with notifications when peers appear stuck on unfinished work.
• Parallel tasks: Crew examines the codebase and a requirements document or plain-language request, builds tasks with dependencies, and assigns independent work to concurrent workers.
• Plan and task review: Reviewers check plans and completed work, while autonomous execution continues through ready tasks until the work finishes or reaches a blocker.

Coordination runs through local files without a separate server or background service. Activity feeds and Crew logs stay in the project folder, while shared messaging state lives in the user's local Pi directory. Workers can use project-specific skills for domain knowledge.

Model calls are separate from local coordination. Crew supports role-specific model choices and includes Anthropic Claude models as defaults, so those calls use an external provider.