@d3ara1n/pi-peek-agent2.0.1

Retrieve and summarize another pi session's records through pi-mesh without contacting its assistant.

GitHub Actions Published 19 days ago MIT ~932 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.

Reports 0

No reports yet.

Readme

@d3ara1n/pi-peek-agent

Cross-instance peek for pi — investigate another pi instance's session without disturbing its main conversation. Built on @d3ara1n/pi-mesh for discovery and transport.

Adds the peek tool. Discovery, identity, and the socket mesh live in pi-mesh — load pi-mesh alongside this package.

How it works

Each call runs a temporary pi-peek investigation on the target instance. The helper receives complete dialogue and summaries, retrieves other saved blocks as needed, and reports focused summaries, explanations and findings. The target assistant does not receive the request.

Fresh snapshot per call — include context when following up. Saved thinking is excluded unless includeThinking is enabled.
Live tool view — the collapsed row shows activity and report character count, then the summary. The expanded view streams the Markdown report and stays at … before body text arrives.
Result details — snapshot time, usage, request/tool counts, stop reason and reportMode (tagged or fallback) accompany the report.
Bounded lifetime — the temporary snapshot and helper history are discarded after the call. Caller-session storage and model-provider retention are separate.

Tag parsing, retrieval budgets and cancellation are shared with pi-peek. The client also decodes raw-token streams from older peers using the shared parser.

Tool

`peek`

Investigate another instance's session without disturbing its main conversation.

Parameter	Required	Description
`question`	yes	Information to locate in the session; include context for follow-ups.
`includeThinking`	no	Include readable thinking saved in the session. Defaults to false; missing/redacted thinking cannot be recovered.
`at`	no	Target instance name (e.g. `"Fox"`). Omit to auto-pick the other same-project instance.
`sessionId`	no	Pin a specific instance by sessionId (use when names collide).

Peer discovery moved to pi-mesh — use mesh_list (provided by pi-mesh) to see who's online.

Installation

pi install npm:@d3ara1n/pi-model-roles
pi install npm:@d3ara1n/pi-peek
pi install npm:@d3ara1n/pi-mesh
pi install npm:@d3ara1n/pi-peek-agent

Or add to ~/.pi/agent/settings.json:

{
  "extensions": [
    "/absolute/path/to/pi-extensions/packages/pi-model-roles",
    "/absolute/path/to/pi-extensions/packages/pi-peek",
    "/absolute/path/to/pi-extensions/packages/pi-mesh",
    "/absolute/path/to/pi-extensions/packages/pi-peek-agent"
  ]
}

Dependencies

@d3ara1n/pi-mesh — peer discovery + transport
@d3ara1n/pi-peek — temporary active-context investigations

Configuration

Optional, in ~/.pi/agent/settings.json under peek:

{
  "peek": {
    "investigateTimeoutMs": 120000,
    "timeoutMs": 90000,
    "role": "utility",
    "maxRounds": 6,
    "maxOutputTokens": 8192
  }
}

investigateTimeoutMs is the caller's transport wait timeout. timeoutMs is the serving instance's independent deadline for the entire investigation, including authentication, every model request and retrieval rounds. Set the caller's wait timeout longer than the serving instance's deadline, allowing for transport overhead.

Cancelling a caller's request or disconnecting does not currently propagate cancellation to the serving handler through the mesh protocol. Remote work is bounded by its own deadline and is aborted on session shutdown. No mesh protocol changes are required.

See pi-peek configuration for model role, retrieval rounds, output budgets and deadline settings. Discovery/registry/heartbeat configuration belongs to pi-mesh's mesh block.

Naming

Names are managed by pi-mesh — see the pi-mesh README. Each instance gets a stable name derived from its session id; override at startup with PI_MESH_NAME, or rename at runtime with /mesh:rename.

License

MIT