About this template

Stop leaving Pi for a workflow engine

You already have the long conversation.

What you want next is control flow: propose → holy grail → y/n → implement — without opening n8n, a CI runner, or another harness.

This fork hands you that. Pi boots with osolmaz/pi-workflows installed and the example graphs seeded. Type /workflow and the boxed widget is already there.

The undeniable demo

export ANTHROPIC_API_KEY=sk-ant-...   # or OPENAI_API_KEY / GEMINI_API_KEY
pi
/workflow
/workflow echo summarize this repository

Or discuss a real problem first, then:

/workflow elegant-solution

Watch the graph advance above the editor: propose → holy grail → decision → implement or human checkpoint. Same conversation. No external orchestrator.

What lands in your fork

pi-workflows extension — pi install git:github.com/osolmaz/pi-workflows already run (package under ~/.pi/agent/git/…, registered in settings.json)
Seeded graphs ready as /workflow …:
- echo — smallest end-to-end graph
- elegant-solution — Socratic propose → holy grail → y/n → implement
- autoimplement — implement → verify → review loop
- branch, two-turn, shell, autoresearch
Runtime deps in persist (jiti, typebox) so imports resolve on a fresh fork
Native in-pi widget — the graph lives in the terminal, not a separate web viewer

BYOK — your keys, your VM

Model keys stay in your environment. They are never part of the template.

export ANTHROPIC_API_KEY=sk-ant-...
# export OPENAI_API_KEY=sk-...
# export GEMINI_API_KEY=...
pi

Then /workflow list (or /workflow alone) to see every seeded graph.

Who this is for

You run Pi and keep hitting multi-step sequences that need conditionals
You tried bolting an orchestrator outside the harness and lost conversation context
You want a forkable box, not a weekend of package wiring

Who this is not for

You need Claude Code / Codex / OpenClaw specifically (this harness is Pi only)
You want someone else to hold your model keys (jurniti is BYOK — you export them)

Provenance

Built from osolmaz/pi-workflows by Onur Solmaz. Pi: pi.dev.

Fork it. Own the box. Keep the conversation.

Risk note

jurniti 30-day money-back on first purchase. Model keys are yours (BYOK).

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

Pi agent
The upstream harness, pre-installed — same version the creator ran.
Starter VM
1 vCPU · 2 GiB RAM · 10 GiB disk.
Creator's /persist data
The captured persist volume is copied byte-for-byte into your fork.
BYOK — your keys, your VM
Add your model API keys after forking; they live only inside your microVM.

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

ANTHROPIC_API_KEY
GEMINI_API_KEY
OPENAI_API_KEY

Your own Pi Workflows Control Flow, live in about 3 minutes.

Forking copies this Piagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Pi Workflows Control Flow

What's inside