omp packages

pi-cue0.1.2

Get a notification on your iPhone (and Apple Watch) when pi is done or needs you, only when you are away. Uses Bark.

purboo Published 12 days ago MIT ~704 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Did it work for you?

Result

One report per person. A new report replaces your old one.

Reports 0

No reports yet.

Readme

pi-cue

A notification on your iPhone when pi is done, or needs you.

Sent through Bark, and only when you are away: if you are at the keyboard, nothing happens. While the iPhone is locked, it reaches your Apple Watch too.

Setup

  1. Install Bark from the App Store and allow notifications.
  2. pi install npm:pi-cue
  3. In pi: /cue key <the URL Bark shows>, then /cue test.

The key is stored in ~/.pi/agent/cue.json (mode 600). PI_CUE_KEY and PI_CUE_SERVER work too.

Use

Cues are off in every session until you turn them on, so parallel sessions don't all notify you.
/cue Toggle for this session. Remembered when you resume it.
/cue on · /cue off Explicit.
/cue test Send a sample.
/cue status On/off, key, server.

While on, cue shows in the status line.

What you get

When Level
● repo · Needs you pi waits on a confirm / select / input for 8s, or the reply ends on a question time-sensitive
● repo · Still waiting the same decision is still open after 10 min (once) time-sensitive
✗ repo · Failed a run failed time-sensitive
✓ repo · Done · 3m12s pi stopped 15s ago, and you had been away 30s or more normal

The body is the question, the error, or the first line of the answer. The time is how long since you last touched pi.

Background subagents

When a background subagent wakes the agent for a quick wrap-up, that still cues: away time counts from your last key press, not from the start of the run. A subagent's question, relayed by the agent as a reply ending in ?, cues as Needs you.

pi does not tell extensions about background work, so the turn that dispatches subagents cues once as Done (the body usually says what was dispatched), and each subagent that wakes the agent replaces that notification and alerts again.

Quiet by design

  • Away only. A cue waits out a grace period and is dropped if you pressed a key around that time. Escape-aborted runs never cue.
  • One per session. Each session replaces its own notification instead of stacking.
  • Cleans up. Answering, typing, starting a new run, or quitting removes the notification from the phone and watch. Removal needs Bark's Background App Refresh.
  • Never in the way. Network errors are swallowed. Nested and headless sessions never cue.

Config

~/.pi/agent/cue.json, all optional except key:

{
  "key": "…",
  "server": "https://api.day.app",
  "default": "on",
  "detail": false,
  "graceMs": 15000,
  "askGraceMs": 8000,
  "minRunMs": 30000,
  "remindMs": 600000
}

"default": "on" (or PI_CUE=1) starts new sessions with cues on. "detail": false sends only the project and state, never text from the session; worth it on the public Bark server. remindMs: 0 disables the reminder. minRunMs is the away time needed before Done or a question cues.

Development

bun install
bun run link-pi
bun run check        # tsc + bun test
pi -e ./index.ts     # try it