toolpath-pi 0.3.0

Derive Toolpath provenance documents from Pi (pi.dev) coding-agent session logs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47

# toolpath-pi

Read [Pi](https://pi.dev/) coding-agent session logs and derive Toolpath
provenance documents.

Pi stores sessions as JSONL files at
`~/.pi/agent/sessions/--<encoded-cwd>--/<timestamp>_<uuid>.jsonl`. Each
entry forms a tree via `id`/`parentId` fields, enabling in-place branching.
Sessions can link to parent sessions via a `parentSession` file path in
the session header.

This crate implements the [`toolpath_convo::ConversationProvider`] trait
and a `derive_path` wrapper that produces a [`toolpath::v1::Path`] via
the shared derivation in [`toolpath_convo::derive_path`].

## Quick example

```rust,no_run
use toolpath_pi::PiConvo;

let manager = PiConvo::new();
let session = manager
    .most_recent_session("/Users/alex/project")
    .unwrap()
    .expect("no Pi sessions");
let view = manager.to_view(&session);
```

## Listing sessions

`list_sessions` returns lightweight `SessionMeta` summaries — id, timestamp,
file path, entry count, and `first_user_message` (the first non-empty
user-prompt text). The last field is what makes the listing useful for
"pick a session by topic" surfaces like an `fzf` picker.

```rust,no_run
use toolpath_pi::PiConvo;

let manager = PiConvo::new();
for meta in manager.list_sessions("/Users/alex/project").unwrap() {
    println!(
        "{}: {}",
        meta.id,
        meta.first_user_message.as_deref().unwrap_or("(no prompt)"),
    );
}
```