Skip to content

pi

meshpoint connect pi

writes ~/.pi/agent/extensions/meshpoint.js and ~/.pi/agent/skills/meshpoint/SKILL.md. pi loads every .js file in its extensions directory, so no settings change is needed; restart pi or /reload.

The extension file is a one-line stub that imports the built extension from the CLI’s install by absolute path. pi’s loader resolves relative imports from a symlink’s own directory, so a symlink does not work; re-run meshpoint connect pi after moving or reinstalling the CLI.

--pi-dir <dir> targets another agent directory ($PI_CODING_AGENT_DIR is honoured too). pi has no per-repository config, so --project does not apply.

pi event What happens
session_start Opens the tap for the session and starts recall in the background.
before_agent_start Spools the prompt. On the first prompt, returns the recall and presence as a hidden custom message.
turn_end, tool_call Collect the reply text and the paths passed to edit and write.
agent_before_settle Spools the reply. When a checkpoint is due, appends the nudge as a visible custom message with continue: true, so pi runs one more turn in which the agent runs the skill.
session_before_compact, session_shutdown Send the spool.
session_compact Fetches recall again for the next prompt, since the inject may have been summarized away.

Resumed sessions count the replies already in the session branch, so a long session resumed across restarts still checkpoints on time.

pi -p --session-id <uuid> "..." runs the extension too. Twenty prompts with the same session id trigger the nudge on the twentieth; the extra turn shows as that run taking a few seconds longer.