pi-loop AGENTS.md

Development guidance for pi-loop, a TypeScript extension that manages scheduled or event-triggered work, background monitoring, and limited subagent workflows.

In plain words
What is it for?
Implementing or changing pi-loop features while respecting its data stores, process monitoring, recovery, and subagent boundaries.
Why use it?
It clarifies which parts of the system own tasks, workflows, monitoring, and worker execution, reducing architectural mistakes.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/trvon/pi-loop/agents-md
Clone the repo
git clone --depth 1 https://github.com/trvon/pi-loop

Made for: Codex, OpenCode.

Per session 1,769 This file is loaded in full into every session.
When invoked 1,769 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01769 $0.01769
Opus 5 $0.00885 $0.00885
Sonnet 5 $0.00354 $0.00354
Haiku 4.5 $0.00177 $0.00177

Measured 2d ago against content hash 636935f76c41, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pi-loop AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

AGENTS.md · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

pi-loop development guide

Purpose

pi-loop is a Pi extension for scheduled/event-driven re-wakes, self-paced goals, task-driven workflows, bounded subagent orchestration, native fallback tasks, and background process monitoring.

Stack: strict TypeScript 7, ES2022, TypeBox, Vitest, and Biome.

Authority boundaries

Do not blur these domains:

  • LoopStore exclusively owns loops, workflow definitions/revisions/executions/history/leases, and finite subagent orchestration batches/dispatches.
  • TaskStore or external pi-tasks owns standalone tasks only.
  • /tasks, task RPC, TaskClaim, and TaskUpdate never control workflow work.
  • MonitorManager owns process-local monitor state; monitor recovery across Pi death is not implemented.
  • pi-subagents owns worker execution and global concurrency. pi-loop owns only session-scoped orchestration intent, bounded evidence, local capacity, and recovery decisions.
  • Pending notifications are memory-only; persisted controllers recover on resume, not while Pi is absent.

A feature that requires a cross-store workflow/task transaction violates the architecture.

Source map

src/index.ts                 extension registration and runtime wiring
src/api.ts                   supported @trevonistrevon/pi-loop/api surface
src/types.ts                 loop, workflow, revision, monitor contracts
src/store.ts                 LoopStore workflow/orchestration atomic mutations
src/workflow-admission.ts    provider-neutral blocker transition admission
src/task-store.ts            standalone native task persistence
src/*-reducer.ts             pure state transitions
src/coordinator.ts           reducer/effect coordination
src/scheduler.ts             cron scheduling and fire times
src/trigger-system.ts        cron/event/hybrid activation
src/monitor-manager.ts       child processes and bounded output
src/runtime/                 session, notification, backlog, orchestration, task-provider, monitor wiring
src/tools/                   model-facing tool definitions
src/commands/                /loop and /tasks
src/rpc/                     vendored cross-extension RPC
src/ui/                      status and tool rendering
test/                        unit, integration, property, and live harnesses

Read the full file on GitHub · 158 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 158 lines · 1,769 tokens per session scan A 636935f76c41

Subscribe to this mod's changes

pi-loop AGENTS.md is an instructions file published in the GitHub repository trvon/pi-loop (10 stars, last pushed 2d ago), licensed MIT. It adds 1,769 tokens to every session, about $0.0088 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.