Focus.AI Labs / Layer Report
Subject: Automation / Throughput Systems
Pi layer landing page
Layer landing page

This is where Pi stops being a single session.

Once users trust Pi enough, they wrap it in scripts, queues, worktrees, bots, and review lanes. This layer is the operational branch of the ecosystem.

Layer role Terminal-native automation branches outward
Representative projects Task Factory, PiSwarm, pi-mom
Navigation move Use this page to jump deeper without scanning the whole ecosystem first.
Layer thesis

How to read this part of the ecosystem

This is the shortest explanation of what this layer is for and why it matters.

Once users trust the core loop, the ecosystem forks into automation patterns: queue-first orchestration, worktree swarms, JSON-mode scripting, RPC integrations, Slack bots, and web/TUI overlays.

Key artifacts

Best entry points in this layer

These projects explain this branch of the ecosystem fastest.

Tools & Utilities

PiSwarm

PiSwarm is a Shell-based orchestration toolkit for parallel GitHub issue and PR processing using the pi agent and Git worktrees.

Work patterns

What people actually do here

These workflow slices connect the layer to real usage patterns.

Workflow pattern

Script the agent through JSON, RPC, or SDK

A big part of Pi's distinctiveness is that it can stop being a chat app and become infrastructure for bots, scripts, or embedded tooling.

Workflow pattern

Operate through worktrees or queues

When a single session stops scaling, Pi users either wrap it in queue-first review lanes or in shell-native worktree swarms; both paths show up clearly in the ecosystem.

Guardrails

What to remember while exploring

The layer-specific best-practice reminders that keep this branch legible.

Best practice

Choose your automation branch explicitly

There are at least two distinct Pi escalation paths: queue-first orchestration like Task Factory, and worktree-first shell swarms like PiSwarm. Pick the branch that matches how your team already works.