Feature show more metainfo in `list`

[drahnr]

Currently my list output of shpool list looks like this:

2026-02-25-proganosauria-unbrokenly	2026-02-25T15:55:33.055+00:00	disconnected
2026-02-27-counterlight-argents	2026-02-27T09:11:17.341+00:00	attached
2026-02-24-laryngitic-wide-distant	2026-02-24T14:57:54.953+00:00	attached
2026-02-24-kinetographic-ripcords	2026-02-24T14:48:13.566+00:00	attached
2026-02-24-fanegadas-self-doctrine	2026-02-24T15:14:13.296+00:00	attached
2026-02-26-dezincification-bloomkin	2026-02-26T11:28:36.731+00:00	attached
2026-02-25-wheresoeer-powhatan	2026-02-25T20:26:22.742+00:00	attached

structured by a date prefix and generated name.

What I'd like to have as an extension under i.e. a verbose flag or git-esque format specifier, to allow me to see the name of the running process sub tree, the working directory and the user that's active. That would help tremendously to pick the right session.

Very happy to implement it.

[ethanpailes]

There is a -j/--json flag with some extra information (currently some additional timestamps I beleive).

We could add a "shell pid" field to the json output that would allow you to see the process tree (we'll leave walking the actual process tree up to other tools, just provide a sufficient entrypoint).

The other two fields are not possible for shpool to track. The shell running inside a shpool session is entirely opaque to shpool, so there is no way for us to know what directory the shell is currently in. If you want to track this value yourself, you should configure a prompt hook in your shell that updates some file with the data you need (basically just store a ($SHPOOL_SESSION_NAME, $(pwd)) tuple somewhere. I'm confused about what you mean by the user that is active. shpool is a per-user daemon, so there should only ever be one user running under a single shpool daemon.

If you want to take a swing at adding a "shell pid" field, I'd be happy to dig up some starting points in the code for you.