@tduyng/pi-session 0.0.2 → 0.0.3

package/README.md

@@ -1,20 +1,24 @@
 # @tduyng/pi-session
 
-Session lifecycle: sessions name themselves and resume once a provider quota resets. No more `untitled` rows in the picker, no more waiting out a usage limit by hand.
+Sessions name themselves, and a turn killed by a usage limit resumes when the limit resets. No more `untitled` rows in the picker, no more sitting out a quota by hand.
+
+## What it costs
+
+Nothing. No tool is registered, no prompt text is injected, and no session entry is created for the naming. The extension reads at `agent_end` and writes a name.
 
 ## Auto-name
 
-A new session starts unnamed. On `agent_end`, the extension reads the first user message and uses it as the name. It takes the first line, strips a leading `/` or `#`, collapses whitespace, and limits the result to 60 characters, cutting at a word boundary.
+A new session starts unnamed. On `agent_end` the extension reads the first user message and uses it: first line, a leading `/` or `#` stripped, whitespace collapsed, 60 characters at most, cut at a word boundary.
 
-An expanded skill uses its argument when one is present, or the skill name when it has no argument. The extension ignores the expanded instructions and the skill's filesystem path. A `/skill:name task` command follows the same rule and uses `task` when present. A `Skill invocation protocol` message without a skill block is skipped because an extension injected it. A name you set with `/name` always wins. Naming runs last and swallows its own errors. It is cosmetic and never blocks the turn.
+Before, a week of `2026-09-01 14:22`, `2026-09-01 14:47`, `2026-09-02 09:03`. After, `fix retry backoff`, `review auth diff`, `migrate schema`.
 
-The extension finds the first user-role message in the `event.messages` array. If the message content is a block array, it extracts text blocks and joins them with spaces. When no user message exists, naming is skipped silently.
+An expanded skill uses its argument when one is present, or the skill name when it has none. The extension ignores the expanded instructions and the skill's filesystem path. A `/skill:name task` command follows the same rule and uses `task`. A `Skill invocation protocol` message with no skill block is skipped, because an extension injected it. A name you set with `/name` always wins.
 
-Before: a week of `2026-09-01 14:22`, `2026-09-01 14:47`, `2026-09-02 09:03`. After: `fix retry backoff`, `review auth diff`, `migrate schema`.
+Naming runs last and swallows its own errors. It is cosmetic and never blocks a turn.
 
 ## Autoresume
 
-When a provider quota exhaustion kills a turn, the extension parses a reset time from the error text. Formats it accepts:
+When a provider quota exhaustion kills a turn, the extension parses a reset time out of the error text. It accepts:
 
 - Epoch timestamps: `limit reached|1757193000`
 - ISO timestamps: `resets at 2026-09-06T23:30:00+02:00`
@@ -22,15 +26,22 @@ When a provider quota exhaustion kills a turn, the extension parses a reset time
 - Clock times: `resets 11:30pm (Europe/Paris)`, `reset at 23:30`
 - Retry-after headers: `retry-after: 3600`
 
-For claude-bridge sessions where the error carries no reset time, autoresume queries the Anthropic OAuth usage endpoint and picks the latest reset among all exhausted windows, with the credential from the macOS keychain (`Claude Code-credentials`) or `~/.claude/.credentials.json`.
+For a claude-bridge session whose error carries no reset time, it asks the Anthropic OAuth usage endpoint and picks the latest reset among the exhausted windows, with the credential from the macOS keychain or `~/.claude/.credentials.json`.
 
-A 5-second safety delay is added past the reset time. The timer caps at 24 hours. A parsed reset further than 24 hours out schedules nothing and posts a warning: Usage limit resets in over 24h, auto-resume not scheduled. Any user turn or session shutdown cancels it. The resume sends a real user message: "The usage limit has reset. Continue the previous task from where it stopped."
+A 5-second safety delay is added past the reset, and the timer caps at 24 hours. A reset further out than 24 hours schedules nothing and posts a warning instead. Any user turn or session shutdown cancels it. The resume sends a real user message: "The usage limit has reset. Continue the previous task from where it stopped."
 
-Commands: `/autoresume`, `/autoresume status`, `/autoresume on`, `/autoresume off`, `/autoresume cancel`.
+A quota reset is the cheapest minute of the day to be running: the window opened, the work is ready, and nobody has to be awake for it.
+
+| Command | Effect |
+| --- | --- |
+| `/autoresume` | Status |
+| `/autoresume on` | Arm it |
+| `/autoresume off` | Disarm it |
+| `/autoresume cancel` | Drop the pending resume |
 
 ## Design
 
-Auto-naming reads at `agent_end`, when real conversation content exists. Autoresume touches no session storage and adds no tools beyond the one command. Session creation, storage, and selection stay with pi.
+Autoresume touches no session storage and adds no tool beyond its command. Session creation, storage, and selection stay with pi.
 
 ## Install
 
@@ -40,6 +51,4 @@ pi install npm:@tduyng/pi-session
 
 Local checkout: `pi install /path/to/dotfiles/pi/agent/extensions/pi-session`
 
-## Configure
-
-None. It works out of the box.
+No configuration required.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@tduyng/pi-session",
-  "version": "0.0.2",
-  "description": "Session lifecycle: name an unnamed session after its first message, and resume once a provider quota resets.",
+  "version": "0.0.3",
+  "description": "Sessions name themselves, and a turn killed by a usage limit resumes when the limit resets.",
   "keywords": [
     "pi",
     "pi-package",