Skip to main content
piloop watch is a terminal app over the database. It shows every project, or one project with piloop watch <project>. It reads the database again whenever the daemon or an agent writes to it.

The screens

The first screen lists every project, the active ones first. Press enter to open one, and esc to come back.
A project has a header, four panels on the left, and the selected row in full on the right:
The header shows the head, the number of keeps, the spend and the tokens. The second line shows the progress against [stop]. With several tracks, one more line shows each track.

Panels and keys

These keys work everywhere:

What the keys write

Each key writes as PILOOP_ACTOR, which is human unless you set it. The events table records the write like any other.
  • Acknowledge does what piloop inbox ack does.
  • Reply asks for the text and a priority (default 2). It writes a decision comment that replies to the first item of the thread. The orchestrator’s next wait returns with it, and the orchestrator acknowledges it after it applies it.
  • Steer types text into the agent’s pane, as piloop prompt does. Herdr refuses while the agent waits on a dialog. Press enter to go to the agent’s tab and answer the dialog.
  • Approve, park and reject ask why. Each one writes the status change and a note on the idea with the reason. Approving a seed sends it to research first.

In Herdr

With the Herdr runtime, piloop has its own Herdr session, piloop, with one workspace for each project. The first tab of a workspace is home: a shell on the left and piloop watch <project> on the right. Each agent gets its own tab, named after its role, its id and its idea:
piloop attach <worker-id> opens an agent’s tab from any terminal.