pi-central 0.6.1 → 0.8.0

package/README.md

@@ -25,6 +25,13 @@ own working directory, each inside its own sandbox.** /paɪ ˈsɛntrəl/
 **Who this is for.** People who already run `pi` and want more than one session at a time.
 Contributors: jump to [Working on this project](#working-on-this-project).
 
+![Pi Central's dashboard: a session rail on the left listing one running, one idle and one stopped
+session with their working directories and context burn; the transcript in the middle showing the
+assistant's prose, a first-person turn containing a pasted screenshot rendered inline with its type
+and size, and a collapsed "Thinking…" group below it; the session header on the right with the model
+and thinking pickers; the composer at the foot with its key hints and an auto-follow toggle; and a
+topbar reading two sessions, one running, one scratch and connected.](docs/images/dashboard.png)
+
 **Status: works end to end, verified, and published.** The version is deliberately not written here —
 `pi-central --version` reports the version of the package it shipped in. See
 [docs/RELEASING.md](docs/RELEASING.md).
@@ -124,12 +131,14 @@ Stated plainly, because a dashboard that overstates itself is worse than one tha
 **Works:** multiple sandboxed sessions in different directories with verified isolation; live transcripts
 reconstructed from Pi's delta-only stream; the approval dock answerable for any session; a bounded tool
 trace with full traversal; a read-only file tree and image viewer confined to the session's directory;
+images shown where they belong in the conversation, including the ones a tool read, and screenshots pasted or
+dropped straight into the composer;
 history searchable by content, with a clear refusal when a session's directory is gone; a session roster
 that survives a restart; agent-scoped credentials with the host's own credentials denied, and commits
 signed as the agent when the store is configured to sign.
 
-**Not yet:** no file editing from the browser, no update checking, no export. Each is a tracked issue
-rather than a wish.
+**Not yet:** no file editing from the browser, no update checking, no export. The image size caps are derived from the
+transport's frame limit rather than tuned against real reading. Each is a tracked issue rather than a wish.
 
 ## Working on this project