Pi, Day to Day
Why this guide exists
You can use Pi every day and still miss what it added last month. You may never try the features that would help you most. Pi ships fast. This guide keeps you current, a few new techniques a day, so you do not get left behind and you use Pi the way it is meant to be used.
Who it is for
Pi, Day to Day is a 12-day guide to Pi, the terminal coding agent, for developers who already use Claude Code.
How it works
You build one small project, Ticket Triage, across every day. Each day starts where the day before ended and takes 20 to 40 minutes. Start here is a real lesson that ends in a result you can check, such as a passing test. Going deeper holds the details and edge cases for when you have more time.
What you will learn
- Install Pi once and confirm which copy your shell runs (Day 1).
- Steer a run: correct it, queue a follow-up, and stop it (Day 3).
- Branch two approaches and keep the winner with
/clone(Day 5). - Compact on purpose and keep a rule in a three-line
AGENTS.md(Day 7). - Add a
/reviewprompt template and ashipskill (Day 8). - Write a
guard.tsextension that blocks one command (Day 9). - Run Pi inside Docker Sandboxes and prove the boundary (Day 10).
The 12 days fall into five stages: getting started (Days 1 and 2), daily habits (Days 3 to 5), context and memory (Days 6 and 7), extending Pi (Days 8 and 9), and working safely (Days 10 to 12).

How it was tested
The Start here steps ran live on Pi 1.5.2 in November 2026 with an Anthropic API key. Day 1 also ran with a Google Gemini key. Days 10 and 11 also used Docker Sandboxes, sbx v0.54.0. A step that was not run for this guide says so in the text.
Get the code
Day 1 builds Ticket Triage by hand. The code is in the ticket-triage-day-by-day repository on the pi branch, with one tag per day, pi/day-00 to pi/day-12. Use a tag to catch up on any day.
Start
Start at Day 1, one part a day.
Also in this series: Claude Code, Day-to-Day, Cursor, Day-to-Day, OpenAI Codex, Day-to-Day, OpenCode, Day-to-Day, and GitHub Copilot, Day-to-Day.
The parts
- Your Pi Update Succeeded. You Are Still Running the Old Pi.
- Your Pi Coding Agent Is Only as Smart as the Folder You Start It In
- Your Coding Agent Only Listens Between Turns
- One Character Decides What Your Coding Agent Reads
- Your Claude Code Habits Branch the Wrong Way in Pi
- Your Coding Agent Did Not Forget Your Rule. It Was Outvoted.
- Compact on Purpose: How Pi Decides What Your Coding Agent Forgets
- The Least Powerful File That Does the Job
- A Rule Asks. A Pi Extension Can Say No.
- Trust Is Not a Sandbox: Running the Pi Coding Agent Where Your Keys Cannot Follow
- Your Coding Agent Said Done. Did Anything Actually Run?
- Three Claude Code Habits That Misfire in Pi, and the Map for Everything Else