Skip to content

docs: sharpen runtime control story #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OnlineChef (ChefGroep) merged 1 commit into from
Sep 11, 2026
Merged

docs: sharpen runtime control story #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

<h1 align="center">Pi Control</h1>

<p align="center"><strong>Inspect the live Pi process, change it deliberately, and verify the result.</strong><br>Control sessions, models, tools and saved runtime state from the same process your agent is already using.</p>
<p align="center"><strong>Control Pi from inside the Pi process you are already running.</strong><br>Inspect sessions, models, tools and saved state, make one bounded change, then verify the live result against the same runtime.</p>

<p align="center">
<a href="https://www.npmjs.com/package/@groeponline/pi-control"><img src="https://img.shields.io/npm/v/@groeponline/pi-control.svg" alt="npm version"></a>
Expand All @@ -28,6 +28,8 @@ pi -e npm:@groeponline/pi-control

Pi loads the extension and its packaged operating skill automatically.

The hero above is the operating contract: capture current state, change the smallest surface possible, verify what Pi is actually running, and keep the evidence. There is no sidecar daemon or shadow state store.

## Three useful things to do first

### Verify what Pi is actually running
Expand Down